pua_dialoginfo: Fix typos in module documentation

src/modules/pua_dialoginfo/doc/pua_dialoginfo_admin.xml

@@ -70,7 +70,7 @@
 		transaction, the pua_dialoginfo module sets the id parameter to the same 
 		value as the call-id parameter. The "local-tag" indicates the local tag of the
 		entity. The remote-tag indicates the tag of the remote party. The "direction"
-		indicates if the entity was the initator of the dialog or the recepient (aka
+		indicates if the entity was the initiator of the dialog or the recipient (aka
 		if the entity sent or received the first INVITE).
 
 	</para>
@@ -83,7 +83,7 @@
 	<para>
 
         The dialog element can contain optional "local" and "remote" elements which
-        decsribes the local and the remote party in more detail, for example:
+        describes the local and the remote party in more detail, for example:
 
         <programlisting format="linespecific">
 <![CDATA[
@@ -323,7 +323,7 @@ modparam("pua_dialoginfo", "override_lifetime", 300)
 			will start blinking if the state is early, regardless if is is the
 			caller or the callee (indicated with the "direction" parameter).
 			To avoid blinking LEDs for the caller, you can enable this parameter.
-			Then the state of the caller will be singaled as "confirmed" even
+			Then the state of the caller will be signaled as "confirmed" even
 			in "early" state. This is a workaround for the buggy Linksys SPA962
 			phones. SNOM phones work well with the default setting.
 		</para>
@@ -400,7 +400,7 @@ modparam("pua_dialoginfo", "disable_callee_publish_flag", 10)
 		<section>
 		<title><varname>use_pubruri_avps</varname> (int)</title>
 		<para>
-			Get Publish R-Uri from avps (see corresponding avp params), not from reqeust to/from uri. 
+			Get Publish R-Uri from avps (see corresponding avp params), not from request to/from uri. 
 		</para>
 		<para>
 			<emphasis>Default value is <quote>0</quote>.</emphasis>