Changeset 1099:6ce5c99a40af in freeDiameter

Timestamp:

May 8, 2013, 9:40:20 PM (11 years ago)

Author:

Thomas Klausner <tk@giga.or.at>

Branch:

default

Phase:

public

Message:

Fix some typos.

Files:

• include/freeDiameter/libfdcore.h (modified) (3 diffs)
• libfdcore/cnxctx.c (modified) (1 diff)
• libfdcore/p_sr.c (modified) (1 diff)
• libfdproto/messages.c (modified) (1 diff)

include/freeDiameter/libfdcore.h

@@ -953 +953 @@
         
         HOOK_MESSAGE_FAILOVER,
-                /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was teared down.
+                /* Hook called when a message that was sent to a peer is being requeued, because e.g. the connection was torn down.
                    In that case the message will go again through the routing process.
                  - {msg} points to the corresponding request message (the answer is discarded). Again, the objects may not have been dictionary resolved. If you
@@ -1022 +1022 @@
 
 
-/* Type if the {permsgdata} ointer. It is up to each extension to define its own structure. This is opaque for the framework. */
+/* Type of the {permsgdata} pointer. It is up to each extension to define its own structure. This is opaque for the framework. */
 struct fd_hook_permsgdata;
 
@@ -1035 +1035 @@
  *
  * PARAMETERS:
- *  permsgdata_new_cb     : function called to initialize a new empty fd_hook_permsgdata structure, when a hook will be called for a message with not structure yet. If the function returns NULL, it will be called again for the next hook.
+ *  permsgdata_new_cb     : function called to initialize a new empty fd_hook_permsgdata structure, when a hook will be called for a message with no structure yet. If the function returns NULL, it will be called again for the next hook.
  *  permsgdata_destroy_cb : function called when a message is being disposed. It should free the resources associated with the fd_hook_permsgdata.
  *  new_handle            : On success, a handler to the registered callback is stored here. 

libfdcore/cnxctx.c

@@ -1756 +1756 @@
         
                 default:
-                        TRACE_DEBUG(INFO, "Unknwon protocol: %d", conn->cc_proto);
+                        TRACE_DEBUG(INFO, "Unknown protocol: %d", conn->cc_proto);
                         ASSERT(0);
                         return ENOTSUP; /* or EINVAL... */

libfdcore/p_sr.c

@@ -196 +196 @@
         } while (1);
 error:  
-        ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label beofre this cause some compilers to complain... */
+        ; /* pthread_cleanup_pop sometimes expands as "} ..." and the label before this cause some compilers to complain... */
         pthread_cleanup_pop( 1 );
         ASSERT(0); /* we have encountered a problem, maybe time to signal the framework to terminate? */

libfdproto/messages.c

@@ -1251 +1251 @@
                 return anscb ? EINVAL : 0; /* we associate with requests only */
         
-        CHECK_PARAMS( (anscb == NULL)    || (msg->msg_cb.anscb == NULL) ); /* We are not overwritting a cb */
-        CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwritting a cb */
+        CHECK_PARAMS( (anscb == NULL)    || (msg->msg_cb.anscb == NULL) ); /* We are not overwriting a cb */
+        CHECK_PARAMS( (expirecb == NULL) || (msg->msg_cb.expirecb == NULL) ); /* We are not overwriting a cb */
         
         /* Associate callback and data with the message, if any */