diff --git a/twander.1 b/twander.1
index 2357670..5d616af 100644
--- a/twander.1
+++ b/twander.1
@@ -128,7 +128,7 @@
 on Unix:
 
 .nf
-export TWANDER=-qt
+.B export TWANDER=-qt
 .fi
 
 From then on, every time you run the program, the -q and -t options
@@ -168,7 +168,7 @@
 until after the Configuration File has been processed.  So, the -q
 argument on the command line will not inhibit warnings generated
 during the reading of the Configuration File.  This is best done by
-adding the statement, "WARN=False" at the top of the Configuration
+adding the statement, WARN=False, at the top of the Configuration
 File.
 
 If the Configuration File is reloaded while the program is running
@@ -262,7 +262,7 @@
 .B Clear History (CLRHIST)
 Control-y
 
-Clears out various program histories including the All Directory list,
+Clears out various program histories including the All Visited Directories list,
 the Directory Stack, the Command History, and the last
 manually-entered values for CHANGEDIR and RUNCMD.  The 12 Program
 Memories are not cleared - they have specially dedicated key bindings
@@ -608,7 +608,7 @@
 selected files to a new directory, press RUNCMD and enter (on Unix):
 
 .nf
-cp [SELECTIONS] newdir
+.B cp [SELECTIONS] newdir
 .fi
 
 \'twander\' understands the variable reference syntax here just as it
@@ -619,7 +619,7 @@
 systems:
 
 .nf
-[$EDITOR] [SELECTIONS]
+.B [$EDITOR] [SELECTIONS]
 .fi
 
 Unless you have set the MAXHIST option to 0, RUNCMD keeps track of
@@ -720,8 +720,9 @@
 (see below).  To take advantage of this feature, you write Command
 Definitions (or manually issue a command via the RUNCMD key) which
 reference the contents of a Program Memory using one of the [MEMx]
-Built-In Variables.  (See the section below on Built-In Variables for
-more details in how to apply Program Memories).
+Built-In Variables.  (See the section below on entitled,
+.B Program Memory Built-Ins
+for more details in how to apply Program Memories).
 
 \'twander\' provides key combinations for selectively setting and
 clearing particular Program Memories as well as a key combination
@@ -820,7 +821,7 @@
 size reasonable.  If you set MAXDIR=0, it means you are
 disabling this menu feature altogether as well as disabling
 the tracking of the last manually entered directory via
-the CHANGEDIR key (default: Control-x).
+the CHANGEDIR key. (default: Control-x)
 
 MAXDIRBUF specifies how many directories \'twander\' keeps track
 of internally, no matter how many are actually displayed.  It defaults
@@ -834,14 +835,14 @@
 actually been visited.
 
 The Directory Menu is emptied and grayed out when you press the
-CLRHIST key (default: Control-y).
+CLRHIST key. (default: Control-y)
 
 .SS History Menu (Alt-h) [Shift-Control-Right-Mouse-Button]
 
 \'twander\' keeps track of every command you attempt to execute,
 whether it is an invocation of a Command Definition found in the
-Configuration File or a manually entered command via the RUNCMD key
-(default: Control-z).  This is done whether or not the command is
+Configuration File or a manually entered command via the RUNCMD key.
+(default: Control-z)  This is done whether or not the command is
 successfully executed.
 
 This feature provides a quick way to re-execute a command you've
@@ -880,7 +881,7 @@
 
 
 The History Menu is emptied and grayed out when you press the
-CLRHIST key (default: Control-y).
+CLRHIST key. (default: Control-y)
 
 .SS Help Menu (Alt-l) [No Mouse Shortcut]
 
@@ -916,10 +917,10 @@
 .SH LOCATION OF CONFIGURATION FILE
 
 By default, the program expects to find configuration information in
-.B $HOME/.twander 
-(%HOME%/.twander on Win32) but you can override this with the -c
-command line option. (Recommended for Win32 systems - see the section
-below entitled,
+.B $HOME/.twander (%HOME%/.twander on Win32) 
+but you can override this with the -c command line
+option. (Recommended for Win32 systems - see the section below
+entitled,
 .B INSTALLING \'twander\'
 )
 
@@ -1001,12 +1002,13 @@
 
 Many of \'twander\'s internal program defaults can be overriden in the
 Configuration File using Program Option statements.  These statements
-look just like User-Defined variables except \'twander\' recognizes
-the variable name as a Program Option rather than an arbitrary
-variable.  Program Option Statements thus take the form:
+look just like the User-Defined variables described later in this
+document except \'twander\' recognizes the variable name as a Program
+Option rather than an arbitrary variable.  Program Option Statements
+thus take the form:
 
 .nf
-Option Name = Option Value
+.B Option Name = Option Value
 .fi
 
 The Option Name is case-sensitive and must be entered exactly as
@@ -1019,7 +1021,7 @@
 
 A Boolean Option must be assigned a value of True or False.  These
 logical values can be in any case, so TRUE, TRue, and tRue all work.
-Note that if you view these variables in the Help menu entitled,
+Note that when you view these variables in the Help menu entitled,
 .B User-Settable Options,
 they are displayed as 0 (False) and 1 (True).
 
@@ -1031,8 +1033,8 @@
 is not allowed:
 
 .nf
-# Bad String Option Assignment - Causes Warning
-BCOLOR =
+.B # Bad String Option Assignment - Causes Warning
+.B BCOLOR =
 .fi
 
 Furthermore, as described above, you cannot use the \'#\' symbol
@@ -1048,15 +1050,15 @@
 to a spectacular program failure and Python traceback on stdout:
 
 .nf
-# A Nice Way To Clobber \'twander\'
-BCOLOR = goo
+.B # A Nice Way To Clobber \'twander\'
+.B BCOLOR = goo
 .fi
 
 The following sections document each available Program Option 
 using this general format:
 
 .nf
-Option-Name [Type] (Default Value)
+.B Option-Name [Type] (Default Value)
 .fi
 
 .TP
@@ -1066,7 +1068,7 @@
 refresh the display with any changes.  If you are running on a very
 slow machine or slow connection between the X-Windows server and
 client, set this option to False.  You can manually force an update at
-any time using the REFRESH key (default: Control-l).
+any time using the REFRESH key. (default: Control-l)
 
 
 .TP
@@ -1088,7 +1090,7 @@
 well.  So, it's common to see Command Definitions like:
 
 .nf
-x MyCommand   xterm -l -e bash -c stuff-for-my-command
+.B x MyCommand   xterm -l -e bash -c stuff-for-my-command
 .fi
 
 In fact, on Unix, the need for this idiom is so common, it's best
@@ -1097,21 +1099,21 @@
 something like (comments removed):
 
 .nf
-SHELL       = bash -c
-VSHELL      = [XTERM] [SHELL]
-XTERM       = xterm -fn 9x15 -l -e
+.B SHELL       = bash -c
+.B VSHELL      = [XTERM] [SHELL]
+.B XTERM       = xterm -fn 9x15 -l -e
 .fi
 
 Now the Command Definition above becomes:
 
 .nf
-x MyCommand [VSHELL] stuff-for-my-command
+.B x MyCommand [VSHELL] stuff-for-my-command
 .fi
 
 That's all well and good for Command Definitions, but what happens
 when you want to
 .B manually enter a command
-via the RUNCMD key (default: Control-z)?  You have to manually
+via the RUNCMD key? (default: Control-z)  You have to manually
 enter the gobbledy-gook above, or at least start your command
 with [VSHELL] (since RUNCMD understands variable references).
 
@@ -1122,11 +1124,11 @@
 Configuration File:
 
 .nf
-CMDSHELL = xterm -l -e bash -c
+.B CMDSHELL = xterm -l -e bash -c
 
             - or -
 
-CMDSHELL = [VSHELL]  # Assuming VSHELL is defined previously
+.B CMDSHELL = [VSHELL]  # Assuming VSHELL is defined previously
 .fi
 
 Now every time you enter a command, this will be placed in
@@ -1140,13 +1142,15 @@
 blank):
 
 .nf
-CMDSHELL = ""
+.B CMDSHELL = ""
 .fi
 
-If you want to disable CMDSHELL operation
-.B for just a single manually entered command,
-begin your command with the backslash (\\) character.  \'twander\'
-understands this to "escape" CMDSHELL processing.
+You also may want to occasionally use RUNCMD to do something without
+CMDSHELL processing, even though that feature has been defined in the
+Configuration File.  You can disable CMDSHELL operation on a
+per-RUNCMD basis.  Just begin your entering your command with the
+backslash (\\) character.  \'twander\' understands this to "escape"
+CMDSHELL processing.
 
 As a general matter, CMDSHELL allows you to prepend
 .B anything you like
@@ -1179,19 +1183,19 @@
 .TP
 .B FNAME [String] (Courier)
 
-This selects the Font Name for the main display.
+Selects the main display Font Name.
 
 .TP
 .B FSZ [Numeric] (12)
 
-This selects the main display Font Size.
+Selects the main display Font Size.
 
 .TP
 .B FWT [String] (bold)
 
-This selects the main display Font Weight.  This can be assigned
-to: normal, bold, italic, or underlined.  Depending on your
-system, other values may also be possible.
+Selects the main display Font Weight.  This can be assigned to:
+normal, bold, italic, or underlined.  Depending on your system, other
+values may also be possible.
 
 .TP
 .B HBCOLOR [String] (lightgreen)
@@ -1201,7 +1205,7 @@
 .TP
 .B HEIGHT [Numeric] (600)
 
-Initial vertical offset of the \'twander\' window in pixels.
+Initial vertical size of the \'twander\' window in pixels.
 
 .TP
 .B HFCOLOR [String] (black)
@@ -1216,7 +1220,7 @@
 .TP
 .B HFSZ [Numeric] (10)
 
-This selects the help menu Font Size.
+Selects the help menu Font Size.
 
 .TP
 .B HFWT [String] (italic)
@@ -1258,23 +1262,23 @@
 .TP
 .B MAXNESTING [Numeric] (32)
 
-Number of time a Command Definition is processed to dereference
+Number of times a Command Definition is processed to dereference
 all variables.  For example, suppose you have this:
 
 .nf
-FOO = bax
-BAM = x[FOO]
+.B FOO = bax
+.B BAM = x[FOO]
 
-x mycmd [BAM] [SELECTION]
+.B x mycmd [BAM] [SELECTION]
 .fi
 
 When you press the x key, the \'twander\' command interpreter has to
 process the line repeatedly until all variables are resolved:
 
 .nf
-[BAM] [SELECTION]   -> x[FOO] [SELECTION]
-x[FOO] [SELECTION]  -> xbax [SELECTION]
-xbax [SELECTION]    -> xbax selected-item
+.B [BAM] [SELECTION]   -> x[FOO] [SELECTION]
+.B x[FOO] [SELECTION]  -> xbax [SELECTION]
+.B xbax [SELECTION]    -> xbax selected-item
 .fi
 
 So, in this case, it took 3 iterations to do this.  MAXNESTING
@@ -1282,16 +1286,18 @@
 We have to do this to stop runaway definitions like this:
 
 .nf
-FOO = x[FOO]
+.B FOO = x[FOO]
 .fi
 
 This kind of construct will cause \'twander\' to iterate
 MAXNESTING number of times and then give up with
-a warning about exeeding this limit.
+a warning about exeeding the nesting (dereferencing) limit.
 
 A 32 iteration limit should be plenty for any reasonable
 Command Definitions.  If you set MAXNESTING to 0, \'twander\'
-will not allow *any* variable dereferencing,
+will not allow 
+.B any
+variable dereferencing,
 .B including the Built-In Variables.
 This is probably not what you want.
 
@@ -1396,21 +1402,25 @@
 than the default of 3 seconds), but it can be off this
 nominal value by quite a bit.  
 
-If you run \'twander\' on a slow system (or have a slow
-link between X-Client and X-Server) you might want to
-increase this value substantially.  You can get into
-the situtation where, just as one refresh completes,
-its time to do the next one, and the \'twander\'
-will seem really sluggish and unresponsive.
+If you run \'twander\' on a slow system (or have a slow link between
+X-Client and X-Server) you might want to increase this value
+substantially.  You can get into the situtation where just as one
+refresh completes, its time to do the next one, and the \'twander\'
+will seem really sluggish and unresponsive.  By lengthening the time
+between automatic updates, the amount of unresponsive behavior is
+reduced.  Of course, this also means that any changes in the currently
+viewed directory will also take longer to appear in the \'twander\'
+display.
 
 .TP
 .B STARTDIR [String] (Directory In Which Program Started)
 
 This allows you to force a starting directory of your choice no matter
 where the program actually is launched.  This is useful both for
-day-to-day operation - perhaps you always want to start in you home
-directory - and in tandem with the NODETAILS and NONAVIGATE options to
-force a user to the only directory which they should be using.
+day-to-day operation - perhaps you always want to start in your home
+directory.  STARTDIR is also handy in tandem with the NODETAILS and
+NONAVIGATE options to force a user to the only directory which they
+should be using.
 
 .TP
 .B STARTX [Numeric] (0)
@@ -1486,7 +1496,7 @@
 .TP
 .B WIDTH [Numeric] (800)
 
-Initial width of the \'twander\' window in pixels.
+Initial horizontal size of the \'twander\' window in pixels.
 
 .P
 A few general notes about Program Options are worth mentioning here:
@@ -1508,19 +1518,24 @@
 somewhat by system.  For instance, Win32 TrueType fonts are
 effectively available in every size and weight.  On the other hand,
 most Unix-like systems have a more limited palette of fonts and colors
-with which to work.  If your setting in the Configuration File seems
-not to work, take a look at the command windows in which you started
-\'twander\' (or start it from one manually, if you're using a GUI
-shortcut directly).  Attempts to use unavailable colors and weights
-will cause Python/Tkinter to dump traceback information on stdout.
+with which to work.  Most systems should support obvious color
+names like, red, white, blue, yellow, beige, and so on.  Many also
+support colors like lightgreen, lightblue, etc.  At a minimum,
+you should be able to use normal, bold, italic, and underline
+for font weights.
 
-.IP \(bu 4
 Most systems attempt some kind of "best fit" font matching.  If you
 specify a font size/weight/name that does not exist, the system
 will try to find what it thinks is the closest match.  This is
 usually ugly, so try to specify font information for things that
 actually exist on your system.
 
+If your setting in the Configuration File seems not to work, take a
+look at the command window in which you started \'twander\' (or start
+it from one manually, if you're using a GUI shortcut to start it).
+Attempts to use unavailable colors and weights will cause
+Python/Tkinter to dump traceback information on stdout.
+
 .IP  \(bu 4
 Although you can use proportionally spaced fonts with \'twander\',
 the result is pretty ugly.  \'twander\' assumes a fixed width
@@ -1530,12 +1545,25 @@
 .IP \(bu 4
 If you set MAXDIR or MAXDIRBUF to 0, it disables both the tracking of
 visited directories and the retention of last manually entered
-directory with CHANGEDIR (default: Control-x).
+directory with CHANGEDIR. (default: Control-x)
 
 .IP \(bu 4
 Similarly if you set MAXHIST or MAXHISTBUF to 0, you disable both
 command history and the retention of the last manually entered command
-via RUNCMD (default: Control-z).
+via RUNCMD. (default: Control-z)
+
+.IP \(bu 4
+Changing either MAXDIR or MAXHIST and then reloading the Configuration
+File only changes
+.B the number of items visible on their respective menus.
+\'twander\' actually keeps track of more than this internally
+(governed by the MAXDIRBUF and MAXHISTBUF options).
+
+Say MAXDIR and MAXHIST are set to 4, but you've actually visited 20
+different directories and issued 30 commands.  You'll only see 4 of
+each.  But, if you edit MAXDIR and MAXHIST to now be 32 and reload the
+Configuration File, you will see all 20 directories and 30 commands on
+their respective menus.
 
 .IP \(bu 4
 At first glance, the ability to set QUOTECHAR to any arbitary string
@@ -1549,7 +1577,7 @@
 Definition like this:
 
 .nf
-x mycmd MyPythonScript [DSELECTIONS] other stuff
+.B x mycmd MyPythonScript [DSELECTIONS] other stuff
 .fi
 
 When MyPythonScript runs, it can immediately tell which arguments
@@ -1558,6 +1586,13 @@
 
 You probably won't need this often, but its nice to have.
 
+.IP \(bu 4
+STARTX and STARTY are relative to the (0,0) origin that Tk uses for
+window placement.  In High-School algebra most of us got used
+to seeing (0,0) in the lower-left corner of a graph.  Tk has 
+a rather different view of this and STARTX and STARTY are
+relative to the
+.B upper-left corner of the screen.
 
 .SS Key Binding Statements
 
@@ -1591,15 +1626,15 @@
 keystokes can be found in the many sources of Tk documentation,
 both in print and on the Internet.)
 
-Keyboard binding assignments look just like local variable definitions
+Keyboard binding assignments look just like variable definitions
 in the Configuration File.  (The \'twander\' Configuration File parser
-automatically distinguishes between Key Binding Statements and User-Defined
-Variables.  This means you can never use one of the program
-function names as one of your own variable names.) Key Binding
-Statements thus take the form:
+automatically distinguishes between Key Binding Statements and
+Variable Definitions or other legitimate statements.  This means you
+can never use one of the program function names as one of your own
+variable names.) Key Binding Statements thus take the form:
 
 .nf
-Program-Function-Name = Tkinter-Keystroke-Name
+.B Program Function Name = Tkinter Keystroke Name
 .fi
 
 Changing the default bindings is therefore nothing more than a matter
@@ -1610,10 +1645,8 @@
 Examples of all the default key bindings are shown as comments in the
 ".twander" example Configuration File supplied in the program
 distribution.  The easiest way to rebind a particular function is to
-uncomment the relevant line and change the right side of the
-assignment to the new key you'd like to use.  More detailed
-instructions on what to do are found in the example ".twander" file
-itself.
+copy the relevant line, uncomment the copy, and change the right side
+of the assignment to the new key you'd like to use.
 
 It is important to observe several rules when rebinding keys:
 
@@ -1629,9 +1662,11 @@
 .B without any quotation marks.
 
 .nf
-So, this is correct:    QUITPROG = <F3>
+.B # Incorrect
+.B QUITPROG = '<F3>'    
 
-But, this is not:       QUITPROG = '<F3>'
+.B # Correct
+.B QUITPROG = <F3>
 .fi
 
 .IP \(bu 4 
@@ -1641,7 +1676,7 @@
 recognize such an attempt.  For example, suppose you try to do this:
 
 .nf
-QUITPROG = something-or-other
+.B QUITPROG = something-or-other
 .fi
 
 Because you want to be able to reference [QUITPROG] in a subsequent
@@ -1674,17 +1709,17 @@
 These statements are in the form:
 
 .nf
-DIRSCxx = path
+.B DIRSCxx = path
 
    where, xx is a number from 1-12
-.nf
+.fi
 
 So, for example, if you want to enter "C:\\Documents And Settings"
 when you press the F5 key, you would add this to your Configuration
 File:
 
 .nf
-DIRSC5 = c:\\Documents And Settings
+.B DIRSC5 = c:\\Documents And Settings
 .fi
 
 There are several subtleties to Directory Shortcuts you should
@@ -1701,7 +1736,7 @@
 
 .nf
 # This "undefines" shortcut #5
-DIRSC5 =
+.B DIRSC5 =
 .fi
 
 .IP \(bu 4
@@ -1727,10 +1762,12 @@
 shortcut.
 
 .IP \(bu 4
-Keep the Program Function Names (KDIRSC1 ... KDIRSC12) which
-are used for Key Binding, distinct in your thinking from
-the Directory Shortcut Names (DIRSC1 ... DIRSC12) which are
-used for defining the shortcuts.
+Keep the Program Function Names 
+.B (KDIRSC1 ... KDIRSC12)
+which are used for Key Binding, distinct in your thinking from
+the Directory Shortcut Names 
+.B (DIRSC1 ... DIRSC12)
+which are used for defining the shortcuts.
 
 .IP \(bu 4
 If you enter a Directory Shortcut Name that is invalid
@@ -1769,19 +1806,19 @@
 User-Defined Variables are defined using the syntax:
 
 .nf
-Variable-Name = Replacement-String
+.B Variable Name = Replacement String
 .fi
 
 Environment Variables are referenced using the syntax:
 
 .nf
-[$VARIABLE]
+.B [$VARIABLE]
 .fi
 
 Say we have a configuration line like this,
 
 .nf
-EDITOR = emacs blah blah blah blah
+.B EDITOR = emacs blah blah blah blah
 .fi
 
 Later on, when defining a command, instead of typing in "emacs blah
@@ -1795,7 +1832,7 @@
 could thus become:
 
 .nf
-EDITOR = [$EDITOR] blah blah blah blah
+.B EDITOR = [$EDITOR] blah blah blah blah
 .fi
 
 Why bother with this?  Because it makes maintaining complex
@@ -1812,7 +1849,7 @@
 definition that refers to another variable:
 
 .nf
-NewVar = somestring [OldVar]
+.B NewVar = somestring [OldVar]
 .fi
 
 It is important to realize that this only means: "If you encounter
@@ -1839,9 +1876,9 @@
 MAXNESTING Program Option).  You can have constructs like:
 
 .nf
-Var1 = Foo
-Var2 = Bar
-FB = [Var1][Var2]
+.B Var1 = Foo
+.B Var2 = Bar
+.B FB = [Var1][Var2]
 .fi
 
 Later on (when defining some command) when \'twander\' runs into the
@@ -1851,7 +1888,7 @@
 This limit has to be imposed to catch silly things like this:
 
 .nf
-Var = a[Var]
+.B Var = a[Var]
 .fi
 
 This recursive definition is a no-no and will be cause \'twander\'
@@ -1863,9 +1900,9 @@
 OK:
 
 .nf
-Var1 = [$PAGER]
-Var2 = command-arguments
-V    = [Var1]  [Var2]  [DSELECTION]
+.B Var1 = [$PAGER]
+.B Var2 = command-arguments
+.B V    = [Var1]  [Var2]  [DSELECTION]
 .fi
 
 .IP \(bu 4
@@ -1885,16 +1922,16 @@
 are actually needed:
 
 .nf
-Var1 = foo
-Var2 = [Var3]    # This is just a string substitution, not a reference
-Var3 = bar
-MyVar = [Var1][Var2]
+.B Var1 = foo
+.B Var2 = [Var3]    # This is just a string substitution, not a reference
+.B Var3 = bar
+.B MyVar = [Var1][Var2]
 
-# Now comes the Command Definition
-# If we put this before the Variable Definitions above,
-# it would be an error.
+.B # Now comes the Command Definition
+.B # If we put this before the Variable Definitions above,
+.B # it would be an error.
 
-x mycommand [MyVar]
+.B x mycommand [MyVar]
 .fi
 
 .IP \(bu 4
@@ -1923,7 +1960,7 @@
 named "something". If you do this:
 
 .nf
-$MYVAR = some-string
+.B $MYVAR = some-string
 .fi
 
 You will never be able to subsequently reference it because,
@@ -1950,7 +1987,7 @@
 fields separated by whitespace:
 
 .nf
-Command-Key  Command-Name  Command-String
+.B Command-Key  Command-Name  Command-String
 .fi
 
 The
@@ -1985,9 +2022,8 @@
 In its simplest form, a Command Definition looks like this:
 
 .nf
-# A simple Command Definition
-
-m  MyMore  more somefile
+.B # A simple Command Definition
+.B m  MyMore  more somefile
 .fi
 
 This command can be invoked pressing the "m" key on the keyboard or
@@ -2005,9 +2041,8 @@
 this:
 
 .nf
-# Our command setup to run as a GUI window
-
-m MyMore xterm -l -e more somefile
+.B # Our command setup to run as a GUI window
+.B m MyMore xterm -l -e more somefile
 .fi
 
 .SS User-Defined Variables In A Command String
@@ -2020,12 +2055,12 @@
 like this:
 
 .nf
-# Our command enhanced with a User-Defined Variable.
-# Remember that the variable has to be defined *before*
-# it is referenced.
+.B # Our command enhanced with a User-Defined Variable.
+.B # Remember that the variable has to be defined *before*
+.B # it is referenced.
 
-XTERM = xterm -l -e                 # This defines the variable
-m MyMore [XTERM] more somefile      # And the command then uses it
+.B XTERM = xterm -l -e                 # This defines the variable
+.B m MyMore [XTERM] more somefile      # And the command then uses it
 .fi
 
 .SS Environment Variables In A Command String
@@ -2039,11 +2074,11 @@
 looks like this:
 
 .nf
-# Our command using both a User-Defined Variable and 
-# an Environment Variable to make it more general
+.B # Our command using both a User-Defined Variable and 
+.B # an Environment Variable to make it more general
 
-XTERM = xterm -l -e
-m MyMore [XTERM] [$PAGER] somefile
+.B XTERM = xterm -l -e
+.B m MyMore [XTERM] [$PAGER] somefile
 .fi
 
 .SS Built-In Variables In A Command String
@@ -2064,11 +2099,11 @@
 
 
 .nf
-# Our command in its most generic form using
-# User-Defined, Environment, and Built-In Variables
+.B # Our command in its most generic form using
+.B # User-Defined, Environment, and Built-In Variables
 
-XTERM = xterm -l -e
-m MyMore [XTERM]  [$PAGER]  [DSELECTION]
+.B XTERM = xterm -l -e
+.B m MyMore [XTERM]  [$PAGER]  [DSELECTION]
 .fi
 
 The "DSELECTION" built-in is what communicates the currently
@@ -2152,16 +2187,16 @@
 command:
 
 .nf
-# Copy a group of items to a location set by
-# the user at runtime
-UnixCopy  = cp -R
-Win32Copy = copy
+.B # Copy a group of items to a location set by
+.B # the user at runtime
+.B UnixCopy  = cp -R
+.B Win32Copy = copy
 
-# Unix Version
-c UnixCP [UnixCopy]  [DSELECTIONS]  [PROMPT:Enter Destination]
+.B # Unix Version
+.B c UnixCP [UnixCopy]  [DSELECTIONS]  [PROMPT:Enter Destination]
 
-# Win32 Version
-C Win32CP [Win32Copy]   [DSELECTIONS]  [PROMPT:Enter Destination]
+.B # Win32 Version
+.B C Win32CP [Win32Copy]   [DSELECTIONS]  [PROMPT:Enter Destination]
 .fi
 
 .IP \(bu 4
@@ -2177,7 +2212,7 @@
 their intentions:
 
 .nf
-D BigDelete [YESNO:Are You Absolutely Sure About This?] rm -rf [SELECTIONS]
+.B D BigDelete [YESNO:Are You Absolutely Sure About This?] rm -rf [SELECTIONS]
 .fi
 
 .SS Program Memory Built-Ins
@@ -2196,7 +2231,7 @@
 a move command like this:
 
 .nf
-m move mv [MEM1] ./
+.B m move mv [MEM1] ./
 .fi
 
 .SS Notes On Built-In Variable Use
@@ -2219,28 +2254,28 @@
 selected item is:
 
 .nf
-# Unix Path Separator
-UPSEP = /
+.B # Unix Path Separator
+.B UPSEP = /
 
-#Win32 Path Separator
-WPSEP = \\
+.B #Win32 Path Separator
+.B WPSEP = \\
 
-[DIR][UPSEP][SELECTION]
+.B [DIR][UPSEP][SELECTION]
 
-or
+          - or -
 
-[DIR][WPSEP][SELECTION]
+.B [DIR][WPSEP][SELECTION]
 .fi
 
 Be aware that, because of \'twander\' quoting rules, such constructs
 will result in strings like:
 
 .nf
-"/mydir"/"myfile"
+.B "/mydir"/"myfile"
 
-or
+          - or -
 
-"C:\\mydir"\\"myfile"
+.B "C:\\mydir"\\"myfile"
 .fi
 
 This should not generally be a problem with the various Unix
@@ -2278,7 +2313,7 @@
 define a generic Unix copy command:
 
 .nf
-g gencopy cp -R  [PROMPT:Enter Source]  [PROMPT:Enter Destination]
+.B g gencopy cp -R  [PROMPT:Enter Source]  [PROMPT:Enter Destination]
 .fi
 
 When the user presses "g" (or clicks on "gencopy" on the Command
@@ -2369,7 +2404,7 @@
 .nf
 1) Select the ".." from the root directory of any drive.
 2) Enter the string "\\\\" from the CHANGDIR dialog.
-3) Press the DRIVELIST key (default: Control-k).
+3) Press the DRIVELIST key. (default: Control-k)
 4) Start \'twander\' using "\\\\" as the starting directory
    argument, either on the command line or using the 
    Configuration File STARTDIR option.
@@ -2414,7 +2449,7 @@
 This means if a drive is connected or a floppy is inserted into the
 system while in Drive List View, this fact will not be automatically
 noted.  You can force a manual update of the Drive List View by
-pressing the REFRESH key (default: Control-l).
+pressing the REFRESH key. (default: Control-l)
 
 .IP \(bu 4
 The TOGWIN32ALL key (default: Control-w) is disabled in Drive List
@@ -2435,8 +2470,8 @@
 select it as is appropriate.
 
 .SS Disabling \'win32all\' Features
-You can toggle these features on-and off using the TOGWIN32ALL key
-(default: Control-w).  You can also permanently disable them by
+You can toggle these features on-and off using the TOGWIN32ALL key.
+(default: Control-w)  You can also permanently disable them by
 setting the USEWIN32ALL option to False in the Configuration File.
 This allows you to leave \'win32all\' installed on your system 
 if you need it for other reasons but don't want these features
@@ -2463,7 +2498,7 @@
 taking place.  A simple way to do this with \'ksh\' or \'bash\' is:
 
 .nf
-export HOSTNAME=`hostname`
+.B export HOSTNAME=`hostname`
 .fi
 
 (Note the backticks used to execute the \'hostname\' program
@@ -2498,15 +2533,18 @@
 text:
 
 .nf
-encoding = "ascii" # Default value set by _PyUnicode_Init()
+.B encoding = "ascii" # Default value set by _PyUnicode_Init()
 
-if 0:
-    # Enable to support locale aware default string encodings.
-    import locale
+.B if 0:
+.B     # Enable to support locale aware default string encodings.
+.B     import locale
 .fi
 
-Change the "if 0:" statement to "if 1:" and the problem
-will disappear.
+Change the
+.B  if 0:
+statement to
+.B if 1:
+and the problem will disappear.
 
 
 .SS Getting Command Results Displayed In A New Window
@@ -2522,7 +2560,7 @@
 \'less\' to view files.  You would expect that this entry might do it:
 
 .nf
-V   view    less    [DSELECTIONS]
+.B V   view    less    [DSELECTIONS]
 .fi
 
 Sadly, this will not work, at least not the way you expect.
@@ -2540,7 +2578,7 @@
 File:
 
 .nf
-V   view         xterm -l -e less [DSELECTIONS]
+.B V   view         xterm -l -e less [DSELECTIONS]
 .fi
 
 This causes your command line program to execute in an \'xterm\'
@@ -2698,8 +2736,8 @@
 \'twander\' with the correct version of Python:
 
 .nf
-#!/bin/sh
-python2 twander.py $*
+.B #!/bin/sh
+.B python2 twander.py $*
 .fi
 
 .IP \(bu 4
@@ -2886,4 +2924,4 @@
 .nf
 Tim Daneliuk
 twander@tundraware.com
-
+.fi