Changeset 972:ce3cacbbccc9 in freeDiameter for include/freeDiameter/libfdcore.h

Timestamp:

Mar 15, 2013, 1:31:00 AM (11 years ago)

Author:

Thomas Klausner <tk@giga.or.at>

Branch:

default

Phase:

public

Message:

Fix some typos.

File:

• include/freeDiameter/libfdcore.h (modified) (6 diffs)

include/freeDiameter/libfdcore.h

@@ -225 +225 @@
         (((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 */
@@ -406 +406 @@
  *
  * PARAMETERS:
- *  peer_validate       : Callback as defined bellow.
+ *  peer_validate       : Callback as defined below.
  *
  * DESCRIPTION: 
@@ -589 +589 @@
  *   - 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:
@@ -602 +602 @@
  *   - 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.
@@ -626 +626 @@
  *
  * 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.
@@ -703 +703 @@
  *
  * 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).