Turned on concept and function name indexing.

1 files changed, 12 insertions, 0 deletions

diff --git a/doc/user/concepts.t b/doc/user/concepts.t
index c68a9a95b4..63e64343fb 100644
--- a/doc/user/concepts.t
+++ b/doc/user/concepts.t
@@ -23,6 +23,8 @@ one with these concepts.
 
 @section Objects
 
+@cindex objects
+
 RTEMS provides directives which can be used to
 dynamically create, delete, and manipulate a set of predefined
 object types.  These types include tasks, message queues,
@@ -41,6 +43,8 @@ reflect the object's use in the application.  Conversely, object
 IDs are designed to facilitate efficient object manipulation by
 the executive.
 
+@cindex object name
+
 An object name is an unsigned thirty-two bit entity
 associated with the object by the user.  Although not required
 by RTEMS, object names are typically composed of four ASCII
@@ -55,6 +59,8 @@ assign meaningful ASCII names to each task.  A more convenient
 approach would be to name them the binary values one through
 one-hundred, respectively.
 
+@cindex object ID
+
 @need 3000
 
 An object ID is a unique unsigned thirty-two bit
@@ -179,6 +185,8 @@ user applications.
 
 @section Communication and Synchronization
 
+@cindex communication and synchronization
+
 In real-time multitasking applications, the ability
 for cooperating execution threads to communicate and synchronize
 with each other is imperative.  A real-time executive should
@@ -220,6 +228,8 @@ for exception handling.
 
 @section Time
 
+@cindex time
+
 The development of responsive real-time applications
 requires an understanding of how RTEMS maintains and supports
 time-related operations.  The basic unit of time in RTEMS is
@@ -267,6 +277,8 @@ provided by a real time clock or counter/timer device.
 
 @section Memory Management
 
+@cindex memory management
+
 RTEMS memory management facilities can be grouped
 into two classes: dynamic memory allocation and address
 translation.  Dynamic memory allocation is required by