[rtems-docs commit] c-user: Fix typo "cod" -> "code"

[Sebastian Huber]

Module:    rtems-docs
Branch:    master
Commit:    bc66c959004b0eb651f5028401eddaad46ae3e08
Changeset: http://git.rtems.org/rtems-docs/commit/?id=bc66c959004b0eb651f5028401eddaad46ae3e08

Author:    Sebastian Huber <sebastian.huber at embedded-brains.de>
Date:      Tue Apr 27 19:54:12 2021 +0200

c-user: Fix typo "cod" -> "code"

---

 c-user/message/directives.rst | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/c-user/message/directives.rst b/c-user/message/directives.rst
index c154a3b..11ff105 100644
--- a/c-user/message/directives.rst
+++ b/c-user/message/directives.rst
@@ -864,12 +864,13 @@ this message queue.
 
 If the calling task chooses to return immediately and the queue is empty, then
 the directive returns immediately with the :c:macro:`RTEMS_UNSATISFIED` status
-cod.  If the calling task chooses to wait at the message queue and the queue is
-empty, then the calling task is placed on the message wait queue and blocked.
-If the queue was created with the :c:macro:`RTEMS_PRIORITY` option specified,
-then the calling task is inserted into the wait queue according to its
-priority.  But, if the queue was created with the :c:macro:`RTEMS_FIFO` option
-specified, then the calling task is placed at the rear of the wait queue.
+code.  If the calling task chooses to wait at the message queue and the queue
+is empty, then the calling task is placed on the message wait queue and
+blocked.  If the queue was created with the :c:macro:`RTEMS_PRIORITY` option
+specified, then the calling task is inserted into the wait queue according to
+its priority.  But, if the queue was created with the :c:macro:`RTEMS_FIFO`
+option specified, then the calling task is placed at the rear of the wait
+queue.
 
 .. rubric:: RETURN VALUES: