CLEANUP: assorted typo fixes in the code and comments

This is 25th iteration of typo fixes
diff --git a/doc/SPOE.txt b/doc/SPOE.txt
index ba7aca0..4792963 100644
--- a/doc/SPOE.txt
+++ b/doc/SPOE.txt
@@ -450,7 +450,7 @@
 timeout processing <timeout>
   Set the maximum time to wait for a stream to process an event, i.e to acquire
   a stream to talk with an agent, to encode all messages, to send the NOTIFY
-  frame, to receive the corrsponding acknowledgement and to process all
+  frame, to receive the corresponding acknowledgement and to process all
   actions. It is applied on the stream that handle the client and the server
   sessions.
 
diff --git a/doc/configuration.txt b/doc/configuration.txt
index bb4b4fc..556e977 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -813,7 +813,7 @@
   - a non-nul integer (e.g. '1'), always returns "true".
   - a predicate optionally followed by argument(s) in parenthesis.
   - a condition placed between a pair of parenthesis '(' and ')'
-  - a question mark ('!') preceeding any of the non-empty elements above, and
+  - a question mark ('!') preceding any of the non-empty elements above, and
     which will negate its status.
   - expressions combined with a logical AND ('&&'), which will be evaluated
     from left to right until one returns false
@@ -17798,11 +17798,11 @@
   Returns the ID of the error that might have occurred on the current
   connection. Any strictly positive value of this fetch indicates that the
   connection did not succeed and would result in an error log being output (as
-  decribed in section 8.2.5). See the "fc_conn_err_str" fetch for a full list of
+  described in section 8.2.5). See the "fc_conn_err_str" fetch for a full list of
   error codes and their corresponding error message.
 
 fc_conn_err_str : string
-  Returns an error message decribing what problem happened on the current
+  Returns an error message describing what problem happened on the current
   connection, resulting in a connection failure. This string corresponds to the
   "message" part of the error log format (see section 8.2.5). See below for a
   full list of error codes and their corresponding error messages :
diff --git a/doc/internals/fd-migration.txt b/doc/internals/fd-migration.txt
index 010431d..aaddad3 100644
--- a/doc/internals/fd-migration.txt
+++ b/doc/internals/fd-migration.txt
@@ -60,7 +60,7 @@
       allowed to run anymore. The tasks retrieve their execution context from
       the scheduler in the arguments, but will check the tasks' context from
       the structure under the lock to detect this possible change, and abort.
-    - at this point the takeover suceeded, the idle_conns_lock is released and
+    - at this point the takeover succeeded, the idle_conns_lock is released and
       the connection and its FD are now owned by the caller
 
   2) poll report: happens on late rx, shutdown or error on idle conns
@@ -81,7 +81,7 @@
     - check the task/tasklet's context to verify that no recently completed
       takeover() stole the connection. If it's NULL, the connection was lost,
       the lock is released and the task/tasklet killed. Otherwise it is
-      guaranted that no other thread may use that connection (current takeover
+      guaranteed that no other thread may use that connection (current takeover
       candidates are waiting on the lock, previous owners waking from poll()
       lost their bit in the thread_mask and will not touch the FD).
     - the connection is removed from the idle conns list. From this point on,