snapshot of project "lynx", label v2-8-2dev_5

1 files changed, 11 insertions, 9 deletions

diff --git a/lynx.cfg b/lynx.cfg
index ece995a7..c6a4d9bc 100644
--- a/lynx.cfg
+++ b/lynx.cfg
@@ -8,7 +8,7 @@
 #
 #  If you do not have write access to /usr/local/bin you may change
 #  the default location of this file in the userdefs.h file and recompile,
-#  or specify it's location on the command line with the "-cfg"
+#  or specify its location on the command line with the "-cfg"
 #  command line option.
 #
 # Items may be commented out by putting a '#' as the FIRST char of the line
@@ -30,7 +30,7 @@
 # Then in ~/lynx.cfg:
 #
 #INCLUDE:/usr/local/lib/lynx.cfg
-#       ^^^^^^^^^^^^^^^^^^^^^^^ or whatever's appropriate on your system
+#       ^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system
 #and now your own tweaks.
 
 #
@@ -86,7 +86,7 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 # the user presses the 'J' (JUMP) key.  The user will be prompted for
 # a shortcut entry (analogously to 'g'oto), and can enter one
 # or use '?' for a list of the shortcuts with associated links to
-# their actual URL's.  See the jumps files in the lynx*/samples
+# their actual URLs.  See the jumps files in the lynx*/samples
 # subdirectory.  Make sure your jumps file includes a '?' shortcut
 # for a file://localhost URL to itself:
 #
@@ -262,6 +262,7 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 #
 # The value should be the MIME name of a character set recognized by
 # Lynx (case insensitive).
+# Find RFC 1345 at http://www.ics.uci.edu/pub/ietf/uri/rfc1345.txt .
 #
 #CHARACTER_SET:iso-8859-1
 
@@ -364,7 +365,8 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 # and if the server cannot send a response which is acceptable
 # according to the Accept-Charset header, then the server SHOULD send
 # an error response with the 406 (not acceptable) status code, though
-# the sending of an unacceptable response is also allowed.  See RFC2068.
+# the sending of an unacceptable response is also allowed.  See RFC 2068
+# (http://www.ics.uci.edu/pub/ietf/uri/rfc2068.txt).
 #
 #PREFERRED_CHARSET:
 
@@ -590,9 +592,9 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 # If LOCAL_EXECUTION_LINK_ON_BUT_NOT_REMOTE is TRUE, and no TRUSTED_EXEC
 # rule is defined, it defaults to "file://localhost/" and any lynxexec
 # or lynxprog command will be permitted if it was referenced with a URL
-# beginning with that string.  If you wish to restrict the referencing URL's
+# beginning with that string.  If you wish to restrict the referencing URLs
 # further, you can extend the string to include a trusted path.  You also can
-# specify a trusted directory for http URL's, which will then be treated as
+# specify a trusted directory for http URLs, which will then be treated as
 # if they were local rather than remote.  For example:
 #
 #	TRUSTED_EXEC:file://localhost/trusted/
@@ -617,10 +619,10 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 # rules below, you need not repeat them as TRUSTED_EXEC rules.
 #
 # If EXEC_LINKS and JUMPFILE have been defined, any lynxexec or lynxprog
-# URL's in that file will be permitted, regardless of other settings.  If
+# URLs in that file will be permitted, regardless of other settings.  If
 # you also set LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE and a single
 # TRUSTED_EXEC rule that will always fail (e.g., "none"), then *ONLY* the
-# lynxexec or lynxprog URL's in JUMPFILE (and any ALWAYS_TRUSTED_EXEC rules,
+# lynxexec or lynxprog URLs in JUMPFILE (and any ALWAYS_TRUSTED_EXEC rules,
 # see below) will be allowed.  Note, however, that if Lynx was compiled with
 # CAN_ANONYMOUS_JUMP set to FALSE (default is TRUE), or -restrictions=jump
 # is included with the -anonymous switch at run time, then users of an
@@ -1229,7 +1231,7 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 
 # If HISTORICAL_COMMENTS is TRUE, Lynx will revert to the "Historical"
 # behavior of treating any '>' as a terminator for comments, instead of
-# seeking a valid '-->' terminator (note that white space can be present 
+# seeking a valid '-->' terminator (note that white space can be present
 # between the '--' and '>' in valid terminators).  The compilation default
 # is FALSE.
 #