sip/sip_util.c: typo

RELEASE

@@ -89,7 +89,7 @@ Certain static methods from tport.c were exposed to make this possible.
 
 2) Certificate subjects are copied out of the peer certificate before
 the first message is sent.  The next patch will include code that allows
-the stack to reject messages sent to a untrusted peer.
+the stack to reject messages sent to an untrusted peer.
 
 3) The tport module can now report whether a secondary has a verified
 certificate chain and the subjects of the peer certificate.

libsofia-sip-ua-glib/su-glib/su_source.c

@@ -538,7 +538,7 @@ GSource *su_source_gsource(su_port_t *self)
 /** @internal
  *
  *  Register a @c su_wait_t object. The wait object, a callback function and
- *  a argument pointer is stored in the port object.  The callback function
+ *  an argument pointer is stored in the port object.  The callback function
  *  will be called when the wait object is signaled.
  *
  *  Please note if identical wait objects are inserted, only first one is
@@ -673,7 +673,7 @@ int su_source_register(su_port_t *self,
 /** Unregister a su_wait_t object.
  *
  *  The function su_source_unregister() unregisters a su_wait_t object. The
- *  wait object, a callback function and a argument are removed from the
+ *  wait object, a callback function and an argument are removed from the
  *  port object.
  *
  * @param self     - pointer to port object
@@ -754,7 +754,7 @@ int su_source_unregister(su_port_t *self,
 /** Deregister a su_wait_t object.
  *
  *  The function su_source_deregister() deregisters a su_wait_t registrattion.
- *  The wait object, a callback function and a argument are removed from the
+ *  The wait object, a callback function and an argument are removed from the
  *  port object.
  *
  * @param self     - pointer to port object

libsofia-sip-ua/bnf/bnf.c

@@ -738,7 +738,7 @@ int host_is_ip6_reference(char const *string)
 
 /** Return true if @a string is valid IP address.
  *
- * Valid IP address is either a IP4 adddress in quad-octet notation,
+ * Valid IP address is either an IP4 adddress in quad-octet notation,
  * IP6 hex address or IP6 reference in square brackets ([]).
  */
 int host_is_ip_address(char const *string)

libsofia-sip-ua/bnf/sofia-sip/bnf.h

@@ -196,7 +196,7 @@ su_inline isize_t span_token_lws(char const *s)
   return e - s;
 }
 
-/** Calculate span of a token characters.  */
+/** Calculate span of token characters.  */
 su_inline isize_t span_token(char const *s)
 {
   char const *e = s;
@@ -205,7 +205,7 @@ su_inline isize_t span_token(char const *s)
   return e - s;
 }
 
-/** Calculate span of a alphabetic characters.  */
+/** Calculate span of alphabetic characters.  */
 su_inline isize_t span_alpha(char const *s)
 {
   char const *e = s;
@@ -214,7 +214,7 @@ su_inline isize_t span_alpha(char const *s)
   return e - s;
 }
 
-/** Calculate span of a digits.  */
+/** Calculate span of digits.  */
 su_inline isize_t span_digit(char const *s)
 {
   char const *e = s;
@@ -241,7 +241,7 @@ su_inline isize_t span_alpha_digit_safe(char const *s)
   return e - s;
 }
 
-/** Calculate span of a characters valid in parameters.  */
+/** Calculate span of characters valid in parameters.  */
 su_inline isize_t span_param(char const *s)
 {
   char const *e = s;
@@ -259,7 +259,7 @@ su_inline isize_t span_word(char const *s)
   return e - s;
 }
 
-/** Calculate span of a unreserved characters.  */
+/** Calculate span of unreserved characters.  */
 su_inline isize_t span_unreserved(char const *s)
 {
   char const *e = s;

libsofia-sip-ua/docs/mainpage.docs

@@ -338,7 +338,7 @@ write functions that fetch the desired bits from a 32 bit field
 with bit operations; not very handy and error prone.
 
 The same aligment problem also arises if you cast for example char
-buffer to a int32_t. You can only read int32_t from the 32bit boundary
+buffer to an int32_t. You can only read int32_t from the 32bit boundary
 on ARM platform. So be careful.
 
 As a conclusion, when using bit-fields and stucture packing, beware
@@ -423,7 +423,7 @@ header-specific data, like header name.
 
 @subsection oo_derived Inheritance and Derived Objects
 
-Inheritance is a object-oriented practice that has limited use in Sofia.
+Inheritance is an object-oriented practice that has limited use in Sofia.
 Most common example of inheritance is use of #su_home_t. Many objects are
 derived from #su_home_t, which means that they can use the various
 home-based memory management functions from <su_alloc.h>.

libsofia-sip-ua/http/sofia-sip/http_parser.h

@@ -75,7 +75,7 @@ SOFIA_BEGIN_DECLS
 #define HTTP_HEADER_CLASS_LIST(c, l, kind) \
   MSG_HEADER_CLASS(http_, c, l, "", k_items, kind, msg_list, http_no)
 
-/** Define a authorization header class */
+/** Define an authorization header class */
 #define HTTP_HEADER_CLASS_AUTH(c, l, kind) \
   MSG_HEADER_CLASS(http_, c, l, "", au_params, kind, msg_auth, http_no)
 

libsofia-sip-ua/iptsec/auth_module.c

@@ -817,7 +817,7 @@ void auth_challenge_digest(auth_mod_t *am,
     as->as_status = ach->ach_status, as->as_phrase = ach->ach_phrase;
 }
 
-/** Construct a info header for @b Digest authentication scheme. */
+/** Construct an info header for @b Digest authentication scheme. */
 void auth_info_digest(auth_mod_t *am,
 		      auth_status_t *as,
 		      auth_challenger_t const *ach)

libsofia-sip-ua/sip/sip_util.c

@@ -1045,7 +1045,7 @@ int sip_response_terminates_dialog(int response_code,
     return terminate_dialog;
 
   case 417:
-    /** @par 417 Uknown Resource-Priority
+    /** @par 417 Unknown Resource-Priority
       The effect of this response on usages
       and dialogs is analgous to that for 420 and 488.  The usage is not
       affected.  The dialog is only affected by a change in its local

tests/test_ops.c

@@ -62,7 +62,7 @@ int save_until_final_response(CONDITION_PARAMS)
 
 /** Save events.
  *
- * Terminate when a event is saved.
+ * Terminate when an event is saved.
  */
 int save_until_received(CONDITION_PARAMS)
 {

utils/Doxyfile.in

@@ -6159,7 +6159,7 @@ PERL_PATH              = /usr/bin/perl
 #---------------------------------------------------------------------------
 
 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
-# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
+# generate an inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
 # or super classes. Setting the tag to NO turns the diagrams off. Note that 
 # this option is superseded by the HAVE_DOT option below. This is only a 
 # fallback. It is recommended to install and use dot, since it yields more