Index: develenv/utilities.rst
===================================================================
--- develenv/utilities.rst	(revision 489740f6a9ff82c63c00e9c023fbc7319d6cb8a4)
+++ develenv/utilities.rst	(revision 9b53679540443784bc0dba6426b1a8a2da9f6b37)
@@ -4,23 +4,20 @@
 ########################
 
-This section describes the additional commands
-available within the *RTEMS Development Environment*.  Although
-some of these commands are of general use, most are included to
-provide some capability necessary to perform a required function
-in the development of the RTEMS executive, one of its support
+This section describes the additional commands available within the *RTEMS
+Development Environment*.  Although some of these commands are of general use,
+most are included to provide some capability necessary to perform a required
+function in the development of the RTEMS executive, one of its support
 components, or an RTEMS based application.
 
-Some of the commands are implemented as C programs.
-However, most commands are implemented as Bourne shell scripts.
-Even if the current user has selected a different shell, the
-scripts will automatically invoke the Bourne shell during their
-execution lifetime.
+Some of the commands are implemented as C programs.  However, most commands are
+implemented as Bourne shell scripts.  Even if the current user has selected a
+different shell, the scripts will automatically invoke the Bourne shell during
+their execution lifetime.
 
-The commands are presented in UNIX manual page style
-for compatibility and convenience.  A standard set of paragraph
-headers were used for all of the command descriptions.  If a
-section contained no data, the paragraph header was omitted to
-conserve space.  Each of the permissible paragraph headers and
-their contents are described below:
+The commands are presented in UNIX manual page style for compatibility and
+convenience.  A standard set of paragraph headers were used for all of the
+command descriptions.  If a section contained no data, the paragraph header was
+omitted to conserve space.  Each of the permissible paragraph headers and their
+contents are described below:
 
 ``SYNOPSIS``
@@ -48,19 +45,16 @@
     lists any relevant commands which can be consulted
 
-Most environment variables referenced by the commands
-are defined for the RTEMS Development Environment during the
-login procedure.  During login, the user selects a default RTEMS
-environment through the use of the Modules package.  This tool
-effectively sets the environment variables to provide a
-consistent development environment for a specific user.
-Additional environment variables within the RTEMS environment
-were set by the system administrator during installation.  When
-specifying paths, a command description makes use of these
+Most environment variables referenced by the commands are defined for the RTEMS
+Development Environment during the login procedure.  During login, the user
+selects a default RTEMS environment through the use of the Modules package.
+This tool effectively sets the environment variables to provide a consistent
+development environment for a specific user.  Additional environment variables
+within the RTEMS environment were set by the system administrator during
+installation.  When specifying paths, a command description makes use of these
 environment variables.
 
-When referencing other commands in the SEE ALSO
-paragraph, the following notation is used:   command(code).
-Where command is the name of a related command, and code is a
-section number.  Valid section numbers are as follows:
+When referencing other commands in the SEE ALSO paragraph, the following
+notation is used: command(code).  Where command is the name of a related
+command, and code is a section number.  Valid section numbers are as follows:
 
 ``1``
@@ -73,9 +67,7 @@
     a manual page from this document, the RTEMS Development Environment Guide
 
-For example, ls(1) means see the standard ls command
-in section 1 of the UNIX documentation.  gcc020(1G) means see
-the description of gcc020 in section 1 of the GNU documentation.
-
-.. COMMENT: packhex
+For example, ``ls(1)`` means see the standard ls command in section 1 of the
+UNIX documentation.  gcc020(1G) means see the description of gcc020 in section
+1 of the GNU documentation.
 
 packhex - Compress Hexadecimal File
@@ -84,5 +76,5 @@
 **SYNOPSIS**
 
-.. code:: c
+.. code-block:: c
 
     packhex <source >destination
@@ -90,12 +82,10 @@
 **DESCRIPTION**
 
-packhex accepts Intel Hexadecimal or Motorola Srecord
-on its standard input and attempts to pack as many contiguous
-bytes as possible into a single hexadecimal record.  Many
-programs output hexadecimal records which are less than 80 bytes
-long (for human viewing).  The overhead required by each
-unnecessary record is significant and packhex can often reduce
-the size of the download image by 20%.  packhex attempts to
-output records which are as long as the hexadecimal format
+packhex accepts Intel Hexadecimal or Motorola Srecord on its standard input and
+attempts to pack as many contiguous bytes as possible into a single hexadecimal
+record.  Many programs output hexadecimal records which are less than 80 bytes
+long (for human viewing).  The overhead required by each unnecessary record is
+significant and packhex can often reduce the size of the download image by 20%.
+packhex attempts to output records which are as long as the hexadecimal format
 allows.
 
@@ -106,21 +96,18 @@
 **EXAMPLES**
 
-Assume the current directory contains the Motorola
-Srecord file download.sr. Then executing the command:
-.. code:: c
+Assume the current directory contains the Motorola Srecord file
+download.sr. Then executing the command:
+
+.. code-block:: c
 
     packhex <download.sr >packed.sr
 
-will generate the file packed.sr which is usually
-smaller than download.sr.
+will generate the file packed.sr which is usually smaller than download.sr.
 
 **CREDITS**
 
-The source for packhex first appeared in the May 1993
-issue of Embedded Systems magazine.  The code was downloaded
-from their BBS.  Unfortunately, the author's name was not
-provided in the listing.
-
-.. COMMENT: unhex
+The source for packhex first appeared in the May 1993 issue of Embedded Systems
+magazine.  The code was downloaded from their BBS.  Unfortunately, the author's
+name was not provided in the listing.
 
 unhex - Convert Hexadecimal File into Binary Equivalent
@@ -129,16 +116,15 @@
 **SYNOPSIS**
 
-.. code:: c
+.. code-block:: c
 
-    unhex \[-valF] \[-o file] \[file \[file ...] ]
+    unhex [-valF] [-o file] [file [file ...] ]
 
 **DESCRIPTION**
 
-unhex accepts Intel Hexadecimal, Motorola Srecord, or
-TI 'B' records and converts them to their binary equivalent.
-The output may sent to standout or may be placed in a specified
-file with the -o option.  The designated output file may not be
-an input file.  Multiple input files may be specified with their
-outputs logically concatenated into the output file.
+unhex accepts Intel Hexadecimal, Motorola Srecord, or TI 'B' records and
+converts them to their binary equivalent.  The output may sent to standout or
+may be placed in a specified file with the -o option.  The designated output
+file may not be an input file.  Multiple input files may be specified with
+their outputs logically concatenated into the output file.
 
 **OPTIONS**
@@ -150,6 +136,5 @@
 
 ``a base``
-    First byte of output corresponds with base
-    address
+    First byte of output corresponds with base address
 
 ``l``
@@ -164,9 +149,8 @@
 **EXAMPLES**
 
-The following command will create a binary equivalent
-file for the two Motorola S record files in the specified output
-file binary.bin:
-.. code:: c
+The following command will create a binary equivalent file for the two Motorola
+S record files in the specified output file binary.bin:
+
+.. code-block:: c
 
     unhex -o binary.bin downloadA.sr downloadB.sr
-
