--- a/INSTALL.OSX	Tue Mar 12 17:43:30 2013 +0100
+++ b/INSTALL.OSX	Thu Mar 14 17:31:00 2013 +0100
@@ -42,7 +42,7 @@
     $ brew install mercurial cmake gnutls libgcrypt postgres mysql libidn
 
    Notes:
-    * GNU IDN (libidn) is optional, see bellow
+    * GNU IDN (libidn) is optional, see below
     * When libusrsctp package is available, you can use it as well.
 
 3) Retrieve source code:

--- a/INSTALL.Ubuntu	Tue Mar 12 17:43:30 2013 +0100
+++ b/INSTALL.Ubuntu	Thu Mar 14 17:31:00 2013 +0100
@@ -72,7 +72,7 @@
 
 ===========================================
 
-freeDiameter has been tested on the following distributions (compiled from source as described bellow):
+freeDiameter has been tested on the following distributions (compiled from source as described below):
 Ubuntu Intrepid, Jaunty, Karmic, Lucid, Maverick, Natty. 
 Debian Lenny (with small patch, see ticket #24).
 

--- a/README	Tue Mar 12 17:43:30 2013 +0100
+++ b/README	Thu Mar 14 17:31:00 2013 +0100
@@ -18,7 +18,7 @@
  - libfdcore : this shared library contains the core of the framework. It establishes 
       the network connections with other Diameter peers and performs the tasks described 
       in Diameter Base Protocol, such as watchdogs, basic routing, ... It also handles 
-      the loading of extensions (see bellow).
+      the loading of extensions (see below).
       
  - freeDiameterd : this simple daemon parses the command line and initializes the
       freeDiameter framework. Use it for your Diameter server & agent components.

--- a/contrib/OpenWRT/packages/freeDiameter/Makefile	Tue Mar 12 17:43:30 2013 +0100
+++ b/contrib/OpenWRT/packages/freeDiameter/Makefile	Thu Mar 14 17:31:00 2013 +0100
@@ -123,7 +123,7 @@
 	echo "# test_app.fdx provided in freeDiameter-test package:" \
 							>> $(1)/etc/freeDiameter/freeDiameter.conf
 	echo "# LoadExtension = \"test_app.fdx\";"	>> $(1)/etc/freeDiameter/freeDiameter.conf
-	echo "## Add overrides bellow this point" 	>> $(1)/etc/freeDiameter/freeDiameter.conf
+	echo "## Add overrides below this point" 	>> $(1)/etc/freeDiameter/freeDiameter.conf
 
 	
 	$(INSTALL_CONF) \

--- a/contrib/app_acct_tools/display_results.php	Tue Mar 12 17:43:30 2013 +0100
+++ b/contrib/app_acct_tools/display_results.php	Thu Mar 14 17:31:00 2013 +0100
@@ -3,7 +3,7 @@
 # The copyright of this file is the same as the freeDiameter project. Licence is BSD.
 
 # This file should no be called directly; 
-# instead it should be included from another script that sets its parameters as described bellow.
+# instead it should be included from another script that sets its parameters as described below.
 
 ## $USERS  
 # An array of the user names to display; the empty array will display all users.

--- a/doc/app_redirect.conf.sample	Tue Mar 12 17:43:30 2013 +0100
+++ b/doc/app_redirect.conf.sample	Thu Mar 14 17:31:00 2013 +0100
@@ -11,7 +11,7 @@
 
 ## default_redirect_cache_time
 # Specify the default value for Redirect-Max-Cache-Time.
-# This value can be overwriten for each rule as specified bellow.
+# This value can be overwriten for each rule as specified below.
 # If this value is not specified, the default is:
 #default_redirect_cache_time = 86400;  ## => 1 day
 

--- a/doc/freediameter.conf.sample	Tue Mar 12 17:43:30 2013 +0100
+++ b/doc/freediameter.conf.sample	Thu Mar 14 17:31:00 2013 +0100
@@ -193,7 +193,7 @@
 #  In addition to incoming connections, the local peer can
 # be configured to establish and maintain connections to some 
 # Diameter nodes and allow connections from these nodes.
-#  This is achieved with the ConnectPeer directive described bellow.
+#  This is achieved with the ConnectPeer directive described below.
 #
 # Note that the configured Diameter Id MUST match
 # the information received inside CEA, or the connection will be aborted.

--- a/extensions/app_radgw/md5.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_radgw/md5.c	Thu Mar 14 17:31:00 2013 +0100
@@ -2,7 +2,7 @@
 /* freeDiameter author note:
  *  The content from this file comes directly from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  *  In addition to this notice, only the #include directives have been modified.
  */
 #include "rgw_common.h"

--- a/extensions/app_radgw/md5.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_radgw/md5.h	Thu Mar 14 17:31:00 2013 +0100
@@ -2,7 +2,7 @@
 /* freeDiameter author note:
  *  The content from this file comes directly from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  */
 
 /*********************************************************************************/

--- a/extensions/app_radgw/radius.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_radgw/radius.c	Thu Mar 14 17:31:00 2013 +0100
@@ -36,7 +36,7 @@
 /* freeDiameter author note:
  *  The content from this file comes for the main part from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  * The modifications to this file are placed under the copyright of the freeDiameter project.
  */
 

--- a/extensions/app_radgw/radius.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_radgw/radius.h	Thu Mar 14 17:31:00 2013 +0100
@@ -37,7 +37,7 @@
 /* freeDiameter author note:
  *  The content from this file comes mostly from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  * The changes to this file are placed under the copyright of the freeDiameter project.
  */
 

--- a/extensions/app_radgw/rgwx_auth.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_radgw/rgwx_auth.c	Thu Mar 14 17:31:00 2013 +0100
@@ -1098,7 +1098,7 @@
         	 the Translation Agent receiving the subsequent RADIUS Access-
         	 Request will have access to the Session Identifier and be able
         	 to set the Destination-Host to the correct value.
-		 	-> done here bellow
+		 	-> done here below
 		 
 	      -  If the Command-Code is set to AA-Answer, the Diameter Session-
         	 Id AVP is saved in a new RADIUS Class attribute whose format

--- a/extensions/app_sip/app_sip.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_sip/app_sip.c	Thu Mar 14 17:31:00 2013 +0100
@@ -121,7 +121,7 @@
 	
 	
 	
-	//We set usefull AVPs 
+	//We set useful AVPs 
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Auth-Session-State", &sip_dict.Auth_Session_State, ENOENT) );
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Auth-Application-Id", &sip_dict.Auth_Application_Id, ENOENT) );
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Destination-Host", &sip_dict.Destination_Host, ENOENT) );

--- a/extensions/app_sip/app_sip.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_sip/app_sip.h	Thu Mar 14 17:31:00 2013 +0100
@@ -217,7 +217,7 @@
 	char *nonce;
 };
 
-//Storage for some usefull AVPs
+//Storage for some useful AVPs
 struct app_sip_dict{
 	struct dict_object * Auth_Session_State;
 	struct dict_object * Auth_Application_Id;

--- a/extensions/app_sip/md5.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_sip/md5.c	Thu Mar 14 17:31:00 2013 +0100
@@ -2,7 +2,7 @@
 /* freeDiameter author note:
  *  The content from this file comes directly from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  *  In addition to this notice, only the #include directives have been modified.
  */
 

--- a/extensions/app_sip/md5.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/app_sip/md5.h	Thu Mar 14 17:31:00 2013 +0100
@@ -2,7 +2,7 @@
 /* freeDiameter author note:
  *  The content from this file comes directly from the hostap project.
  * It is redistributed under the terms of the BSD license, as allowed
- * by the original copyright reproduced bellow.
+ * by the original copyright reproduced below.
  *  The file has not been modified, except for this notice.
  */
 /*********************************************************************************/

--- a/extensions/dbg_interactive/dictionary.i	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/dbg_interactive/dictionary.i	Thu Mar 14 17:31:00 2013 +0100
@@ -196,7 +196,7 @@
 
 /* The following wrapper leaks memory each time an union avp_value is assigned an octet string.
  TODO: fix this leak by better understanding SWIG... 
-   -- the alternative is to uncomment the "free" statements bellow, but then it is easy to
+   -- the alternative is to uncomment the "free" statements below, but then it is easy to
    create a segmentation fault by assigning first an integer, then an octetstring.
  */
 %extend avp_value {

--- a/extensions/test_netemul/tne_process.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/test_netemul/tne_process.c	Thu Mar 14 17:31:00 2013 +0100
@@ -57,7 +57,7 @@
 static pthread_cond_t  cnd = PTHREAD_COND_INITIALIZER;
 static pthread_t       thr = (pthread_t)NULL;
 
-/* The lists bellow are all protected by the same mutex mtx */
+/* The lists below are all protected by the same mutex mtx */
 static struct fd_list input = FD_LIST_INITIALIZER(input); /* messages received from network */
 static struct fd_list forlat = FD_LIST_INITIALIZER(forlat); /* messages after duplicate filter */
 static struct fd_list waitlist = FD_LIST_INITIALIZER(waitlist); /* messages waiting for sending */

--- a/extensions/test_sip/test_sip.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/test_sip/test_sip.c	Thu Mar 14 17:31:00 2013 +0100
@@ -126,7 +126,7 @@
 	
 	
 	
-	//We set usefull AVPs 
+	//We set useful AVPs 
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Auth-Session-State", &sip_dict.Auth_Session_State, ENOENT) );
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Auth-Application-Id", &sip_dict.Auth_Application_Id, ENOENT) );
 	CHECK_FCT( fd_dict_search( fd_g_config->cnf_dict, DICT_AVP, AVP_BY_NAME, "Destination-Host", &sip_dict.Destination_Host, ENOENT) );

--- a/extensions/test_sip/test_sip.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/extensions/test_sip/test_sip.h	Thu Mar 14 17:31:00 2013 +0100
@@ -54,7 +54,7 @@
 };
 extern struct ts_conf * ts_conf;
 
-//Storage for some usefull AVPs
+//Storage for some useful AVPs
 struct sip_dict{
 	struct dict_object * Auth_Session_State;
 	struct dict_object * Auth_Application_Id;

--- a/include/freeDiameter/libfdcore.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/include/freeDiameter/libfdcore.h	Thu Mar 14 17:31:00 2013 +0100
@@ -224,7 +224,7 @@
 #define STATE_STR(state) \
 	(((unsigned)(state)) <= STATE_MAX ? peer_state_str[((unsigned)(state)) ] : "<Invalid>")
 
-/* Constants for the peer_info structure bellow */
+/* Constants for the peer_info structure below */
 #define PI_P3_DEFAULT	0	/* Use any available protocol */
 #define PI_P3_IP	1	/* Use only IP to connect to this peer */
 #define PI_P3_IPv6	2	/* resp, IPv6 */
@@ -405,7 +405,7 @@
  * FUNCTION:	fd_peer_validate_register
  *
  * PARAMETERS:
- *  peer_validate 	: Callback as defined bellow.
+ *  peer_validate 	: Callback as defined below.
  *
  * DESCRIPTION: 
  *  Add a callback to authorize / reject incoming peer connections.
@@ -588,10 +588,10 @@
  * (*) FWD messages details:
  *   - The process is the same as for IN messages, until the routing-in threads makes its decision that the message is not handled locally.
  *   - If the local peer does not relay message, an error DIAMETER_APPLICATION_UNSUPPORTED is returned.
- *   - All callbacks registered with fd_rt_fwd_register are called for the message (see bellow).
+ *   - All callbacks registered with fd_rt_fwd_register are called for the message (see below).
  *     - these callbacks will typically do proxying work. Note that adding the route-record is handled by the daemon.
  *   - Once all callbacks have been called, the message is queued in the global fd_g_outgoing queue.
- *   - The remaining processing is the same as for OUT messages, as described bellow.
+ *   - The remaining processing is the same as for OUT messages, as described below.
  *
  * (*) OUT messages details:
  *   - The message are picked from fd_g_outgoing (they are queued there as result of forwarding process or call to fd_msg_send.)
@@ -601,7 +601,7 @@
  *      - remove also all peers that have previously replied an error message for this message.
  *   - If the list is empty, create an error UNABLE_TO_DELIVER (note: should we trig dynamic discovery here???) and reply.
  *   - Otherwise, call all callbacks registered by function fd_rt_out_register, with the list of peers and the message.
- *   - Order the resulting list of peers by score (see bellow), and sent the message to the peer with highest (positive) score.
+ *   - Order the resulting list of peers by score (see below), and sent the message to the peer with highest (positive) score.
  *    - in case the peer is no longer in the "OPEN" state, send the message to the second peer in the list.
  *      - if no peer is in OPEN state anymore, restart the process of creating the list.
  *   - Once a peer has been selected, the message is queued into that peer's outgoing queue.
@@ -625,7 +625,7 @@
  * FUNCTION:	fd_rt_fwd_register
  *
  * PARAMETERS:
- *  rt_fwd_cb	  : The callback function to register (see prototype bellow).
+ *  rt_fwd_cb	  : The callback function to register (see prototype below).
  *  cbdata	  : Pointer to pass to the callback when it is called. The data is opaque to the daemon.
  *  dir           : One of the RT_FWD_* directions defined above.
  *  handler       : On success, a handler to the registered callback is stored here. 
@@ -702,7 +702,7 @@
  * FUNCTION:	fd_rt_out_register
  *
  * PARAMETERS:
- *  rt_out_cb	  : The callback function to register (see prototype bellow).
+ *  rt_out_cb	  : The callback function to register (see prototype below).
  *  cbdata	  : Pointer to pass to the callback when it is called. The data is opaque to the daemon.
  *  priority      : Order for calling this callback. The callbacks are called in reverse priority order (higher priority = called sooner).
  *  handler       : On success, a handler to the registered callback is stored here. 

--- a/include/freeDiameter/libfdproto.h	Tue Mar 12 17:43:30 2013 +0100
+++ b/include/freeDiameter/libfdproto.h	Thu Mar 14 17:31:00 2013 +0100
@@ -283,7 +283,7 @@
 #define TRACE_DEBUG(level,format,args... ) \
 	TRACE(FD_LOG_DEBUG,(level),format,##args)
 
-/* Report a normal message that is usefull for normal admin monitoring */
+/* Report a normal message that is useful for normal admin monitoring */
 #define TRACE_NOTICE(format,args... ) \
 	TRACE(FD_LOG_NOTICE,INFO,format,##args)
 
@@ -311,7 +311,7 @@
 	TRACE_DEBUG(NONE, " -- debug checkpoint %d -- ", fd_breakhere());
 int fd_breakhere(void);
 
-/* Helper for tracing the CHECK_* macros bellow -- very very verbose code execution! */
+/* Helper for tracing the CHECK_* macros below -- very very verbose code execution! */
 #define TRACE_DEBUG_ALL( str ) 	\
 	TRACE_DEBUG(CALL, str );
 
@@ -893,7 +893,7 @@
  *  dict	: Pointer to the dictionnary where the object is created
  *  type 	: What kind of object must be created
  *  data 	: pointer to the data for the object. 
- *          	 type parameter is used to determine the type of data (see bellow for detail).
+ *          	 type parameter is used to determine the type of data (see below for detail).
  *  parent 	: a reference to a parent object, if needed.
  *  ref 	: upon successful creation, reference to new object is stored here if !null.
  *
@@ -917,14 +917,14 @@
  * PARAMETERS:
  *  dict	: Pointer to the dictionnary where the object is searched
  *  type 	: type of object that is being searched
- *  criteria 	: how the object must be searched. See object-related sections bellow for more information.
+ *  criteria 	: how the object must be searched. See object-related sections below for more information.
  *  what 	: depending on criteria, the data that must be searched.
  *  result 	: On successful return, pointer to the object is stored here.
  *  retval	: this value is returned if the object is not found and result is not NULL.
  *
  * DESCRIPTION: 
  *   Perform a search in the dictionary. 
- *   See the object-specific sections bellow to find how to look for each objects.
+ *   See the object-specific sections below to find how to look for each objects.
  *   If the "result" parameter is NULL, the function is used to check if an object is in the dictionary.
  *   Otherwise, a reference to the object is stored in result if found.
  *   If result is not NULL and the object is not found, retval is returned (should be 0 or ENOENT usually)
@@ -994,7 +994,7 @@
 enum {
 	VENDOR_BY_ID = 10,	/* "what" points to a vendor_id_t */
 	VENDOR_BY_NAME,		/* "what" points to a char * */
-	VENDOR_OF_APPLICATION	/* "what" points to a struct dict_object containing an application (see bellow) */
+	VENDOR_OF_APPLICATION	/* "what" points to a struct dict_object containing an application (see below) */
 };
 
 /***
@@ -1064,8 +1064,8 @@
 enum {
 	APPLICATION_BY_ID = 20,		/* "what" points to a application_id_t */
 	APPLICATION_BY_NAME,		/* "what" points to a char * */
-	APPLICATION_OF_TYPE,		/* "what" points to a struct dict_object containing a type object (see bellow) */
-	APPLICATION_OF_COMMAND		/* "what" points to a struct dict_object containing a command (see bellow) */
+	APPLICATION_OF_TYPE,		/* "what" points to a struct dict_object containing a type object (see below) */
+	APPLICATION_OF_COMMAND		/* "what" points to a struct dict_object containing a command (see below) */
 };
 
 /***
@@ -1205,7 +1205,7 @@
 /* The criteria for searching a type object in the dictionary */
 enum {
 	TYPE_BY_NAME = 30,		/* "what" points to a char * */
-	TYPE_OF_ENUMVAL,		/* "what" points to a struct dict_object containing an enumerated constant (DICT_ENUMVAL, see bellow). */
+	TYPE_OF_ENUMVAL,		/* "what" points to a struct dict_object containing an enumerated constant (DICT_ENUMVAL, see below). */
 	TYPE_OF_AVP			/* "what" points to a struct dict_object containing an AVP object. */
 };
 
@@ -1279,7 +1279,7 @@
 
 /* The criteria for searching a constant in the dictionary */
 enum {
-	ENUMVAL_BY_STRUCT = 40,	/* "what" points to a struct dict_enumval_request as defined bellow */
+	ENUMVAL_BY_STRUCT = 40,	/* "what" points to a struct dict_enumval_request as defined below */
 	ENUMVAL_BY_NAME,	/* This cannot be used for researches */
 	ENUMVAL_BY_VALUE	/* This cannot be used for researches */
 };
@@ -1401,11 +1401,11 @@
 	AVP_BY_CODE = 50,	/* "what" points to an avp_code_t, vendor is always 0 */
 	AVP_BY_NAME,		/* "what" points to a char *, vendor is always 0 */
 	AVP_BY_NAME_ALL_VENDORS,/* "what" points to a string. Might be quite slow... */
-	AVP_BY_STRUCT,		/* "what" points to a struct dict_avp_request_ex (see bellow) */
+	AVP_BY_STRUCT,		/* "what" points to a struct dict_avp_request_ex (see below) */
 			
 	/* kept for backward compatibility, better use AVP_BY_STRUCT above instead */
-	AVP_BY_CODE_AND_VENDOR,	/* "what" points to a struct dict_avp_request (see bellow), where avp_vendor and avp_code are set */
-	AVP_BY_NAME_AND_VENDOR	/* "what" points to a struct dict_avp_request (see bellow), where avp_vendor and avp_name are set */
+	AVP_BY_CODE_AND_VENDOR,	/* "what" points to a struct dict_avp_request (see below), where avp_vendor and avp_code are set */
+	AVP_BY_NAME_AND_VENDOR	/* "what" points to a struct dict_avp_request (see below), where avp_vendor and avp_name are set */
 };
 
 /* Struct used for some researchs */
@@ -1639,7 +1639,7 @@
 
 /* The criteria for searching a rule in the dictionary */
 enum {
-	RULE_BY_AVP_AND_PARENT = 70	/* "what" points to a struct dict_rule_request -- see bellow. This is used to query "what is the rule for this AVP in this group?" */
+	RULE_BY_AVP_AND_PARENT = 70	/* "what" points to a struct dict_rule_request -- see below. This is used to query "what is the rule for this AVP in this group?" */
 };
 
 /* Structure for querying the dictionary about a rule */
@@ -1852,7 +1852,7 @@
  *  session	  : The location where the session object will be created upon success.
  *  diamid	  : a Diameter Identity, or NULL.
  *  diamidlen	  : if diamid is \0-terminated, this can be 0. Otherwise, the length of diamid.
- *  opt           : Additional string, or NULL. Usage is described bellow.
+ *  opt           : Additional string, or NULL. Usage is described below.
  *  optlen	  : if opt is \0-terminated, this can be 0. Otherwise, the length of opt.
  *
  * DESCRIPTION: 
@@ -2135,7 +2135,7 @@
 	MSG_BRW_WALK		/* This is equivalent to FIRST_CHILD or NEXT or PARENT->next, first that is not NULL. Use this to walk inside all AVPs. */
 };
 
-/* Some flags used in the functions bellow */
+/* Some flags used in the functions below */
 #define AVPFL_SET_BLANK_VALUE	   0x01	/* When creating an AVP, initialize its value to a blank area */
 #define AVPFL_SET_RAWDATA_FROM_AVP 0x02 /* When creating an AVP, initialize its rawdata area from an existing AVP -- it is only blank padding (for error reporting) */
 #define AVPFL_MAX		   AVPFL_SET_RAWDATA_FROM_AVP	/* The biggest valid flag value */

--- a/libfdcore/p_psm.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/libfdcore/p_psm.c	Thu Mar 14 17:31:00 2013 +0100
@@ -53,7 +53,7 @@
 but, if we require at least 1 DWR/DWA exchange to be always performed
 after the CER/CEA exchange (and initiated by the peer that sent the
 CEA), we have a simple way to deal with our ordering problem, as resumed
-bellow. Peers are: [i]nitiator, [r]esponder.
+below. Peers are: [i]nitiator, [r]esponder.
  (1) [i] SCTP connection attempt.
  (2) [r] accept the connection.
  (3) [i,r] (if secure port) DTLS handshake, close on failure.

--- a/libfdcore/peers.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/libfdcore/peers.c	Thu Mar 14 17:31:00 2013 +0100
@@ -541,7 +541,7 @@
 		/* Insert the new peer in the list (the PSM will take care of setting the expiry after validation) */
 		fd_list_insert_after( li_inf, &peer->p_hdr.chain );
 		
-		/* Start the PSM, which will receive the event bellow */
+		/* Start the PSM, which will receive the event below */
 		CHECK_FCT_DO( ret = fd_psm_begin(peer), goto out );
 	} else {
 		/* Check if the peer is in zombie state */

--- a/libfdproto/dictionary.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/libfdproto/dictionary.c	Thu Mar 14 17:31:00 2013 +0100
@@ -78,11 +78,11 @@
 	struct fd_list		list[NB_LISTS_PER_OBJ];/* used to chain objects.*/
 	/* More information about the lists :
 	
-	 - the use for each list depends on the type of object. See detail bellow.
+	 - the use for each list depends on the type of object. See detail below.
 	 
 	 - a sentinel for a list has its 'o' field cleared. (this is the criteria to detect end of a loop)
 	 
-	 - The lists are always ordered. The criteria are described bellow. the functions to order them are referenced in dict_obj_info
+	 - The lists are always ordered. The criteria are described below. the functions to order them are referenced in dict_obj_info
 	 
 	 - The dict_lock must be held for any list operation.
 	 

--- a/tests/testfifo.c	Tue Mar 12 17:43:30 2013 +0100
+++ b/tests/testfifo.c	Thu Mar 14 17:31:00 2013 +0100
@@ -301,7 +301,7 @@
 			nbr_threads = NBR_THREADS;
 		} else {
 			TRACE_DEBUG(INFO, "Local limit on number of threads: %d", nbr_threads);
-			/* The local limit is bellow NBR_THREADS */
+			/* The local limit is below NBR_THREADS */
 			nbr_threads = (nbr_threads / 2) - 1;
 			/* Ensure we create at least a few threads! */
 			CHECK( 1, nbr_threads >= 10 ? 1 : 0 );