[hipl-commit] [trunk] Rev 4526: doc: misc small typo, grammar and cosmetical fixes

From: Diego Biurrun <diego@xxxxxxxxxx>
To: hipl-commit@xxxxxxxxxxxxx
Date: Sun, 16 May 2010 17:36:42 +0300
Committer: Diego Biurrun <diego@xxxxxxxxxx>
Date: 16/05/2010 at 17:36:42
Revision: 4526
Revision-id: diego@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Branch nick: trunk

Log:
  doc: misc small typo, grammar and cosmetical fixes

Modified:
  M  doc/HOWTO.xml

=== modified file 'doc/HOWTO.xml'
--- doc/HOWTO.xml       2010-05-16 14:33:52 +0000
+++ doc/HOWTO.xml       2010-05-16 14:36:21 +0000
@@ -2233,7 +2233,7 @@
   Ldapadd can be used similarly with LDAPURI and HITs.
   </para>
   <para>
-  Maybe the most intereseting part are the ACL rules with OpenLDAP. In
+  Maybe the most interesting parts are the ACL rules with OpenLDAP. In
   the newer versions you can use IPv6 formatted peername rules, so it
   is interesting when we remember that HITs are IPv6 formatted. Below
   is the basic example of a rule that grants write/read/search
@@ -2407,10 +2407,10 @@
     }
 
     define service {
-        use                             local-service
-        host_name                       crossroads.infrahip.net
-        service_description             PING
-        check_command                   check_ping6
+        use                     local-service
+        host_name               crossroads.infrahip.net
+        service_description     PING
+        check_command           check_ping6
     }
 
     define host {
@@ -2818,7 +2818,7 @@
           <programlisting>
             whitelist = "2001:0018:8321:4e1a:c009:1ff8:fed4:8e9c"
           </programlisting>
-          ,where 2001:0018:8321:4e1a:c009:1ff8:fed4:8e9c is the HIT of the
+          where 2001:0018:8321:4e1a:c009:1ff8:fed4:8e9c is the HIT of the
           responder. Multiple HITs are separated with commas:
           <programlisting>
             whitelist = 
"2001:0018:8321:4e1a:c009:1ff8:fed4:8e9c","2001:11:91e3:528e:7c41:9560:82ae:630f"
@@ -3753,7 +3753,7 @@
         by installing the Miredo client software. Then, establish HIP 
connections
         to Teredo addresses (check ifconfig teredo) at the client side as
         instructed in <xref linkend="ch_basictest" />. As Teredo is a NAT 
traversal
-        solution by itself, you don't have use UDP encapsulation for HIP 
(hipconf nnat none).
+        solution by itself, you don't have use UDP encapsulation for HIP 
(hipconf nat none).
       </para>
       <para>
         See
@@ -3850,7 +3850,9 @@
            hipd
     </para></listitem>
     <listitem><para>
-            . Using hipconf tool to set HIP Opportunistic mode on both hosts 
manually. "hipconf set opp on|off" command is used to enable/disable 
opportunistic mode. By default it is on.
+            Use the hipconf tool to set up HIP Opportunistic mode on both
+            hosts manually. "hipconf set opp on|off" is used to
+            enable/disable opportunistic mode. By default it is on.
     </para></listitem>
     <listitem><para>
            Now the opportunistic mode is enabled. To test Opportunistic mode, 
you need to remove crash's HITs and name from /etc/hip/hosts, and then 
following the steps in <xref linkend="ch_basictest" />.
[hipl-commit] [trunk] Rev 4526: doc: misc small typo, grammar and cosmetical fixes

Other related posts:
