Browse code

Typos fixed.

Jan Janak authored on 25/03/2003 22:36:00
Showing 1 changed files
... ...
@@ -58,9 +58,8 @@
58 58
 	    </abstract>
59 59
 	    <para>
60 60
 		Each function exported by a module must be described by <structname>cmd_export_t</structname> structure. Structures describing all exported
61
-		functions are arranged into an array and pointer to the array is then passed to the core. The last element of the array must contain 0 in
62
-		all it's fields, this element serves as the mark telling the core that this is the very last element of the array and it must stop
63
-		scanning the array.
61
+		functions are arranged into an array and pointer to the array is then passed to the core. The last element of the array must contain 0 in all
62
+		it's fields, this element serves as the mark telling the core that this is the very last element and it must stop scanning the array.
64 63
 	    </para>
65 64
 	    <para>
66 65
 		Each exported function is described by the following structure:
... ...
@@ -102,8 +101,8 @@ typedef int (*cmd_function)(struct sip_msg*, char*, char*);
102 101
 			    have to do type-casting otherwise the compiler will complain and will not compile your module.
103 102
 			</simpara>
104 103
 			<simpara>
105
-			    Simply put (cmd_function) just before the function name, for example <varname>(cmd_function)my_function</varname>. Don't use this
106
-			    unless you know what are you doing ! The server might crash if you pass wrong parameters to the function later !
104
+			    Simply put (cmd_function) just before the function name, for example <function moreinfo="none">(cmd_function)my_function</function>. 
105
+			    Don't use this unless you know what are you doing ! The server might crash if you pass wrong parameters to the function later !
107 106
 			</simpara>
108 107
 		    </note>
109 108
 		</listitem>
... ...
@@ -139,7 +138,7 @@ typedef int (*cmd_function)(struct sip_msg*, char*, char*);
139 138
 			Fixup function can be used to convert the string back to integer. Such a conversion should happend only once because the string
140 139
 			parameter doesn't change when the server is running. Fixup is therefore ideal place for the conversion, it will be converted upon the
141 140
 			server startup before the server starts processing <acronym>SIP</acronym> messages. After the conversion the function will get directly
142
-			the converted value. See existing modules for an example of such a fixup function.
141
+			the converted value. See existing modules for example of such a fixup function.
143 142
 		    </simpara>
144 143
 		</listitem>
145 144
 		<listitem>
... ...
@@ -169,9 +168,9 @@ typedef int (*cmd_function)(struct sip_msg*, char*, char*);
169 168
 	    </abstract>
170 169
 	    <simpara>
171 170
 		Each parameter exported by a module must be described by <structname>param_export_t</structname> structure. Structures describing all exported
172
-		parameters are arranged into an array and pointer to the array is then passed to the core. The last element of the array must contain 0 in
173
-		all it's fields, this element serves as the mark telling the core that this is the very last element of the array and it must stop
174
-		scanning the array (This is same as in array of exported functions).
171
+		parameters are arranged into an array and pointer to the array is then passed to the core. The last element of the array must contain 0 in all
172
+		it's fields, this element serves as the mark telling the core that this is the very last element and it must stop scanning the array (This is
173
+		same as in array of exported functions).
175 174
 	    </simpara>
176 175
 	    <simpara>
177 176
 		Each exported parameter is described by the following structure: