Cleanup.

doc/filesystem/applayering.t

@@ -18,9 +18,24 @@ and 7).
 
 
 @example
-Figure 6
+Figure of the File System Functional Layering goes here.
+This figure includes networking and disk caching layering.
 @end example
 
+@ifset use-ascii
+@example
+@group
+@end group
+@end example
+@end ifset
+
+@ifset use-tex
+@c @image{FunctionalLayerCake,6in,4in}
+@end ifset
+
+@ifset use-html
+@end ifset
+
 @enumerate
 
 @item Application programs are presented with a standard set of POSIX
@@ -66,7 +81,8 @@ interface routines.
 
 
 @example
-Figure 7
+Figure of the File System Functional Layering goes here.
+This figure focuses on the Base File System and IMFS.
 @end example
 
 
@@ -74,7 +90,7 @@ Figure 7
 
 
 @example
-Figure 8
+Figure of the IMFS Memfile control blocks 
 @end example
 
 

doc/filesystem/imfs.t

@@ -243,12 +243,12 @@ This routine will examine the mode argument to determine is we are trying to
 create a directory, regular file and a device node. The creation of other
 node types is not permitted and will cause an assert.
 
-Memory space will be allocated for a -jnode- and the node will be set up
+Memory space will be allocated for a @code{jnode} and the node will be set up
 according to the nodal type that was specified. The IMFS_create_node()
 function performs the allocation and setup of the node.
 
 The only problem that is currently reported is the lack of memory when we
-attempt to allocate space for the -jnode- (ENOMEN).
+attempt to allocate space for the @code{jnode} (ENOMEN).
 
 
 @c
@@ -731,16 +731,16 @@ memfile.c
 
 @subheading Development Comments:
 
-This routine will determine the -jnode- that is associated with this file.
+This routine will determine the @code{jnode} that is associated with this file.
 
-It will then call IMFS_memfile_read() with the -jnode-, file position index,
+It will then call IMFS_memfile_read() with the @code{jnode}, file position index,
 buffer and transfer count as arguments.
 
 IMFS_memfile_read() will do the following:
 
 @itemize @bullet
 
-@item Verify that the -jnode- is associated with a memory file
+@item Verify that the @code{jnode} is associated with a memory file
 
 @item Verify that the destination of the read is valid
 
@@ -1093,7 +1093,7 @@ imfs_directory.c
 
 @subheading Development Comments:
 
-This routine will look into the file control block to find the -jnode- that
+This routine will look into the file control block to find the @code{jnode} that
 is associated with the directory.
 
 The routine will verify that the node is a directory. If its not a directory
@@ -1482,7 +1482,7 @@ deviceio.c
 This routine will use the file control block to locate the node structure for
 the device.
 
-It will extract the major and minor device numbers from the -jnode-.
+It will extract the major and minor device numbers from the @code{jnode}.
 
 The major and minor device numbers will be used to make a rtems_io_open()  
 function call to open the device driver. An argument list is sent to the

doc/filesystem/init.t

@@ -18,10 +18,10 @@ of the following:
 
 @item Initialization of mount table chain control structure
 
-@item Allocation of a -jnode- structure that will server as the root node
+@item Allocation of a @code{jnode} structure that will server as the root node
 of the `In Memory File System'
 
-@item Initialization of the allocated -jnode- with the appropriate OPS,
+@item Initialization of the allocated @code{jnode} with the appropriate OPS,
 directory handlers and pathconf limits and options.
 
 @item Allocation of a memory region for file system specific global