[rtems-docs commit] c-user: fix broken definition in rate-monotonic background.

[Sebastian Huber]

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

Author:    Gedare Bloom <gedare at rtems.org>
Date:      Thu Apr 22 09:10:45 2021 -0600

c-user: fix broken definition in rate-monotonic background.

---

 c-user/rate-monotonic/background.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/c-user/rate-monotonic/background.rst b/c-user/rate-monotonic/background.rst
index 9ca7dff..c81af4e 100644
--- a/c-user/rate-monotonic/background.rst
+++ b/c-user/rate-monotonic/background.rst
@@ -112,7 +112,9 @@ less than its period.  For example, a periodic task's requirements may state
 that it should execute for 10 milliseconds every 100 milliseconds.  Although
 the execution time may be the average, worst, or best case, the worst-case
 execution time is more appropriate for use when analyzing system behavior under
-transient overload conditions... index:: aperiodic task, definition
+transient overload conditions.
+
+.. index:: aperiodic task, definition
 
 In contrast, an aperiodic task executes at irregular intervals and has only a
 soft deadline.  In other words, the deadlines for aperiodic tasks are not