summaryrefslogtreecommitdiffstats
path: root/htdocs/docs/users.html
diff options
context:
space:
mode:
Diffstat (limited to 'htdocs/docs/users.html')
-rwxr-xr-xhtdocs/docs/users.html24
1 files changed, 12 insertions, 12 deletions
diff --git a/htdocs/docs/users.html b/htdocs/docs/users.html
index 0479887..eb95f34 100755
--- a/htdocs/docs/users.html
+++ b/htdocs/docs/users.html
@@ -1,11 +1,11 @@
-<!--#set var="revision" value="\$Id: users.html,v 1.6 2002-08-20 01:51:24 link Exp $"
---><!--#set var="date" value="\$Date: 2002-08-20 01:51:24 $"
+<!--#set var="revision" value="\$Id: users.html,v 1.7 2002-09-08 19:37:42 ville Exp $"
+--><!--#set var="date" value="\$Date: 2002-09-08 19:37:42 $"
--><!--#set var="title" value="User Documentation for The W3C HTML Validation Service"
--><!--#set var="relroot" value="../"
--><!--#include virtual="../header.html" -->
<div id="Quickstart">
- <h2 id="skip">QuickStart</h2>
+ <h2 id="skip">Quick Start</h2>
<p>
Just type (or Cut&amp;Paste) the URL for the page you want to validate
into the text field on the form and press the "Validate this page"
@@ -13,7 +13,7 @@
</p>
<p>
If you have a local file you want to validate, choose the "File Upload"
- link from the navigation menu. Select the button labelled "Browse..."
+ link from the navigation menu. Select the button labeled "Browse..."
(or something like that, depending on your browser) and choose the file
you want to upload in the usual manner for your OS.
</p>
@@ -27,9 +27,9 @@
objective syntax rules called a "DTD", a Document Type Definition. This
way you can be sure your HTML is really valid and not just that it
conforms to some random programmer's idea of "nice" HTML. Note that
- valid HTML does not guarantee that your pages will work ok in all
- browsers. Most of them are severly broken and you may need to find
- alternate ways of achieveing your goal.
+ valid HTML does not guarantee that your pages will work OK in all
+ browsers. Most of them are severely broken and you may need to find
+ alternate ways of achieving your goal.
</p>
<p>
When you send an URL to the W3C HTML Validation Service, it will fetch
@@ -72,7 +72,7 @@
constructs.
</dd>
<dt>exclude attributes from the parse tree (<code>noatt</code>)</dt>
- <dd>Supress attributes from the parse tree to make it more readable.</dd>
+ <dd>Suppress attributes from the parse tree to make it more readable.</dd>
</dl>
</div>
@@ -82,7 +82,7 @@
You can link directly to the Validator home page, or you can call the
Validator CGI program. The home page is &lt;URL:<a
href="http://validator.w3.org/">http://validator.w3.org/</a>&gt; at
- the moment (and for the forseeable future) and the CGI program can be
+ the moment (and for the foreseeable future) and the CGI program can be
reached at &lt;URL:<a
href="http://validator.w3.org/check">http://validator.w3.org/check</a>&gt;.
</p>
@@ -101,14 +101,14 @@
</p>
<p>
The various options are listed above in the section
- "<a href="#Options">The Options</a>" in paranthesis after the long
+ "<a href="#Options">The Options</a>" in parenthesis after the long
name. To add options to your links directly, append the options
separated by a semi-colon. For example &lt;URL:<a href="http://validator.w3.org/check?uri=http://www.example.com/;ss;outline;sp">http://validator.w3.org/check?uri=http://www.example.com/;ss;outline;sp</a>&gt;
will validate the example.com home page with "Show Source", "Outline" and
"Show Parse Tree" on, but "Exclude Attributes" off.
</p>
<p>
- You may also see these separated by amperstands and equal-signs, but
+ You may also see these separated by ampersands and equal-signs, but
this usage is deprecated and support may be removed at some time in the
future.
</p>
@@ -123,7 +123,7 @@
average HTML document. We're working on ways to make the error messages
more friendly, but for now feel free to email the
<a href="mailto:www-validator@w3.org">www-validator@w3.org</a>
- mailinglist if you need help interpreting the results. This will have
+ mailing list if you need help interpreting the results. This will have
the added benefit of letting us know which error messages are causing
the most trouble so we can fix those first. Please be as specific as
possible and include the <em>exact</em> error message and, preferably, an URL