5 files changed, 35 insertions, 14 deletions
diff --git a/c-user/fatal-error/background.rst b/c-user/fatal-error/background.rst
index 6932846..e3d7320 100644
--- a/c-user/fatal-error/background.rst
+++ b/c-user/fatal-error/background.rst
@@ -316,13 +316,13 @@ INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT (31)
         }
 
 INTERNAL_ERROR_RTEMS_INIT_TASK_CREATE_FAILED (32)
-    Creation of an RTEMS initialization task failed.  This fatal error may
+    The creation of the RTEMS initialization task failed.  This fatal error may
     occur during system initialization.  It is an application configuration
     error.
 
 INTERNAL_ERROR_POSIX_INIT_THREAD_CREATE_FAILED (33)
-    Creation of a POSIX initialization thread failed.  This fatal error may
-    occur during system initialization.  It is an application configuration
+    The creation of the POSIX initialization thread failed.  This fatal error
+    may occur during system initialization.  It is an application configuration
     error.
 
 INTERNAL_ERROR_LIBIO_STDOUT_FD_OPEN_FAILED (36)
@@ -356,3 +356,25 @@ INTERNAL_ERROR_TOO_LARGE_TLS_SIZE (41)
     :ref:`CONFIGURE_MAXIMUM_THREAD_LOCAL_STORAGE_SIZE <CONFIGURE_MAXIMUM_THREAD_LOCAL_STORAGE_SIZE>`.
     You can get the thread-local storage size of an application using the RTEMS
     tool ``rtems-execinfo``.
+
+INTERNAL_ERROR_RTEMS_INIT_TASK_CONSTRUCT_FAILED (42)
+    The construction of the RTEMS initialization task failed.  This fatal error
+    may occur during system initialization.  It is an application configuration
+    error.
+
+INTERNAL_ERROR_IDLE_THREAD_CREATE_FAILED (43)
+    The creation of an IDLE task failed.  This fatal error may occur during
+    system initialization.  It happens if a task create extension fails for an
+    IDLE task.
+
+INTERNAL_ERROR_NO_MEMORY_FOR_IDLE_TASK_STORAGE (44)
+    There was not enough memory available to allocate an IDLE task stack.  This
+    fatal error may occur during system initialization.  It is an application
+    configuration error.
+
+INTERNAL_ERROR_IDLE_THREAD_STACK_TOO_SMALL (45)
+    The task stack size of an IDLE task would have been less than the
+    configured stack size for IDLE tasks, see
+    :ref:`CONFIGURE_IDLE_TASK_STACK_SIZE <CONFIGURE_IDLE_TASK_STACK_SIZE>`.
+    This fatal error may occur during system initialization.  It is an
+    application configuration error.
diff --git a/c-user/fatal-error/directives.rst b/c-user/fatal-error/directives.rst
index 98ce209..434172f 100644
--- a/c-user/fatal-error/directives.rst
+++ b/c-user/fatal-error/directives.rst
@@ -1,6 +1,6 @@
 .. SPDX-License-Identifier: CC-BY-SA-4.0
 
-.. Copyright (C) 2015, 2021 embedded brains GmbH (http://www.embedded-brains.de)
+.. Copyright (C) 2015, 2021 embedded brains GmbH & Co. KG
 .. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
 
 .. This file is part of the RTEMS quality process and was automatically
@@ -116,10 +116,10 @@ Prints the message and invokes the fatal error handler.
 
 .. rubric:: DESCRIPTION:
 
-This directive prints a message via :c:func:`printk` specified by the ``fmt``
-parameter and optional parameters and then invokes the fatal error handler.
-The fatal source is set to :c:macro:`RTEMS_FATAL_SOURCE_PANIC`.  The fatal code
-is set to the value of the ``fmt`` parameter value.
+This directive prints a message via :ref:`InterfacePrintk` specified by the
+``fmt`` parameter and optional parameters and then invokes the fatal error
+handler.  The fatal source is set to :c:macro:`RTEMS_FATAL_SOURCE_PANIC`.  The
+fatal code is set to the value of the ``fmt`` parameter value.
 
 .. rubric:: CONSTRAINTS:
 
@@ -216,7 +216,7 @@ Prints the exception frame.
 .. rubric:: DESCRIPTION:
 
 The exception frame is printed in an architecture-dependent format using
-:c:func:`printk`.
+:ref:`InterfacePrintk`.
 
 .. Generated from spec:/rtems/fatal/if/source-text
 
diff --git a/c-user/fatal-error/index.rst b/c-user/fatal-error/index.rst
index 89cbe30..40eca3b 100644
--- a/c-user/fatal-error/index.rst
+++ b/c-user/fatal-error/index.rst
@@ -1,6 +1,6 @@
 .. SPDX-License-Identifier: CC-BY-SA-4.0
 
-.. Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de)
+.. Copyright (C) 2021 embedded brains GmbH & Co. KG
 
 .. index:: fatal errors
 
diff --git a/c-user/fatal-error/introduction.rst b/c-user/fatal-error/introduction.rst
index ff86922..fc310f4 100644
--- a/c-user/fatal-error/introduction.rst
+++ b/c-user/fatal-error/introduction.rst
@@ -1,6 +1,6 @@
 .. SPDX-License-Identifier: CC-BY-SA-4.0
 
-.. Copyright (C) 2015, 2021 embedded brains GmbH (http://www.embedded-brains.de)
+.. Copyright (C) 2015, 2021 embedded brains GmbH & Co. KG
 .. Copyright (C) 1988, 2008 On-Line Applications Research Corporation (OAR)
 
 .. This file is part of the RTEMS quality process and was automatically
diff --git a/c-user/fatal-error/operations.rst b/c-user/fatal-error/operations.rst
index 77753d6..6d03a26 100644
--- a/c-user/fatal-error/operations.rst
+++ b/c-user/fatal-error/operations.rst
@@ -40,12 +40,11 @@ The fatal extensions are called with three parameters:
 
 - the fatal source,
 
-- a legacy parameter which is always false, and
+- a legacy parameter which is always set to :c:macro:`false`, and
 
 - an error code with a fatal source dependent content.
 
-Once all fatal extensions executed, the error information will be stored to
-:c:data:`_Internal_errors_What_happened` and the system state is set to
+Once all fatal extensions executed, the system state is set to
 :c:macro:`SYSTEM_STATE_TERMINATED`.
 
 The final step is to call the CPU port specific :c:func:`_CPU_Fatal_halt()`.