lynx-dev minor typo patch for lynx.cfg in lynx 2.8.2dev.4

[Larry W. Virden]

--- lynx.cfg-dist       Wed Nov 18 14:23:55 1998
+++ lynx.cfg-new        Wed Nov 18 17:33:46 1998
@@ -10,3 +10,3 @@
 #  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.
@@ -32,3 +32,3 @@
 #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.
@@ -88,3 +88,3 @@
 # 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
@@ -264,2 +264,3 @@
 # Lynx (case insensitive).
+# Find RFC 1345 at http://www.ics.uci.edu/pub/ietf/uri/rfc1345.txt .
 #
@@ -366,3 +367,4 @@
 # 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).
 #
@@ -501,4 +503,4 @@
 #
-# The Unix and VMS (but not VAXC) implementations use the C library malloc's
-# and calloc's for memory allocation, but procedures for taking the actual
+# The Unix and VMS (but not VAXC) implementations use the C library mallocs
+# and callocs for memory allocation, but procedures for taking the actual
 # amount of cache into account still need to be developed.  They use only
@@ -592,5 +594,5 @@
 # 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:
@@ -619,6 +621,6 @@
 # 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
-- 
Larry W. Virden                 <URL:mailto:address@hidden>
<URL:http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.