Browse code

ldap: Fix typos in module documentation

Florian Floimair authored on 26/02/2018 21:52:44 • Daniel-Constantin Mierla committed on 28/02/2018 17:00:48
Showing 1 changed files
... ...
@@ -647,7 +647,7 @@ ldap_result("telephoneNumber/$avp(s:tel_number)");
647 647
 
648 648
             <listitem>
649 649
               <para>
650
-		Opional specification of destination AVP type, either <varname>str</varname>
650
+		Optional specification of destination AVP type, either <varname>str</varname>
651 651
 		or <varname>int</varname>. If this parameter is not specified then the LDAP
652 652
 		attribute values are stored as AVP of type string.
653 653
 	      </para>
... ...
@@ -767,7 +767,7 @@ ldap_result("SIPIdentitySIPURI/$avp(i:10)", "/^[^@]+@(.+)$/\1/");
767 767
             <term>string_to_match</term>
768 768
 
769 769
             <listitem>
770
-              <para>String to be matched. Included AVPs and pseudo variabels
770
+              <para>String to be matched. Included AVPs and pseudo variables
771 771
               do get expanded.</para>
772 772
             </listitem>
773 773
           </varlistentry>
... ...
@@ -995,7 +995,7 @@ if (ldap_result_next())
995 995
             <term><parameter>string</parameter></term>
996 996
 
997 997
             <listitem>
998
-              <para>String to apply RFC 4515 and URL escpaing rules to.
998
+              <para>String to apply RFC 4515 and URL escaping rules to.
999 999
 	      AVPs and pseudo variables do get expanded. Example:
1000 1000
               <varname>"cn=$avp(s:name)"</varname></para>
1001 1001
             </listitem>