[SR-Dev] git:master: spelling fixes in documentation

[Henning Westerholt]

Module: sip-router
Branch: master
Commit: 247a71839a3112aac26ce0ac27e0507664bfe810
URL:    http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=247a71839a3112aac26ce0ac27e0507664bfe810

Author: Henning Westerholt <henning.westerholt at 1und1.de>
Committer: Henning Westerholt <henning.westerholt at 1und1.de>
Date:   Thu Apr 30 19:58:20 2009 +0200

spelling fixes in documentation

---

 modules_s/registrar/README            |   14 +++++++-------
 modules_s/registrar/doc/registrar.xml |    4 ++--
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/modules_s/registrar/README b/modules_s/registrar/README
index 102fe58..0bb62ee 100644
--- a/modules_s/registrar/README
+++ b/modules_s/registrar/README
@@ -70,12 +70,12 @@ UA2 ---- NAT2 ----| 5090    |
    Registrar and usrloc would store the public IP of NAT with each
    registered contact, thus it would know how to reach both user agents.
 
-   In addition to the publi IP and port of the NAT device, registrar would
-   also remember the destination IP and port of the REGISTER request (the
-   IP and port used in SER). If registrar did not store this information,
-   it would not know what outbound socket it should use when sending SIP
-   messages to the registered contact. It would use the default port
-   number (often 5060) for such outgoing requests.
+   In addition to the public IP and port of the NAT device, registrar
+   would also remember the destination IP and port of the REGISTER request
+   (the IP and port used in SER). If registrar did not store this
+   information, it would not know what outbound socket it should use when
+   sending SIP messages to the registered contact. It would use the
+   default port number (often 5060) for such outgoing requests.
 
    When an INVITE for UA1 comes, everything would work because UA1 used
    port 5060 when registering and that is also the destination port in the
@@ -98,7 +98,7 @@ UA1 ---- NAT1        +------ |  5060  | <---------------
 UA2 ---- NAT2 X <----+       |  5090  |
                              +--------+
 
-   That is the reason why registrar and usrloc also need to remmember the
+   That is the reason why registrar and usrloc also need to remember the
    IP and port used on the server side, that information would be used
    later when forwarding INVITEs:
                                  SER
diff --git a/modules_s/registrar/doc/registrar.xml b/modules_s/registrar/doc/registrar.xml
index da8e93e..b553f0a 100644
--- a/modules_s/registrar/doc/registrar.xml
+++ b/modules_s/registrar/doc/registrar.xml
@@ -72,7 +72,7 @@ UA2 ---- NAT2 ----| 5090    |
 	    agents.
 	</para>
 	<para>
-	    In addition to the publi IP and port of the NAT device, registrar
+	    In addition to the public IP and port of the NAT device, registrar
 	    would also remember the destination IP and port of the REGISTER
 	    request (the IP and port used in SER). If registrar did not store
 	    this information, it would not know what outbound socket it should
@@ -111,7 +111,7 @@ UA2 ---- NAT2 X <----+       |  5090  |
 ]]>
 	</programlisting>
 	<para>
-	    That is the reason why registrar and usrloc also need to remmember
+	    That is the reason why registrar and usrloc also need to remember
 	    the IP and port used on the server side, that information would be
 	    used later when forwarding INVITEs:
 	</para>