Minor fixes for API extension doc

Update the API Extensions doc to reflect new source directory layout.

diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index 59d3414a5bcd7e790e5d8c5283f6fba4f3b11910..de6eedc877f2622296151e3d5163c8d94b4fc2fd 100644 (file)
--- a/docs/api_extension.html.in
+++ b/docs/api_extension.html.in
@@ -178,7 +178,7 @@
       involves making two additions to:
     </p>
 
-    <p><code>qemud/remote_protocol.x</code></p>
+    <p><code>src/remote/remote_protocol.x</code></p>
 
     <p>
       First, create two new structs for each new function that you're adding
@@ -198,7 +198,7 @@
 
     <p>
       Once these changes are in place, it's necessary to run 'make rpcgen'
-      in the qemud directory to create the .c and .h files required by the
+      in the src directory to create the .c and .h files required by the
       remote protocol code. This must be done on a Linux host using the
       GLibC rpcgen program. Other rpcgen versions may generate code which
       results in bogus compile time warnings
@@ -213,7 +213,7 @@
       the rpcgen generated .h files.  The remote method calls go in:
     </p>
 
-    <p><code>src/remote_internal.c</code></p>
+    <p><code>src/remote/remote_internal.c</code></p>
 
     <p>Each remote method invocation does the following:</p>
 
@@ -243,7 +243,7 @@
       The server side dispatchers are implemented in:
     </p>
 
-    <p><code>qemud/remote.c</code></p>
+    <p><code>daemon/remote.c</code></p>
 
     <p>Again, this step uses the .h files generated by make rpcgen.</p>