X-Git-Url: http://git.indexdata.com/?p=yazproxy-moved-to-github.git;a=blobdiff_plain;f=doc%2Fproxy.xml;h=2f15f7f4bafcedaff7806ccf82c763dc896de5c3;hp=da89b1d0c2bac5f28ccb0883216082da3403e655;hb=55cae2f576f69682a9b45890bd06b01dfa7775ea;hpb=3f57a94d4bb1753d013d5bf450af407d6a32d36d

diff --git a/doc/proxy.xml b/doc/proxy.xml
index da89b1d..2f15f7f 100644
--- a/doc/proxy.xml
+++ b/doc/proxy.xml
@@ -48,7 +48,7 @@
     <literal>your.company.com</literal> like this:
    </para>
    <screen>
-    yaz-proxy -a - -t tcp:foo.bar.com:18398 tcp:@:9000
+    yazproxy -a - -t tcp:foo.bar.com:18398 tcp:@:9000
    </screen>
    <para>
     (The <literal>-a -</literal> option requests APDU logging on
@@ -281,10 +281,10 @@
     order for the config file facility to be enabled.
    </para>
    <tip>
-    <para>To check for a config file to be well-formed, the yaz-proxy may
+    <para>To check for a config file to be well-formed, the yazproxy may
      be invoked without specifying a listening port, i.e.
      <screen>
-      yaz-proxy -c myconfig.xml
+      yazproxy -c myconfig.xml
      </screen>
      If this does not produce errors, the file is well-formed.
     </para>
@@ -640,7 +640,7 @@
    <title>Proxy Usage</title>
    <para>
    </para>
-   <refentry id="yaz-proxy">
+   <refentry id="yazproxy-ref">
     &yaz-proxy-ref;
    </refentry>
   </section>