about summary refs log tree commit diff stats
path: root/lynx_help/lynx_url_support.html
diff options
context:
space:
mode:
Diffstat (limited to 'lynx_help/lynx_url_support.html')
-rw-r--r--lynx_help/lynx_url_support.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
index 27f069ab..d0deb099 100644
--- a/lynx_help/lynx_url_support.html
+++ b/lynx_help/lynx_url_support.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">
-<HTML> 
+<HTML>
 <HEAD>
 <TITLE>URL Schemes Supported in Lynx</TITLE>
 <LINK rev=made href="mailto:lynx-dev@sig.net">
@@ -31,7 +31,7 @@ more details about URLs (Uniform Resource Locators) see <em>RFC1738</em>:
 <li><a href="http://www.w3.org/Addressing/rfc1738.txt"
 >http://www.w3.org/Addressing/rfc1738.txt</a>
 <li><a href="ftp://ds.internic.net/rfc/rfc1738.txt"
->ftp://ds.internic.net/rfc/rfc1738.txt</a>  
+>ftp://ds.internic.net/rfc/rfc1738.txt</a>
 </ul>
 
 <p>Lynx resolves partial or relative URLs in documents with respect to
@@ -41,7 +41,7 @@ absolute URL, using the rules described in <em>RFC1808</em>:
 <li><a href="http://www.w3.org/Addressing/rfc1808.txt"
 >http://www.w3.org/Addressing/rfc1808.txt</a>
 <li><a href="ftp://ds.internic.net/rfc/rfc1808.txt"
->ftp://ds.internic.net/rfc/rfc1808.txt</a>  
+>ftp://ds.internic.net/rfc/rfc1808.txt</a>
 </ul>
 
 and in subsequent drafts of the <em>IETF</em>:
@@ -90,7 +90,7 @@ which can correspond to positions in the rendering of the document.
 
 <p>The https URL has the same format, but the default port is <em>:443</em>.
 Patches for support of https URLs and the CONNECT procedure are available
-for qualified recipients via <a 
+for qualified recipients via <a
 href="http://www.crl.com/~subir/lynx.html">Lynx links</a>.  US Export laws
 and associated red tape pose severe impediments to inclusion of this support
 in the general distributions of freeware WWW clients such as Lynx.  Sorry.
@@ -100,7 +100,7 @@ in the general distributions of freeware WWW clients such as Lynx.  Sorry.
 >The <em>telnet</em>, <em>tn3270</em>, and <em>rlogin</em> URLs:</a></H2>
 
 A <em>telnet</em> URL generally results in Lynx spawning a telnet
-session. Lynx implements the complete telnet URL scheme, i.e.:<BR>
+session.  Lynx implements the complete telnet URL scheme, i.e.:<BR>
 <tab indent="12"><em>telnet://user:password@host:port</em>
 
 <p>The <em>user</em> and/or <em>:password</em> fields may be omitted, and
@@ -334,7 +334,7 @@ respectively, to standard nntp servers, with default port <em>:119</em>.
 Lynx now also supports homologous snewspost and snewsreply URLs for use
 with SSL capable nntp servers, but the latter requires patches for built
 in SSL support, or use of a daemon which handles the secure communications
-on behalf of Lynx. 
+on behalf of Lynx.
 
 <p>The formats are:<BR>
 <tab indent="12"><em>newspost://host:port/newsgroup(s)</em>&nbsp;&nbsp;<tab
@@ -577,7 +577,7 @@ find the self-restraint to <em>resist</em> that temptation!!!
 ><em>Return to your &lt;A HREF="LYNXHIST:0"&gt;Startfile&lt;/A&gt;</em><BR>
 <tab indent="12"
 ><em>Review your &lt;A HREF="LYNXKEYMAP:"&gt;Keymap&lt;/A&gt;</em><BR>
-(Yes, they'll work. No, they won't do any harm. But...)
+(Yes, they'll work.  No, they won't do any harm.  But...)
 
 <p>If you <em>must</em> try one, the second is OK from the command line:<BR>
 <tab indent="12"><em>lynx LYNXKEYMAP:</em><BR>