about summary refs log tree commit diff stats
path: root/lynx_help/Lynx_users_guide.html
diff options
context:
space:
mode:
Diffstat (limited to 'lynx_help/Lynx_users_guide.html')
-rw-r--r--lynx_help/Lynx_users_guide.html8
1 files changed, 5 insertions, 3 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html
index 49cec8d3..b5e5cd5d 100644
--- a/lynx_help/Lynx_users_guide.html
+++ b/lynx_help/Lynx_users_guide.html
@@ -1096,7 +1096,7 @@ commands.
 	    document's author.
    <dt><em>;</em>
 	<dd>The <em>;</em> command shows the <em>Lynx Trace Log</em>
-	    (<em>lynx.trace</em> in the home directory) if one has been
+	    (<em>Lynx.trace</em> in the home directory) if one has been
 	    started for the current session.  If a log has not been started,
 	    any trace and other stderr messages will be sent to the screen
 	    (and will disturb the normal display) unless the system supports
@@ -2174,6 +2174,8 @@ where
 	     <dt><code>-startfile_ok</code>
 		<dd>allow non-http startfile and homepage with
 		    <em>-validate</em>.
+	     <dt><code>-tagsoup</code>
+		<dd>initialize DTD with "TagSoup" tables.
 	     <dt><code>-telnet</code>
 		<dd>disable recognition of telnet commands.
 	     <dt><code>-term=TERM</code>
@@ -2183,7 +2185,7 @@ where
 		    a script that, in turn, starts another Lynx process.)
 	     <dt><code>-tlog</code>
 		<dd>toggles use of a <em>Lynx Trace Log</em> for the current
-		    session.  The log is named <em>lynx.trace</em> and is
+		    session.  The log is named <em>Lynx.trace</em> and is
 		    created in the home directory when Lynx trace mode is
 		    turned on via the <em>-trace</em> command line switch
 		    (see below), or via the TOGGLE_TRACE (<em>Control-T</em>)
@@ -2194,7 +2196,7 @@ where
 		    keystroke command.
 	     <dt><code>-trace</code>
 		<dd>turns on Lynx trace mode.  If a Lynx Trace Log
-		    (<em>lynx.trace</em> in the home directory) has
+		    (<em>Lynx.trace</em> in the home directory) has
 		    been started for the current session, all trace and
 		    other stderr messages are written to that log, and
 		    can be examined during the session via the TRACE_LOG