snapshot of project "lynx", label v2-8-3dev_17

1 files changed, 3 insertions, 3 deletions

diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
index ec0fe551..b270f618 100644
--- a/lynx_help/lynx_url_support.html
+++ b/lynx_help/lynx_url_support.html
@@ -594,7 +594,7 @@ within Lynx.
 
 <H2><a name="internal">The <em>LYNXfoo</em> internal URLs:</a></H2>
 
-Lynx uses a variety of private URL schemes form communication among its
+Lynx uses a variety of private URL schemes for communication among its
 internal modules.  They start with uppercase letters <code>LYNX</code>
 by convention, although, as input, URL schemes are recognized in a
 case-insensitive manner.
@@ -604,7 +604,7 @@ documents, you should <em>resist</em> that temptation:
 <UL><LI>There already is too much browser-specific markup around...
 <LI>The schemes, or their meanings, may change between Lynx versions.
 <LI>Even if a scheme stays the same, some aspect of its behavior may
-    be modified without notice, or the context in which it is allows
+    be modified without notice, or the context in which it is allowed
     may change.
 <LI>If it doesn't work as expected when used outside of the intended
     purpose, don't expect anyone to "fix" it.
@@ -622,7 +622,7 @@ documents, you should <em>resist</em> that temptation:
       <em>lynx LYNXKEYMAP:</em>
 </pre>
 But within Lynx, use the '<em>K</em>' keystroke command.
-Sometimes it may be convenient to use an internal scheme with
+Sometimes it may be convenient to use a private scheme with
 '<em>g</em>'oto, as in:
 <pre>
       <em>g LYNXMESSAGES:</em>