--- freem/doc/freem.texi	2025/04/19 01:10:05	1.32
+++ freem/doc/freem.texi	2025/04/20 15:43:32	1.33
@@ -4427,6 +4427,16 @@ See @ref{Classes}.
 @cindex variables, global
 @cindex data
 
+@menu
+* Globals Overview::            Basics of FreeM persistent storage.
+* Creating Globals::            How to create globals.
+* Removing Globals::            How to remove globals.
+* Global Storage::              How globals are stored.
+@end menu
+
+@node Globals Overview
+@section Globals Overview
+
 FreeM supports typical M globals, which are often described as persistent, hierachical sparse arrays. Globals make it relatively simple to include persistent data in an application without requiring the developer to use an external database management system, and offer syntax and semantics so similar to M local variables and structured system variables that moving from one to the other is seamless.
 
 Each global comprises three elements:
@@ -4507,10 +4517,22 @@ typedef struct global_header {
 @cindex locking
 @cindex transaction processing
 
+@menu
+* Concurrency Control Overview::                Basics of concurrency control.
+* Advisory Locks::                              Coordinating access voluntarily.
+* Transaction Processing::                      Ensuring logical consistency.
+@end menu
+
+@node Concurrency Control Overview
+@section Concurrency Control Overview
+
 Multitasking, multi-user FreeM applications must concern themselves with concurrent access to globals in order to maintain logical consistency and prevent concurrent writes from interleaving.
 
 In FreeM, there are two mechanisms provided for managing concurrent global access: advisory locks, and transaction processing.
 
+@node Advisory Locks
+@section Advisory Locks
+
 @node Transaction Processing
 @section Transaction Processing
 @cindex transaction processing
@@ -4652,6 +4674,16 @@ The effect of this is that the operation
 @node Classes
 @section Classes
 
+@menu
+* Class Overview::                  Class basics.
+* Constructors::                    Managing object creation.
+* Destructors::                     Cleaning up.
+* Runtime Polymorphism::            Selecting methods at runtime.
+@end menu
+
+@node Class Overview
+@subsection Class Overview
+
 A @emph{class} is the primary organizing concept of FreeM support for object-oriented programming, and in FreeM, is simply an M routine with a few special properties:
 
 @example