c-user: Use rubric for configuration options

Clear the page for each configuration options similar to the directives.

Use a rubric instead of a definition list for the application
configuration options similar to the directive documentation pages.  For
direcives and application configuration options use the same rubric
order.

Generalize value constraints to constraints.

This patch does not change hand written content.

1 files changed, 330 insertions, 245 deletions

diff --git a/c-user/config/posix-api.rst b/c-user/config/posix-api.rst
index 148f895..12e6410 100644
--- a/c-user/config/posix-api.rst
+++ b/c-user/config/posix-api.rst
@@ -30,6 +30,10 @@ build configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-keys
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_KEYS
 
 .. _CONFIGURE_MAXIMUM_POSIX_KEYS:
@@ -37,42 +41,51 @@ build configuration option.
 CONFIGURE_MAXIMUM_POSIX_KEYS
 ----------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_KEYS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_KEYS``
+
+.. rubric:: OPTION TYPE:
+
+This configuration option is an integer define.
 
-OPTION TYPE:
-    This configuration option is an integer define.
+.. rubric:: DEFAULT VALUE:
 
-DEFAULT VALUE:
-    The default value is 0.
+The default value is 0.
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+.. rubric:: DESCRIPTION:
 
-    * It shall be greater than or equal to zero.
+The value of this configuration option defines the maximum number of POSIX
+API Keys that can be concurrently active.
 
-    * It shall be less than or equal to 65535.
+.. rubric:: NOTES:
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+.. rubric:: CONSTRAINTS:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Keys that can be concurrently active.
+The following constraints apply to this configuration option:
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-key-value-pairs
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS
 
 .. _CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS:
@@ -80,48 +93,57 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS
 ---------------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS``
+
+.. rubric:: OPTION TYPE:
+
+This configuration option is an integer define.
+
+.. rubric:: DEFAULT VALUE:
 
-OPTION TYPE:
-    This configuration option is an integer define.
+The default value is
+:ref:`CONFIGURE_MAXIMUM_POSIX_KEYS` *
+( :ref:`CONFIGURE_MAXIMUM_TASKS` +
+:ref:`CONFIGURE_MAXIMUM_POSIX_THREADS` ).
 
-DEFAULT VALUE:
-    The default value is
-    :ref:`CONFIGURE_MAXIMUM_POSIX_KEYS` *
-    ( :ref:`CONFIGURE_MAXIMUM_TASKS` +
-    :ref:`CONFIGURE_MAXIMUM_POSIX_THREADS` ).
+.. rubric:: DESCRIPTION:
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+The value of this configuration option defines the maximum number of key
+value pairs used by POSIX API Keys that can be concurrently active.
 
-    * It shall be greater than or equal to zero.
+.. rubric:: NOTES:
 
-    * It shall be less than or equal to 65535.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+A key value pair is created by :c:func:`pthread_setspecific` if the value
+is not `NULL <https://en.cppreference.com/w/c/types/NULL>`_, otherwise it is deleted.
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+.. rubric:: CONSTRAINTS:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of key
-    value pairs used by POSIX API Keys that can be concurrently active.
+The following constraints apply to this configuration option:
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+* The value of the configuration option shall be greater than or equal to zero.
 
-    A key value pair is created by :c:func:`pthread_setspecific` if the value
-    is not `NULL <https://en.cppreference.com/w/c/types/NULL>`_, otherwise it is deleted.
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-message-queues
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
 
 .. _CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES:
@@ -129,48 +151,58 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES
 --------------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES``
+.. rubric:: CONSTANT:
 
-OPTION TYPE:
-    This configuration option is an integer define.
+``CONFIGURE_MAXIMUM_POSIX_MESSAGE_QUEUES``
 
-DEFAULT VALUE:
-    The default value is 0.
+.. rubric:: OPTION TYPE:
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+This configuration option is an integer define.
 
-    * It shall be greater than or equal to zero.
+.. rubric:: DEFAULT VALUE:
 
-    * It shall be less than or equal to 65535.
+The default value is 0.
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+.. rubric:: DESCRIPTION:
 
-    * It shall be small enough so that the RTEMS Workspace size calculation
-      carried out by ``<rtems/confdefs.h>`` does not overflow an integer of
-      type `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+The value of this configuration option defines the maximum number of POSIX
+API Message Queues that can be concurrently active.
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+.. rubric:: NOTES:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Message Queues that can be concurrently active.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.  You have to account for the memory used to
+store the messages of each message queue, see
+:ref:`CONFIGURE_MESSAGE_BUFFER_MEMORY`.
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.  You have to account for the memory used to
-    store the messages of each message queue, see
-    :ref:`CONFIGURE_MESSAGE_BUFFER_MEMORY`.
+.. rubric:: CONSTRAINTS:
+
+The following constraints apply to this configuration option:
+
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option shall be small enough so that the RTEMS
+  Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-queued-signals
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
 
 .. _CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS:
@@ -178,45 +210,56 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS
 --------------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_QUEUED_SIGNALS``
 
-OPTION TYPE:
-    This configuration option is an integer define.
+.. rubric:: OPTION TYPE:
 
-DEFAULT VALUE:
-    The default value is 0.
+This configuration option is an integer define.
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+.. rubric:: DEFAULT VALUE:
 
-    * It shall be greater than or equal to zero.
+The default value is 0.
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+.. rubric:: DESCRIPTION:
 
-    * It shall be small enough so that the RTEMS Workspace size calculation
-      carried out by ``<rtems/confdefs.h>`` does not overflow an integer of
-      type `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+The value of this configuration option defines the maximum number of POSIX
+API Queued Signals that can be concurrently active.
 
-    * It shall be zero if the POSIX API is not enabled (e.g. RTEMS was built
-      without the ``RTEMS_POSIX_API = True`` build configuration option).
-      Otherwise a compile time error in the configuration file will occur.
+.. rubric:: NOTES:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Queued Signals that can be concurrently active.
+Unlimited objects are not available for queued signals.
 
-NOTES:
-    Unlimited objects are not available for queued signals.
+Queued signals are only available if RTEMS was built with the
+``--enable-posix`` build configuration option.
 
-    Queued signals are only available if RTEMS was built with the
-    ``--enable-posix`` build configuration option.
+.. rubric:: CONSTRAINTS:
+
+The following constraints apply to this configuration option:
+
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option shall be small enough so that the RTEMS
+  Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
+
+* The value of the configuration option shall be zero if the POSIX API is not
+  enabled (e.g. RTEMS was built without the ``RTEMS_POSIX_API = True`` build
+  configuration option).  Otherwise a compile time error in the configuration
+  file will occur.
 
 .. Generated from spec:/acfg/if/max-posix-semaphores
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
 
 .. _CONFIGURE_MAXIMUM_POSIX_SEMAPHORES:
@@ -224,51 +267,61 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_SEMAPHORES
 ----------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_SEMAPHORES``
 
-OPTION TYPE:
-    This configuration option is an integer define.
+.. rubric:: OPTION TYPE:
 
-DEFAULT VALUE:
-    The default value is 0.
+This configuration option is an integer define.
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+.. rubric:: DEFAULT VALUE:
 
-    * It shall be greater than or equal to zero.
+The default value is 0.
 
-    * It shall be less than or equal to 65535.
+.. rubric:: DESCRIPTION:
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+The value of this configuration option defines the maximum number of POSIX
+API Named Semaphores that can be concurrently active.
 
-    * It shall be small enough so that the RTEMS Workspace size calculation
-      carried out by ``<rtems/confdefs.h>`` does not overflow an integer of
-      type `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+.. rubric:: NOTES:
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Named Semaphores that can be concurrently active.
+Named semaphores are created with :c:func:`sem_open`.  Semaphores
+initialized with :c:func:`sem_init` are not affected by this
+configuration option since the storage space for these semaphores is
+user-provided.
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+.. rubric:: CONSTRAINTS:
 
-    Named semaphores are created with :c:func:`sem_open`.  Semaphores
-    initialized with :c:func:`sem_init` are not affected by this
-    configuration option since the storage space for these semaphores is
-    user-provided.
+The following constraints apply to this configuration option:
+
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option shall be small enough so that the RTEMS
+  Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-shms
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_SHMS
 
 .. _CONFIGURE_MAXIMUM_POSIX_SHMS:
@@ -276,46 +329,56 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_SHMS
 ----------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_SHMS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_SHMS``
+
+.. rubric:: OPTION TYPE:
 
-OPTION TYPE:
-    This configuration option is an integer define.
+This configuration option is an integer define.
 
-DEFAULT VALUE:
-    The default value is 0.
+.. rubric:: DEFAULT VALUE:
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+The default value is 0.
 
-    * It shall be greater than or equal to zero.
+.. rubric:: DESCRIPTION:
 
-    * It shall be less than or equal to 65535.
+The value of this configuration option defines the maximum number of POSIX
+API Shared Memory objects that can be concurrently active.
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+.. rubric:: NOTES:
 
-    * It shall be small enough so that the RTEMS Workspace size calculation
-      carried out by ``<rtems/confdefs.h>`` does not overflow an integer of
-      type `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+.. rubric:: CONSTRAINTS:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Shared Memory objects that can be concurrently active.
+The following constraints apply to this configuration option:
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option shall be small enough so that the RTEMS
+  Workspace size calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
 
 .. Generated from spec:/acfg/if/max-posix-threads
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_THREADS
 
 .. _CONFIGURE_MAXIMUM_POSIX_THREADS:
@@ -323,51 +386,61 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_THREADS
 -------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_THREADS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_THREADS``
+
+.. rubric:: OPTION TYPE:
+
+This configuration option is an integer define.
 
-OPTION TYPE:
-    This configuration option is an integer define.
+.. rubric:: DEFAULT VALUE:
 
-DEFAULT VALUE:
-    The default value is 0.
+The default value is 0.
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+.. rubric:: DESCRIPTION:
 
-    * It shall be greater than or equal to zero.
+The value of this configuration option defines the maximum number of POSIX
+API Threads that can be concurrently active.
 
-    * It shall be less than or equal to 65535.
+.. rubric:: NOTES:
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-    * It shall be small enough so that the task stack space calculation carried
-      out by ``<rtems/confdefs.h>`` does not overflow an integer of type
-      `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+This calculations for the required memory in the RTEMS Workspace for threads
+assume that each thread has a minimum stack size and has floating point
+support enabled.  The configuration option :ref:`CONFIGURE_EXTRA_TASK_STACKS` is used
+to specify thread stack requirements **above** the minimum size required.
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Threads that can be concurrently active.
+The maximum number of Classic API Tasks is specified by
+:ref:`CONFIGURE_MAXIMUM_TASKS`.
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+All POSIX threads have floating point enabled.
 
-    This calculations for the required memory in the RTEMS Workspace for threads
-    assume that each thread has a minimum stack size and has floating point
-    support enabled.  The configuration option :ref:`CONFIGURE_EXTRA_TASK_STACKS` is used
-    to specify thread stack requirements **above** the minimum size required.
+.. rubric:: CONSTRAINTS:
 
-    The maximum number of Classic API Tasks is specified by
-    :ref:`CONFIGURE_MAXIMUM_TASKS`.
+The following constraints apply to this configuration option:
 
-    All POSIX threads have floating point enabled.
+* The value of the configuration option shall be greater than or equal to zero.
+
+* The value of the configuration option shall be less than or equal to 65535.
+
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option shall be small enough so that the task
+  stack space calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
 
 .. Generated from spec:/acfg/if/max-posix-timers
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MAXIMUM_POSIX_TIMERS
 
 .. _CONFIGURE_MAXIMUM_POSIX_TIMERS:
@@ -375,49 +448,59 @@ NOTES:
 CONFIGURE_MAXIMUM_POSIX_TIMERS
 ------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MAXIMUM_POSIX_TIMERS``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MAXIMUM_POSIX_TIMERS``
+
+.. rubric:: OPTION TYPE:
+
+This configuration option is an integer define.
+
+.. rubric:: DEFAULT VALUE:
 
-OPTION TYPE:
-    This configuration option is an integer define.
+The default value is 0.
 
-DEFAULT VALUE:
-    The default value is 0.
+.. rubric:: DESCRIPTION:
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+The value of this configuration option defines the maximum number of POSIX
+API Timers that can be concurrently active.
 
-    * It shall be greater than or equal to zero.
+.. rubric:: NOTES:
 
-    * It shall be less than or equal to 65535.
+This object class can be configured in unlimited allocation mode, see
+:ref:`ConfigUnlimitedObjects`.
 
-    * It shall be less than or equal to a BSP-specific and application-specific
-      value which depends on the size of the memory available to the
-      application.
+Timers are only available if RTEMS was built with the
+``--enable-posix`` build configuration option.
 
-    * It may be defined through :c:func:`rtems_resource_unlimited` the enable
-      unlimited objects for the object class, if the value passed to
-      :c:func:`rtems_resource_unlimited` satisfies all other constraints of the
-      configuration option.
+.. rubric:: CONSTRAINTS:
 
-    * It shall be zero if the POSIX API is not enabled (e.g. RTEMS was built
-      without the ``RTEMS_POSIX_API = True`` build configuration option).
-      Otherwise a compile time error in the configuration file will occur.
+The following constraints apply to this configuration option:
 
-DESCRIPTION:
-    The value of this configuration option defines the maximum number of POSIX
-    API Timers that can be concurrently active.
+* The value of the configuration option shall be greater than or equal to zero.
 
-NOTES:
-    This object class can be configured in unlimited allocation mode, see
-    :ref:`ConfigUnlimitedObjects`.
+* The value of the configuration option shall be less than or equal to 65535.
 
-    Timers are only available if RTEMS was built with the
-    ``--enable-posix`` build configuration option.
+* The value of the configuration option shall be less than or equal to a
+  BSP-specific and application-specific value which depends on the size of the
+  memory available to the application.
+
+* The value of the configuration option may be defined through
+  :c:func:`rtems_resource_unlimited` the enable unlimited objects for the
+  object class, if the value passed to :c:func:`rtems_resource_unlimited`
+  satisfies all other constraints of the configuration option.
+
+* The value of the configuration option shall be zero if the POSIX API is not
+  enabled (e.g. RTEMS was built without the ``RTEMS_POSIX_API = True`` build
+  configuration option).  Otherwise a compile time error in the configuration
+  file will occur.
 
 .. Generated from spec:/acfg/if/min-posix-thread-stack-size
 
+.. raw:: latex
+
+    \clearpage
+
 .. index:: CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE
 .. index:: minimum POSIX thread stack size
 
@@ -426,30 +509,32 @@ NOTES:
 CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE
 -----------------------------------------
 
-CONSTANT:
-    ``CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE``
+.. rubric:: CONSTANT:
+
+``CONFIGURE_MINIMUM_POSIX_THREAD_STACK_SIZE``
+
+.. rubric:: OPTION TYPE:
+
+This configuration option is an integer define.
+
+.. rubric:: DEFAULT VALUE:
 
-OPTION TYPE:
-    This configuration option is an integer define.
+The default value is two times the value of
+:ref:`CONFIGURE_MINIMUM_TASK_STACK_SIZE`.
 
-DEFAULT VALUE:
-    The default value is two times the value of
-    :ref:`CONFIGURE_MINIMUM_TASK_STACK_SIZE`.
+.. rubric:: DESCRIPTION:
 
-VALUE CONSTRAINTS:
-    The value of this configuration option shall satisfy all of the following
-    constraints:
+The value of this configuration option defines the minimum stack size in
+bytes for every POSIX thread in the system.
 
-    * It shall be small enough so that the task stack space calculation carried
-      out by ``<rtems/confdefs.h>`` does not overflow an integer of type
-      `uintptr_t <https://en.cppreference.com/w/c/types/integer>`_.
+.. rubric:: CONSTRAINTS:
 
-    * It shall be greater than or equal to a BSP-specific and
-      application-specific minimum value.
+The following constraints apply to this configuration option:
 
-DESCRIPTION:
-    The value of this configuration option defines the minimum stack size in
-    bytes for every POSIX thread in the system.
+* The value of the configuration option shall be small enough so that the task
+  stack space calculation carried out by ``<rtems/confdefs.h>`` does not
+  overflow an integer of type `uintptr_t
+  <https://en.cppreference.com/w/c/types/integer>`_.
 
-NOTES:
-    None.
+* The value of the configuration option shall be greater than or equal to a
+  BSP-specific and application-specific minimum value.