[html5] r2963 - [e] (0) Typos: round 1.
whatwg at whatwg.org
whatwg at whatwg.org
Fri Apr 17 23:33:46 PDT 2009
Author: ianh
Date: 2009-04-17 23:33:45 -0700 (Fri, 17 Apr 2009)
New Revision: 2963
Modified:
index
source
Log:
[e] (0) Typos: round 1.
Modified: index
===================================================================
--- index 2009-04-18 01:16:51 UTC (rev 2962)
+++ index 2009-04-18 06:33:45 UTC (rev 2963)
@@ -2640,7 +2640,7 @@
the order given, aborting at the first step that returns a
value. This algorithm will either return a number greater than or
equal to 1.0, or an error; if a number is returned, then it is
- further categorised as either a percentage or a length.</p>
+ further categorized as either a percentage or a length.</p>
<ol><li><p>Let <var title="">input</var> be the string being
parsed.</li>
@@ -3098,7 +3098,7 @@
<h5 id=months><span class=secno>2.4.5.1 </span>Months</h5>
<p>A <dfn id=concept-month title=concept-month>month</dfn> consists of a specific
- proleptic Gregorian date with no timezone information and no date
+ proleptic Gregorian date with no time-zone information and no date
information beyond a year and a month. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
<p>A string is a <dfn id=valid-month-string>valid month string</dfn> representing a year
@@ -3170,8 +3170,8 @@
<h5 id=dates><span class=secno>2.4.5.2 </span>Dates</h5>
<p>A <dfn id=concept-date title=concept-date>date</dfn> consists of a specific
- proleptic Gregorian date with no timezone information, consisting of
- a year, a month, and a day. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
+ proleptic Gregorian date with no time-zone information, consisting
+ of a year, a month, and a day. <a href=#refsGREGORIAN>[GREGORIAN]</a></p>
<p>A string is a <dfn id=valid-date-string>valid date string</dfn> representing a year
<var title="">year</var>, month <var title="">month</var>, and day
@@ -3242,7 +3242,7 @@
<h5 id=times><span class=secno>2.4.5.3 </span>Times</h5>
<p>A <dfn id=concept-time title=concept-time>time</dfn> consists of a specific
- time with no timezone information, consisting of an hour, a minute,
+ time with no time-zone information, consisting of an hour, a minute,
a second, and a fraction of a second.</p>
<p>A string is a <dfn id=valid-time-string>valid time string</dfn> representing an hour
@@ -3443,7 +3443,7 @@
-->
<p>A string is a <dfn id=valid-global-date-and-time-string>valid global date and time string</dfn>
- representing a date, time, and a timezone offset if it consists of
+ representing a date, time, and a time-zone offset if it consists of
the following components in the given order:</p>
<ol><li>A <a href=#valid-date-string>valid date string</a> representing the date</li>
@@ -3461,17 +3461,17 @@
<ol><li>Either a U+002B PLUS SIGN character (+) or a U+002D
HYPHEN-MINUS (-) character, representing the sign of the
- timezone offset</li>
+ time-zone offset</li>
<li>Two <a href=#concept-datetime-digit title=concept-datetime-digit>digits</a>,
representing the hours component <var title="">hour</var> of
- the timezone offset, in the range 0 ≤ <var title="">hour</var> ≤ 23</li>
+ the time-zone offset, in the range 0 ≤ <var title="">hour</var> ≤ 23</li>
<li>A U+003A COLON character (:)</li>
<li>Two <a href=#concept-datetime-digit title=concept-datetime-digit>digits</a>,
representing the minutes component <var title="">minute</var>
- of the timezone offset, in the range 0 ≤ <var title="">minute</var> ≤ 59</li>
+ of the time-zone offset, in the range 0 ≤ <var title="">minute</var> ≤ 59</li>
</ol></li>
@@ -3520,7 +3520,7 @@
used. However, it seems unlikely that it would be given in the
Gregorian calendar, so I assume sites use the Julian one. -->
- <li>The time and timezone components are not optional.</li>
+ <li>The time and time-zone components are not optional.</li>
<li>Dates before the year zero can't be represented as a datetime
in this version of HTML.</li>
@@ -3533,7 +3533,7 @@
<p>The rules to <dfn id=parse-a-global-date-and-time-string>parse a global date and time string</dfn> are
as follows. This will either return a time in UTC, with associated
- timezone information for round tripping or display purposes, or
+ time-zone information for round tripping or display purposes, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.</p>
@@ -3553,7 +3553,7 @@
<li><p>If <var title="">position</var> is beyond the end of <var title="">input</var>, then fail.</li>
- <li><p><a href=#parse-a-timezone-component>Parse a timezone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns
+ <li><p><a href=#parse-a-time-zone-component>Parse a time-zone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns
nothing, then fail.</p>
<li><p>If <var title="">position</var> is <em>not</em> beyond the
@@ -3564,15 +3564,15 @@
subtracting <var title="">timezone<sub title="">hours</sub></var>
hours and <var title="">timezone<sub title="">minutes</sub></var>
minutes. That moment in time is a moment in the UTC
- timezone.</li>
+ time zone.</li>
<li><p>Let <var title="">timezone</var> be <var title="">timezone<sub title="">hours</sub></var> hours and <var title="">timezone<sub title="">minutes</sub></var> minutes from
UTC.</li>
<li><p>Return <var title="">time</var> and <var title="">timezone</var>.</li>
- </ol><p>The rules to <dfn id=parse-a-timezone-component>parse a timezone component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
- as follows. This will either return timezone hours and timezone
+ </ol><p>The rules to <dfn id=parse-a-time-zone-component>parse a time-zone component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
+ as follows. This will either return time-zone hours and time-zone
minutes, or nothing. If at any point the algorithm says that it
"fails", this means that it is aborted at that point and returns
nothing.</p>
@@ -3796,8 +3796,8 @@
<li><p>If the <var title="">time present</var> flag is true, but
<var title="">position</var> is beyond the end of <var title="">input</var>, then fail.</li>
- <li><p>If the <var title="">date present</var> and <var title="">time present</var> flags are both true, <a href=#parse-a-timezone-component>parse a
- timezone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns nothing, then
+ <li><p>If the <var title="">date present</var> and <var title="">time present</var> flags are both true, <a href=#parse-a-time-zone-component>parse a
+ time-zone component</a> to obtain <var title="">timezone<sub title="">hours</sub></var> and <var title="">timezone<sub title="">minutes</sub></var>. If this returns nothing, then
fail.</p>
<li><p>For the <i>in content</i> variant: <a href=#skip-white_space-characters>skip White_Space
@@ -3820,7 +3820,7 @@
at year <var title="">year</var>, month <var title="">month</var>,
day <var title="">day</var>, hours <var title="">hour</var>,
minute <var title="">minute</var>, second <var title="">second</var>, subtracting <var title="">timezone<sub title="">hours</sub></var> hours and <var title="">timezone<sub title="">minutes</sub></var> minutes, that moment in time being a
- moment in the UTC timezone; let <var title="">timezone</var> be
+ moment in the UTC time zone; let <var title="">timezone</var> be
<var title="">timezone<sub title="">hours</sub></var> hours and
<var title="">timezone<sub title="">minutes</sub></var> minutes
from UTC; and return <var title="">time</var> and <var title="">timezone</var>.</p>
@@ -4512,7 +4512,7 @@
<li>
<p>If parsing <var title="">url</var> resulted in a <a href=#url-host title=url-host><host></a> component, then replace the
- matching subtring of <var title="">url</var> with the string that
+ matching substring of <var title="">url</var> with the string that
results from expanding any sequences of percent-encoded octets in
that component that are valid UTF-8 sequences into Unicode
characters as defined by UTF-8.</p>
@@ -6970,7 +6970,7 @@
<p>The <dfn id=dom-document-lastmodified title=dom-document-lastModified><code>lastModified</code></dfn>
attribute, on getting, must return the date and time of the
<code>Document</code>'s source file's last modification, in the
- user's local timezone, in the following format:</p>
+ user's local time zone, in the following format:</p>
<ol><li> The month component of the date. </li>
@@ -7925,7 +7925,7 @@
any language information, the default value is unknown (the empty
string).</p>
- <p>If the resulting value is not a recognised language code, then it
+ <p>If the resulting value is not a recognized language code, then it
must be treated as an unknown language (as if the value was the
empty string).</p>
@@ -7983,11 +7983,11 @@
directionality</a> of the element is the directionality used by
the presentation layer, potentially determined from the value of the
<code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute on the
- element. Otherwise, if the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute has the state <i>ltr</i>,
- the element's directionality is 'ltr' (left-to-right); if the
- attribute has the state <i>rtl</i>, the element's directionality
- is 'rtl' (right-to-left); and oherwise, the element's directionality
- is the same as its parent element, or 'ltr' if there is no parent
+ element. Otherwise, if the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute has the state <i>ltr</i>, the
+ element's directionality is 'ltr' (left-to-right); if the attribute
+ has the state <i>rtl</i>, the element's directionality is 'rtl'
+ (right-to-left); and otherwise, the element's directionality is the
+ same as its parent element, or 'ltr' if there is no parent
element.</p>
<hr><dl class=domintro><dt><var title="">document</var> . <code title=dom-dir><a href=#dom-dir>dir</a></code> [ = <var title="">value</var> ]</dt>
@@ -8342,8 +8342,8 @@
embedded content are all types of flow content. Embedded content is
also a type of phrasing content." src=images/content-venn.png></object></p>
- <p>In addition, certain elements are categorised as <a href=#form-associated-element title="form-associated element">form-associated elements</a> and
- further subcategorised so so to define their role in various
+ <p>In addition, certain elements are categorized as <a href=#form-associated-element title="form-associated element">form-associated elements</a> and
+ further subcategorized so so to define their role in various
form-related processing models.</p>
<!-- XXX list all the elements for each kind of element in the
@@ -8366,7 +8366,7 @@
<div class=example>
- <p>Thus, in the XML serialisation, one can use RDF, like this:</p>
+ <p>Thus, in the XML serialization, one can use RDF, like this:</p>
<pre><html xmlns="http://www.w3.org/1999/xhtml"
xmlns:r="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
@@ -8388,7 +8388,7 @@
</body>
</html></pre>
- <p>This isn't possible in the HTML serialisation, however.</p>
+ <p>This isn't possible in the HTML serialization, however.</p>
</div>
@@ -8977,7 +8977,7 @@
<li><p>Create a new <a href=#html-parser>HTML parser</a> and associate it with
the document. This is a <dfn id=script-created-parser>script-created parser</dfn> (meaning
that it can be closed by the <code title=dom-document-open><a href=#dom-document-open>document.open()</a></code> and <code title=dom-document-close><a href=#dom-document-close>document.close()</a></code> methods, and
- that the tokeniser will wait for an explicit call to <code title=dom-document-close><a href=#dom-document-close>document.close()</a></code> before emitting
+ that the tokenizer will wait for an explicit call to <code title=dom-document-close><a href=#dom-document-close>document.close()</a></code> before emitting
an end-of-file token). The encoding <a href=#concept-encoding-confidence title=concept-encoding-confidence>confidence</a> is
<i>irrelevant</i>.</li>
@@ -8997,7 +8997,7 @@
<p>If <var title="">type</var> is <em>not</em> now an <a href=#ascii-case-insensitive>ASCII
case-insensitive</a> match for the string
- "<code>text/html</code>", then act as if the tokeniser had emitted
+ "<code>text/html</code>", then act as if the tokenizer had emitted
a start tag token with the tag name "pre", then set the <a href=#html-parser>HTML
parser</a>'s <a href=#tokenization>tokenization</a> stage's <a href=#content-model-flag>content
model flag</a> to <i>PLAINTEXT</i>.</p>
@@ -9121,12 +9121,12 @@
<li>
- <p>Otherwise, the tokeniser must process the characters that were
+ <p>Otherwise, the tokenizer must process the characters that were
inserted, one at a time, processing resulting tokens as they are
- emitted, and stopping when the tokeniser reaches the insertion
- point or when the processing of the tokeniser is aborted by the
+ emitted, and stopping when the tokenizer reaches the insertion
+ point or when the processing of the tokenizer is aborted by the
tree construction stage (this can happen if a <code><a href=#script>script</a></code>
- end tag token is emitted by the tokeniser).
+ end tag token is emitted by the tokenizer).
<p class=note>If the <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code> method was
called from script executing inline (i.e. executing because the
@@ -9676,7 +9676,7 @@
<p>The next page might be a part of the same site. Note how the
title describes the subject matter unambiguously, while the first
- header assumes the reader knowns what the context is and therefore
+ header assumes the reader knows what the context is and therefore
won't wonder if the dances are Salsa or Waltz:</p>
<pre> <title>Dances used during bee mating rituals</title>
@@ -10531,7 +10531,7 @@
<li><p>If the character in <var title="">input</var> pointed to
by <var title="">position</var> is either a U+0027 APOSTROPHE
character (') U+0022 QUOTATION MARK character ("), then let <var title="">quote</var> be that character, and advance <var title="">position</var> to the next character. Otherwise, let
- <var title="">quote</var> be the empty stirng.</li>
+ <var title="">quote</var> be the empty string.</li>
<li><p>Let <var title="">url</var> be equal to the substring of
<var title="">input</var> from the character at <var title="">position</var> to the end of the string.</li>
@@ -10671,7 +10671,7 @@
or character escapes of any kind.</li>
<li id=charset512>The element containing the character encoding
- declaration must be serialised completely within the first 512
+ declaration must be serialized completely within the first 512
bytes of the document.</li>
<li>There can only be one character encoding declaration in the
@@ -11090,7 +11090,7 @@
<li>The <code><a href=#script>script</a></code> element's child nodes are changed.</li>
<li>The <code><a href=#script>script</a></code> element has a <code title=attr-script-src><a href=#attr-script-src>src</a></code> attribute set where previously
- the elment had no such attribute.</li>
+ the element had no such attribute.</li>
</ul><p><dfn id=running-a-script title="running a script">Running a script</dfn>: When a
<code><a href=#script>script</a></code> element is to be run, the user agent must act as
@@ -11949,9 +11949,9 @@
<nav>
<h1>Navigation</h1>
<ul>
- <li><a href="articles.html">Index of all articles</a><li>
- <li><a href="today.html">Things sheeple need to wake up for today</a><li>
- <li><a href="successes.html">Sheeple we have managed to wake</a><li>
+ <li><a href="articles.html">Index of all articles</a></li>
+ <li><a href="today.html">Things sheeple need to wake up for today</a></li>
+ <li><a href="successes.html">Sheeple we have managed to wake</a></li>
</ul>
</nav>
<article>
@@ -12148,7 +12148,7 @@
<div class=example>
<p>Here are some examples of valid headers. In each case, the
- emphasised text represents the text that would be used as the
+ emphasized text represents the text that would be used as the
header in an application extracting header data and ignoring
subheadings.</p>
@@ -13663,7 +13663,7 @@
provided to convert the markup into a cloud of differently-sized
words, but for user agents that do not support CSS or are not
visual, the markup contains annotations like "(popular)" or
- "(rare)" to categorise the various tags by frequency, thus enabling
+ "(rare)" to categorize the various tags by frequency, thus enabling
all users to benefit from the information.</p>
<p>The <code><a href=#the-ul-element>ul</a></code> element is used (rather than
@@ -13996,9 +13996,9 @@
<p>This next example shows a typical use of the <code><a href=#the-cite-element>cite</a></code>
element:</p>
- <pre><p>My favourite book is <cite>The Reality Dysfunction</cite> by
-Peter F. Hamilton. My favourite comic is <cite>Pearls Before
-Swine</cite> by Stephan Pastis. My favourite track is <cite>Jive
+ <pre><p>My favorite book is <cite>The Reality Dysfunction</cite> by
+Peter F. Hamilton. My favorite comic is <cite>Pearls Before
+Swine</cite> by Stephan Pastis. My favorite track is <cite>Jive
Samba</cite> by the Cannonball Adderley Sextet.</p></pre>
</div>
@@ -14195,7 +14195,7 @@
is also sometimes used for attribution.</p>
<p class=note>The <code><a href=#the-small-element>small</a></code> element does not
- "de-emphasize" or lower the importance of text emphasised by the
+ "de-emphasize" or lower the importance of text emphasized by the
<code><a href=#the-em-element>em</a></code> element or marked as important with the
<code><a href=#the-strong-element>strong</a></code> element.</p>
@@ -14321,7 +14321,7 @@
<p>This is another example showing the use of <code><a href=#the-mark-element>mark</a></code> to
highlight a part of quoted text that was originally not
- emphasised. In this example, common typographic conventions have
+ emphasized. In this example, common typographic conventions have
led the author to explicitly style <code><a href=#the-mark-element>mark</a></code> elements in
quotes to render in italics.</p>
@@ -14662,7 +14662,7 @@
<p>I've liked model trains since at least 1983.</p></pre>
<p>Using a styling technology that supports restyling times, the
- first paragraph from the above snipet could be rendered as follows:</p>
+ first paragraph from the above snippet could be rendered as follows:</p>
<blockquote><p>I usually have a snack at 4pm.</blockquote>
@@ -14677,7 +14677,7 @@
<p>The <dfn id=dom-time-datetime title=dom-time-datetime><code>dateTime</code></dfn> DOM
attribute must <a href=#reflect>reflect</a> the <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code> content attribute.</p>
- <p>User agents, to obtain the <dfn id=concept-time-date title=concept-time-date>date</dfn>, <dfn id=concept-time-time title=concept-time-time>time</dfn>, and <dfn id=concept-time-timezone title=concept-time-timezone>timezone</dfn> represented by a
+ <p>User agents, to obtain the <dfn id=concept-time-date title=concept-time-date>date</dfn>, <dfn id=concept-time-time title=concept-time-time>time</dfn>, and <dfn id=concept-time-timezone title=concept-time-timezone>time zone</dfn> represented by a
<code><a href=#the-time-element>time</a></code> element, must follow these steps:</p>
<ol><li>If the <code title=attr-time-datetime><a href=#attr-time-datetime>datetime</a></code>
@@ -14692,13 +14692,13 @@
<li>If <var title="">result</var> is empty (because the parsing
failed), then the <a href=#concept-time-date title=concept-time-date>date</a> is
unknown, the <a href=#concept-time-time title=concept-time-time>time</a> is unknown,
- and the <a href=#concept-time-timezone title=concept-time-timezone>timezone</a> is
+ and the <a href=#concept-time-timezone title=concept-time-timezone>time zone</a> is
unknown.</li>
<li>Otherwise: if <var title="">result</var> contains a date, then
- that is the <a href=#concept-time-date title=concept-time-date>date</a>; if <var title="">result</var> contains a time, then that is the <a href=#concept-time-time title=concept-time-time>time</a>; and if <var title="">result</var> contains a timezone, then the timezone is the
- element's <a href=#concept-time-timezone title=concept-time-timezone>timezone</a>. (A
- timezone can only be present if both a date and a time are also
+ that is the <a href=#concept-time-date title=concept-time-date>date</a>; if <var title="">result</var> contains a time, then that is the <a href=#concept-time-time title=concept-time-time>time</a>; and if <var title="">result</var> contains a time zone, then the time zone is the
+ element's <a href=#concept-time-timezone title=concept-time-timezone>time zone</a>. (A
+ time zone can only be present if both a date and a time are also
present.)</li>
</ol></div>
@@ -14709,7 +14709,7 @@
<p>Returns a <code>Date</code> object representing the date
component of the element's value, at midnight in the UTC
- timezone.</p>
+ time zone.</p>
<p>Returns null if there is no date.</p>
@@ -14721,7 +14721,7 @@
<p>Returns a <code>Date</code> object representing the time
component of the element's value, on 1970-01-01 in the UTC
- timezone.</p>
+ time zone.</p>
<p>Returns null if there is no time.</p>
@@ -14732,10 +14732,10 @@
<dd>
<p>Returns a <code>Date</code> object representing the time
- corresponding to 1970-01-01 00:00 UTC in the timezone given by the
+ corresponding to 1970-01-01 00:00 UTC in the time zone given by the
element's value.</p>
- <p>Returns null if there is no timezone.</p>
+ <p>Returns null if there is no time zone.</p>
</dd>
@@ -14750,14 +14750,14 @@
must return null if the <a href=#concept-time-time title=concept-time-time>time</a> is
unknown, and otherwise must return the time corresponding to the
given <a href=#concept-time-time title=concept-time-time>time</a> of 1970-01-01, with
- the timezone UTC.</p>
+ the time zone UTC.</p>
<p>The <dfn id=dom-time-timezone title=dom-time-timezone><code>timezone</code></dfn> DOM
- attribute must return null if the <a href=#concept-time-timezone title=concept-time-timezone>timezone</a> is unknown, and otherwise
+ attribute must return null if the <a href=#concept-time-timezone title=concept-time-timezone>time zone</a> is unknown, and otherwise
must return the time corresponding to 1970-01-01 00:00 UTC in the
- given <a href=#concept-time-timezone title=concept-time-timezone>timezone</a>, with the
- timezone set to UTC (i.e. the time corresponding to 1970-01-01 at
- 00:00 UTC plus the offset corresponding to the timezone).</p>
+ given <a href=#concept-time-timezone title=concept-time-timezone>time zone</a>, with the
+ time zone set to UTC (i.e. the time corresponding to 1970-01-01 at
+ 00:00 UTC plus the offset corresponding to the time zone).</p>
</div>
@@ -15103,11 +15103,11 @@
<p>If the <code title=attr-meter-min><a href=#attr-meter-min>min</a></code> attribute
attribute is specified, then the <var title="">minimum</var> is
- that attribue's value; otherwise, it is 0.</p>
+ that attribute's value; otherwise, it is 0.</p>
<p>If the <code title=attr-meter-max><a href=#attr-meter-max>max</a></code> attribute
attribute is specified, then the <var title="">maximum</var> is
- that attribue's value; otherwise, it is 1.</p>
+ that attribute's value; otherwise, it is 1.</p>
<p>If there is exactly one number in the contents of the element,
then <var title="">value</var> is that number; otherwise, <var title="">value</var> is the value of the <code title=attr-meter-value><a href=#attr-meter-value>value</a></code> attribute.</p>
@@ -15499,7 +15499,7 @@
variable in prose:</p>
<pre><p>If there are <var>n</var> pipes leading to the ice
cream factory then I expect at <em>least</em> <var>n</var>
-flavours of ice cream to be available for purchase!</p></pre>
+flavors of ice cream to be available for purchase!</p></pre>
</div>
<p>For mathematics, in particular for anything beyond the simplest
@@ -16280,7 +16280,7 @@
timestamp (the value is non-conforming; it is not a <a href=#valid-global-date-and-time-string>valid
global date and time string</a>). Otherwise, the modification is
marked as having been made at the given datetime. User agents should
- use the associated timezone information to determine which timezone
+ use the associated time-zone information to determine which time zone
to present the given datetime in.</p>
</div>
@@ -16378,7 +16378,7 @@
<p>In the following example, a list that started empty had items
added and removed from it over time. The bits in the example that
- have been emphasised show the parts that are the "current" state of
+ have been emphasized show the parts that are the "current" state of
the list. The list item numbers don't take into account the edits,
though.</p>
@@ -16691,7 +16691,7 @@
(e.g. scripts) embedded in the image resource. User agents must only
display the first page of a multipage resource (e.g. a PDF
file). User agents must not allow the resource to act in an
- interactive fashion, but should honour any animation in the
+ interactive fashion, but should honor any animation in the
resource.</p>
<p>This specification does not specify which image types are to be
@@ -16997,7 +16997,7 @@
<pre><article>
<h1>My cats</h1>
<h2>Fluffy</h2>
- <p>Fluffy is my favourite.</p>
+ <p>Fluffy is my favorite.</p>
<img src="fluffy.jpg" alt="She likes playing with a ball of yarn.">
<p>She's just too cute.</p>
<h2>Miles</h2>
@@ -17122,10 +17122,10 @@
<pre><p>In the common case, the data handled by the tokenization stage
comes from the network, but it can also come from script.</p>
<p><strong><img src="images/parsing-model-overview.png" alt="The network
-passes data to the Tokeniser stage, which passes data to the Tree
+passes data to the Tokenizer stage, which passes data to the Tree
Construction stage. From there, data goes to both the DOM and to
Script Execution. Script Execution is linked to the DOM, and, using
-document.write(), passes data to the Tokeniser."></strong></p></pre>
+document.write(), passes data to the Tokenizer."></strong></p></pre>
</div>
@@ -17331,11 +17331,11 @@
<p>A flowchart that repeats the previous paragraph in graphical form:</p>
- <pre><p>The network passes data to the Tokeniser stage, which
+ <pre><p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<strong><p><img src="images/parsing-model-overview.png" alt=""></p></strong></pre>
<p>In these cases, it would be wrong to include alternative text
@@ -17347,36 +17347,36 @@
representation, and would thus require alternative text.</p>
<pre><!-- Using the title="" attribute -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<p><strong><img src="images/parsing-model-overview.png" alt=""
title="Flowchart representation of the parsing model."></strong></p></pre>
<pre><!-- Using <figure> and <legend> -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<figure>
<strong><img src="images/parsing-model-overview.png" alt="The Network leads
- to the Tokeniser, which leads to the Tree Construction. The Tree
+ to the Tokenizer, which leads to the Tree Construction. The Tree
Construction leads to two items. The first is Script Execution, which
- leads via document.write() back to the Tokeniser. The second item
+ leads via document.write() back to the Tokenizer. The second item
from which Tree Construction leads is the DOM. The DOM is related to
the Script Execution."></strong>
<legend>Flowchart representation of the parsing model.</legend>
</figure></pre>
<pre class=bad><!-- This is WRONG. Do not do this. Instead, do what the above examples do. -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<p><img src="images/parsing-model-overview.png"
alt="Flowchart representation of the parsing model."></p>
<!-- Never put the image's caption in the alt="" attribute! --></pre>
@@ -17835,7 +17835,7 @@
<p>Markup generators (such as WYSIWYG authoring tools) should,
wherever possible, obtain alternative text from their
- users. However, it is recognised that in many cases, this will not
+ users. However, it is recognized that in many cases, this will not
be possible.</p>
<p>For images that are the sole contents of links, markup generators
@@ -17847,7 +17847,7 @@
the assumption that the image is a purely decorative image that
doesn't add any information but is still specific to the surrounding
content, or omit the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute
- altogther, under the assumption that the image is a key part of the
+ altogether, under the assumption that the image is a key part of the
content.</p>
<p>Markup generators should generally avoid using the image's own
@@ -17986,7 +17986,7 @@
and <code title=attr-iframe-sandbox-allow-scripts><a href=#attr-iframe-sandbox-allow-scripts>allow-scripts</a></code>. When
the attribute is set, the content is treated as being from a unique
<a href=#origin-0>origin</a>, forms and scripts are disabled, links are
- prevented from targetting other <a href=#browsing-context title="browsing
+ prevented from targeting other <a href=#browsing-context title="browsing
context">browsing contexts</a>, and plugins are disabled. The
<code title=attr-iframe-sandbox-allow-same-origin><a href=#attr-iframe-sandbox-allow-same-origin>allow-same-origin</a></code>
token allows the content to be treated as being from the same origin
@@ -19726,7 +19726,7 @@
<p><dfn id=a-type-that-the-user-agent-knows-it-cannot-render>A type that the user agent knows it cannot render</dfn> is
one that describes a resource that the user agent definitely does
- not support, for example because it doesn't recognise the container
+ not support, for example because it doesn't recognize the container
type, or it doesn't support the listed codecs.</p>
<dl class=domintro><dt><var title="">media</var> . <code title=dom-navigator-canPlayType><a href=#dom-navigator-canplaytype>canPlayType</a></code>(<var title="">type</var>)</dt>
@@ -21798,7 +21798,7 @@
in the SVG resource, the SVG file would appear to be in a lone
top-level browsing context with no parent.</p>
- <hr><p>If a hostile page embeds victom content, the threat is that the
+ <hr><p>If a hostile page embeds victim content, the threat is that the
embedding page could obtain information from the content that it
would not otherwise have access to. The API does expose some
information: the existence of the media, its type, its duration, its
@@ -24976,7 +24976,7 @@
<p><img alt="A line with four shapes in it, equally spaced: a red hollow box, a green circle, a blue triangle, and a yellow four-pointed star." src=images/sample-usemap.png></p>
- <p>If we wanted just the coloured areas to be clickable, we could
+ <p>If we wanted just the colored areas to be clickable, we could
do it as follows:</p>
<pre><p>
@@ -27565,7 +27565,7 @@
<p>The
<span>indices of the supported indexed properties</span> at any
- instant are the indicies supported by the object returned by the
+ instant are the indices supported by the object returned by the
<code title=dom-form-elements><a href=#dom-form-elements>elements</a></code> attribute at that
instant.</p>
@@ -27671,7 +27671,7 @@
<dt>Contexts in which this element may be used:</dt>
<dd>Where <a href=#flow-content-0>flow content</a> is expected.</dd>
<dt>Content model:</dt>
- <dd>One <code><a href=#the-legend-element>legend</a></code> element follwed by <a href=#flow-content-0>flow content</a>.</dd>
+ <dd>One <code><a href=#the-legend-element>legend</a></code> element followed by <a href=#flow-content-0>flow content</a>.</dd>
<dt>Content attributes:</dt>
<dd><a href=#global-attributes>Global attributes</a></dd>
<dd><code title=attr-fieldset-disabled><a href=#attr-fieldset-disabled>disabled</a></code></dd>
@@ -28088,7 +28088,7 @@
attributes, and the <code title=dom-input-stepUp><a href=#dom-input-stepup>stepUp()</a></code>
and <code title=dom-input-stepDown><a href=#dom-input-stepdown>stepDown()</a></code> methods, are
specific to certain states. The following table <span class=impl>is non-normative and</span> summarises which content
- attributes, DOM attrbutes, and methods apply to each state:</p>
+ attributes, DOM attributes, and methods apply to each state:</p>
<table class=applies><thead><tr><td>
<th> <span title=""><a href=#hidden-state title=attr-input-type-hidden>Hidden</a></span>
@@ -29006,7 +29006,7 @@
<p>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute changes state, and
when the element is first created, the element's rendering and
- behaviour must change to the new state's accordingly and the
+ behavior must change to the new state's accordingly and the
<dfn id=value-sanitization-algorithm>value sanitization algorithm</dfn>, if one is defined for the
<code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute's new state,
must be invoked.</p>
@@ -29633,7 +29633,7 @@
for setting the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to a string representing a
specific <a href=#concept-datetime title=concept-datetime>global date and
time</a>. <span class=impl>User agents may display the date and
- time in whatever timezone is appropriate for the user.</span></p>
+ time in whatever time zone is appropriate for the user.</span></p>
<div class=impl>
@@ -29645,8 +29645,8 @@
set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that
is not a <a href=#valid-global-date-and-time-string>valid global date and time string</a> expressed in
UTC, though user agents may allow the user to set and view the time
- in another timezone and silently translate the time to and from the
- UTC timezone in the <a href=#concept-fe-value title=concept-fe-value>value</a>. If
+ in another time zone and silently translate the time to and from the
+ UTC time zone in the <a href=#concept-fe-value title=concept-fe-value>value</a>. If
the user agent provides a user interface for selecting a <a href=#concept-datetime title=concept-datetime>global date and time</a>, then the <a href=#concept-fe-value title=concept-fe-value>value</a> must be set to a <a href=#valid-global-date-and-time-string>valid
global date and time string</a> expressed in UTC representing the
user's selection. User agents should allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
@@ -29664,7 +29664,7 @@
follows:</strong> If the <a href=#concept-fe-value title=concept-fe-value>value</a>
of the element is a <a href=#valid-global-date-and-time-string>valid global date and time string</a>,
then adjust the time so that the <a href=#concept-fe-value title=concept-fe-value>value</a> represents the same point in
- time but expressed in the UTC timezone, otherwise, set it to the
+ time but expressed in the UTC time zone, otherwise, set it to the
empty string instead.</p>
</div>
@@ -29863,7 +29863,7 @@
follows:</strong> Return a <a href=#valid-date-string>valid date string</a> that
represents the <a href=#concept-date title=concept-date>date</a> current at the
time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -30010,7 +30010,7 @@
follows:</strong> Return a <a href=#valid-month-string>valid month string</a> that
represents the <a href=#concept-month title=concept-month>month</a> current at
the time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -30157,7 +30157,7 @@
follows:</strong> Return a <a href=#valid-week-string>valid week string</a> that
represents the <a href=#concept-week title=concept-week>week</a> current at the
time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -31404,7 +31404,7 @@
<code><a href=#the-input-element>input</a></code> element. User agents must not run executable code
embedded in the image resource. User agents must only display the
first page of a multipage resource. User agents must not allow the
- resource to act in an interactive fashion, but should honour any
+ resource to act in an interactive fashion, but should honor any
animation in the resource.</p>
<p>The <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
@@ -32888,7 +32888,7 @@
<p>The <code title=dom-select-options><a href=#dom-select-options>options</a></code> collection is
also mirrored on the <code><a href=#htmlselectelement>HTMLSelectElement</a></code> object. The
<span>indices of the supported indexed properties</span> at any
- instant are the indicies supported by the object returned by the
+ instant are the indices supported by the object returned by the
<code title=dom-select-options><a href=#dom-select-options>options</a></code> attribute at that
instant. The <span>names of the supported named properties</span> at
any instant are the names supported by the object returned by the
@@ -33253,7 +33253,7 @@
object must have a <code title=attr-option-selected><a href=#attr-option-selected>selected</a></code> attribute set with no
value. If the <var title="">selected</var> argument is present and
true, the new object must have its <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> set to true;
- otherwise the fouth argument is absent or false, and the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> must be set
+ otherwise the fourth argument is absent or false, and the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> must be set
to false, even if the <var title="">defaultSelected</var> argument
is present and true.</p>
@@ -33434,9 +33434,9 @@
defined to be the element's <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a> with the
following transformation applied:</p>
- <ol><li><p>Replace every occurance of a U+000D CARRIAGE RETURN (CR)
+ <ol><li><p>Replace every occurrence of a U+000D CARRIAGE RETURN (CR)
character not followed by a U+000A LINE FEED (LF) character, and
- every occurance of a U+000A LINE FEED (LF) character not proceeded
+ every occurrence of a U+000A LINE FEED (LF) character not proceeded
by a U+000D CARRIAGE RETURN (CR) character, by a two-character
string consisting of a U+000D CARRIAGE RETURN - U+000A LINE FEED
(CRLF) character pair.</li>
@@ -34486,7 +34486,7 @@
constraint validation</a>, then move on to the next
element.</li>
- <li><p>Otherwise, if <var title="">field</var> <a href=#concept-fv-valid title=concept-fv-valid>satisfies its constaints</a>, then
+ <li><p>Otherwise, if <var title="">field</var> <a href=#concept-fv-valid title=concept-fv-valid>satisfies its constraints</a>, then
move on to the next element.</li>
<li><p>Otherwise, add <var title="">field</var> to <var title="">invalid controls</var>.</li>
@@ -34559,7 +34559,7 @@
<dd>
- <p>Sets a custom error, so that the elemnt would fail to
+ <p>Sets a custom error, so that the element would fail to
validate. The given message is the message to be shown to the user
when reporting the problem to the user.</p>
@@ -34723,7 +34723,7 @@
</dl><p>When the <dfn id=dom-cva-checkvalidatity title=dom-cva-checkValidatity><code>checkValidity()</code></dfn>
method is invoked, if the element is a <a href=#candidate-for-constraint-validation>candidate for
- constraint validation</a> and does not <a href=#concept-fv-valid title=concept-fv-valid>satisfy its constaints</a>, the user
+ constraint validation</a> and does not <a href=#concept-fv-valid title=concept-fv-valid>satisfy its constraints</a>, the user
agent must <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-invalid>invalid</code> at the element and return
false. Otherwise, it must only return true without doing anything
else.</p>
@@ -34731,7 +34731,7 @@
<p>The <dfn id=dom-cva-validationmessage title=dom-cva-validationMessage><code>validationMessage</code></dfn>
attribute must return the empty string if the element is not a
<a href=#candidate-for-constraint-validation>candidate for constraint validation</a> or if it is one but
- it <a href=#concept-fv-valid title=concept-fv-valid>satisfies its constaints</a>;
+ it <a href=#concept-fv-valid title=concept-fv-valid>satisfies its constraints</a>;
otherwise, it must return a suitably localised message that the user
agent would show the user if this were the only form with a validity
constraint problem. If the element is <a href=#suffering-from-a-custom-error>suffering from a custom
@@ -34914,7 +34914,7 @@
<li><p>The <var title="">field</var> element is <var title="">submitter</var>, and before this algorithm was invoked
the user <a href=#concept-input-type-image-coordinate title=concept-input-type-image-coordinate>indicated a
- coordinate</a>. Let <var title="">x</var> be the <var title="">x</var>-component of the coordindate selected by the
+ coordinate</a>. Let <var title="">x</var> be the <var title="">x</var>-component of the coordinate selected by the
user, and let <var title="">y</var> be the <var title="">y</var>-component of the coordinate selected by the
user.</li>
@@ -35171,7 +35171,7 @@
interpreted as US-ASCII, do not match the <code title="">unreserved</code> production in the URI Generic Syntax,
and then, treating the result as a US-ASCII string, further
%-escape all the U+0025 PERCENT SIGN characters in the resulting
- string and replace the first occurance of "<code title="">%%%%</code>" in <var title="">action</var> with the
+ string and replace the first occurrence of "<code title="">%%%%</code>" in <var title="">action</var> with the
resulting double-escaped string. <a href=#refsRFC3986>[RFC3986]</a></p>
<p>Otherwise, if <var title="">action</var> contains the string
@@ -35179,7 +35179,7 @@
in a row, but not four), then %-escape all characters in <var title="">data</var> that, if interpreted as US-ASCII, do not
match the <code title="">unreserved</code> production in the URI
Generic Syntax, and then, treating the result as a US-ASCII
- string, replace the first occurance of "<code title="">%%</code>" in <var title="">action</var> with the
+ string, replace the first occurrence of "<code title="">%%</code>" in <var title="">action</var> with the
resulting escaped string. <a href=#refsRFC3986>[RFC3986]</a></p>
<p>Let <var title="">target browsing context</var> be <a href=#the-form-submission-target-browsing-context>the
@@ -35243,7 +35243,8 @@
<var title="">form data set</var> using the <a href=#application/x-www-form-urlencoded-encoding-algorithm><code title="">application/x-www-form-urlencoded</code> encoding
algorithm</a>, interpreted as a US-ASCII string.</p>
- <p>Replace occurances of U+002B PLUS SIGN characters (+) in <var title="">headers</var> with the string "<code title="">%20</code>".</p>
+ <p>Replace occurrences of U+002B PLUS SIGN characters (+) in
+ <var title="">headers</var> with the string "<code title="">%20</code>".</p>
<p>Let <var title="">destination</var> consist of all the
characters from the first character in <var title="">action</var> to the character immediately before the
@@ -35602,7 +35603,7 @@
<p>The user agent should allow the user to request that the details
be shown or hidden. To honor a request for the details to be shown,
the user agent must set the <code title=attr-details-open><a href=#attr-details-open>open</a></code> attribute on the element to
- the value <code title="">open</code>. To honour a request for the
+ the value <code title="">open</code>. To honor a request for the
details to be hidden, the user agent must remove the <code title=attr-details-open><a href=#attr-details-open>open</a></code> attribute from the
element.</p>
@@ -38195,7 +38196,7 @@
DOM attribute must return true if the <code title=attr-bb-type><a href=#attr-bb-type>type</a></code> attribute is in a state other than
the <i title=attr-bb-type-null-state><a href=#attr-bb-type-null-state>null</a></i> state and the user
agent supports that state's <i>action</i> (i.e. when the attribute's
- value is one that the user agent recognises and supports), and false
+ value is one that the user agent recognizes and supports), and false
otherwise.</p>
<p>The <dfn id=dom-bb-disabled title=dom-bb-disabled><code>disabled</code></dfn> DOM
@@ -41431,7 +41432,7 @@
<dt>Parsing</dt>
- <dd><p>The <a href=#html-parser>HTML parser</a> tokenising a single byte, and
+ <dd><p>The <a href=#html-parser>HTML parser</a> tokenizing a single byte, and
then processing any resulting tokens, is a task.</dd>
@@ -42810,7 +42811,7 @@
<p>User agents must raise a <code><a href=#syntax_err>SYNTAX_ERR</a></code> exception if the
<var title="">url</var> argument passed to one of these methods does
not contain the exact literal string "<code>%s</code>", or if <a href=#resolve-a-url title="resolve a url">resolving</a> the <var title="">url</var>
- argument with the first occurance of the string "<code title="">%s</code>" removed, relative to the <a href=#first-script>first
+ argument with the first occurrence of the string "<code title="">%s</code>" removed, relative to the <a href=#first-script>first
script</a>'s <a href="#script's-base-url" title="script's base URL">base URL</a>, is
not successful.</p>
@@ -42901,8 +42902,8 @@
<p><strong>Leaking secure URLs.</strong> User agents should not send
HTTPS URLs to third-party sites registered as content handlers, in
- the same way that user agents do not send <code title=http-referer>Referer</code> headers from secure sites to
- third-party sites.</p>
+ the same way that user agents do not send <code title=http-referer>Referer</code> (sic) HTTP headers from secure
+ sites to third-party sites.</p>
<p><strong>Leaking credentials.</strong> User agents must never send
username or password information in the URLs that are escaped and
@@ -43587,7 +43588,7 @@
<ol><li>
- <p>Pick the approprate substeps:</p>
+ <p>Pick the appropriate substeps:</p>
<dl class=switch><dt>If these steps were invoked with an <a href=#absolute-url>absolute
URL</a> purported to identify a <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a></dt>
@@ -44002,7 +44003,7 @@
either completely downloaded or failed.</p>
<p>If the download failed (e.g. the connection times out, or the
- user cancels the download), then run these sebsteps:</p>
+ user cancels the download), then run these substeps:</p>
<ol><li><p>Unassociate the <code>Document</code> for this entry from
<var title="">new cache</var>.</li>
@@ -45381,13 +45382,13 @@
actually wants to use this ability, so requiring it here seems
like unnecessary work. -->
- <p>HTTP 401 responses that do not include a challenge recognised
+ <p>HTTP 401 responses that do not include a challenge recognized
by the user agent must be processed as if they had no challenge,
e.g. rendering the entity body as if the response had been 200
OK.</p>
<p>User agents may show the entity body of an HTTP 401 response
- even when the response do include a recognised challenge, with the
+ even when the response do include a recognized challenge, with the
option to login being included in a non-modal fashion, to enable
the information provided by the server to be used by the user
before authenticating. Similarly, user agents should allow the
@@ -45526,7 +45527,7 @@
<ol><li><p>Wait for a user-agent defined amount of time, as desired
by the user agent implementor. (This is intended to allow the
- user agent to optimise the user experience in the face of
+ user agent to optimize the user experience in the face of
performance concerns.)</li>
<li><p>If the <code>Document</code> object has no parser, or its
@@ -45557,11 +45558,9 @@
document as the <a href=#the-input-stream>input stream</a> for that parser.</p>
<p class=note>The <a href=#the-input-stream>input stream</a> converts bytes into
- characters for use in the <span>tokeniser</span><!-- XXX xref
- -->. This process relies, in part, on character encoding information
- found in the real <a href=#content-type-0 title=Content-Type>Content-Type
- metadata</a> of the resource; the "sniffed type" is not used for
- this purpose.</p>
+ characters for use in the <a href=#tokenization title=tokenization>tokenizer</a>. This process relies, in part,
+ on character encoding information found in the real <a href=#content-type-0 title=Content-Type>Content-Type metadata</a> of the resource;
+ the "sniffed type" is not used for this purpose.</p>
<!-- next two paragraphs are nearly identical to the navigate-text
section, keep them in sync -->
@@ -45613,7 +45612,7 @@
<p class=note>Because the processing of the <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute happens
only once the root element is parsed, any URLs referenced by
- processing instructions before the root element (such as <code title=""><?xml-styleesheet?></code> and <code title=""><?xbl?></code> PIs) will be fetched from the network and
+ processing instructions before the root element (such as <code title=""><?xml-stylesheet?></code> and <code title=""><?xbl?></code> PIs) will be fetched from the network and
cannot be cached.</p> <!-- XXX any ideas for avoiding this, that
aren't a PI themselves? We can't delay the processing, since the
whole point of the <?xbl?> PI is to have the XBL sheet loaded before
@@ -45644,11 +45643,11 @@
context</a>, the user agent should create a <code>Document</code>
object, mark it as being an <a href=#html-documents title="HTML documents">HTML
document</a>, create an <a href=#html-parser>HTML parser</a>, associate it
- with the document, act as if the tokeniser had emitted a start tag
+ with the document, act as if the tokenizer had emitted a start tag
token with the tag name "pre", set the <a href=#tokenization>tokenization</a>
stage's <a href=#content-model-flag>content model flag</a> to <i>PLAINTEXT</i>, and
begin to pass the stream of characters in the plain text document to
- that tokeniser.</p>
+ that tokenizer.</p>
<p>The rules for how to convert the bytes of the plain text document
into actual characters are defined in RFC 2046, RFC 2646, and
@@ -46197,10 +46196,11 @@
<p>User agents should allow the user to adjust this behavior, for
example in conjunction with a setting that disables the sending of
- HTTP <code title=http-referer>Referer</code> headers. Based on the
- user's preferences, UAs may either <a href=#ignore>ignore</a> the <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute altogether, or
- selectively ignore URLs in the list (e.g. ignoring any third-party
- URLs).</p>
+ HTTP <code title=http-referer>Referer</code> (sic) headers. Based
+ on the user's preferences, UAs may either <a href=#ignore>ignore</a> the
+ <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute altogether,
+ or selectively ignore URLs in the list (e.g. ignoring any
+ third-party URLs).</p>
<p>For URLs that are HTTP URLs, the requests must be performed by
<a href=#fetch title=fetch>fetching</a> the specified URLs using the
@@ -46217,20 +46217,19 @@
value, the <a href="#the-document's-address" title="the document's address">address</a> of
the document containing the hyperlink, and a <code title=http-ping-to>Ping-To</code> HTTP header with, as its value,
the address of the <a href=#absolute-url>absolute URL</a> of the target of the
- hyperlink. The request must not include a <code title=http-referer>Referer</code> HTTP header. <!-- because
+ hyperlink. The request must not include a <code title=http-referer>Referer</code> (sic) HTTP header. <!-- because
otherwise it would look like a trustable same-origin POST --></dd>
<dt>Otherwise, if the origins are different, but the document
containing the hyperlink being audited was not retrieved over an
encrypted connection</dt>
- <dd>The request must include a <code title="">Referer</code> HTTP
- header [sic] with, as its value, the <a href="#the-document's-address" title="the document's
- address">address</a> of the document containing the hyperlink, a
- <code title=http-ping-from>Ping-From</code> HTTP header with the
- same value, and a <code title=http-ping-to>Ping-To</code> HTTP
- header with, as its value, the address of the target of the
- hyperlink.</dd>
+ <dd>The request must include a <code title="">Referer</code> (sic)
+ HTTP header [sic] with, as its value, the <a href="#the-document's-address" title="the
+ document's address">address</a> of the document containing the
+ hyperlink, a <code title=http-ping-from>Ping-From</code> HTTP
+ header with the same value, and a <code title=http-ping-to>Ping-To</code> HTTP header with, as its value,
+ the address of the target of the hyperlink.</dd>
<dt>Otherwise, the origins are different and the document
containing the hyperlink being audited was retrieved over an
@@ -46238,8 +46237,8 @@
<dd>The request must include a <code title=http-ping-to>Ping-To</code> HTTP header with, as its value,
the address of the target of the hyperlink. The request must
- neither include a <code title="">Referer</code> HTTP header nor
- include a <code title=http-ping-from>Ping-From</code> HTTP
+ neither include a <code title="">Referer</code> (sic) HTTP header
+ nor include a <code title=http-ping-from>Ping-From</code> HTTP
header.</dd>
</dl><p>In addition, an <code title=http-origin>XXX-Origin</code> header
@@ -46412,7 +46411,7 @@
<tr><td><code title=rel-noreferrer><a href=#link-type-noreferrer>noreferrer</a></code></td>
<td><em>not allowed</em></td>
<td><a href=#hyperlink>Hyperlink</a></td>
- <td>Requires that the user agent not send an HTTP <code title="">Referer</code> header if the user follows the hyperlink.</td>
+ <td>Requires that the user agent not send an HTTP <code title="">Referer</code> (sic) header if the user follows the hyperlink.</td>
<tr><td><code title=rel-pingback><a href=#link-type-pingback>pingback</a></code></td>
<td><a href=#external-resource-link title="external resource link">External Resource</a></td>
<td><em>not allowed</em></td>
@@ -46916,8 +46915,9 @@
<p>If a user agent follows a link defined by an <code><a href=#the-a-element>a</a></code> or
<code><a href=#the-area-element>area</a></code> element that has the <code title=rel-noreferrer><a href=#link-type-noreferrer>noreferrer</a></code> keyword, the user agent
- must not include a <code title="">Referer</code> HTTP header (<a href=#concept-http-equivalent-headers title=concept-http-equivalent-headers>or equivalent</a> for
- other protocols) in the request.</p>
+ must not include a <code title="">Referer</code> (sic) HTTP header
+ (<a href=#concept-http-equivalent-headers title=concept-http-equivalent-headers>or equivalent</a>
+ for other protocols) in the request.</p>
<p>This keyword also <a href=#noopener>causes the <code title=dom-opener>opener</code> attribute to remain null</a> if the
hyperlink creates a new <a href=#browsing-context>browsing context</a>.</p>
@@ -47529,7 +47529,7 @@
<p>User agents may track focus for each <a href=#browsing-context>browsing
context</a> or <code>Document</code> individually, or may support
- only one focused elment per <a href=#top-level-browsing-context>top-level browsing context</a>
+ only one focused element per <a href=#top-level-browsing-context>top-level browsing context</a>
— user agents should follow platform conventions in this
regard.</p>
@@ -48247,7 +48247,7 @@
</div>
<div class=example>
- <p>In the following document fragment, the emphasised parts
+ <p>In the following document fragment, the emphasized parts
indicate the selection.</p>
<pre><p>The cute girl likes <em>the </em><cite><em>Oxford English</em> Dictionary</cite>.</p></pre>
<p>If a script invoked <code title="">window.getSelection().toString()</code>, the return value
@@ -50334,7 +50334,7 @@
<dd>
- <p>Returns teh value of the command, as described in the list below.</p>
+ <p>Returns the value of the command, as described in the list below.</p>
</dd>
@@ -52410,10 +52410,10 @@
<p><img alt="" src=images/parsing-model-overview.png></p>
- <p id=nestedParsing>There is only one set of state for the
- tokeniser stage and the tree construction stage, but the tree
+ <p id=nestedParsing>There is only one set of states for the
+ tokenizer stage and the tree construction stage, but the tree
construction stage is reentrant, meaning that while the tree
- construction stage is handling one token, the tokeniser might be
+ construction stage is handling one token, the tokenizer might be
resumed, causing further tokens to be emitted and processed before
the first token's processing is complete.</p>
@@ -52438,7 +52438,7 @@
<h4 id=the-input-stream><span class=secno>8.2.2 </span>The <dfn>input stream</dfn></h4>
- <p>The stream of Unicode characters that consists the input to the
+ <p>The stream of Unicode characters that comprises the input to the
tokenization stage will be initially seen by the user agent as a
stream of bytes (typically coming over the network or from the local
file system). The bytes encode the actual characters according to a
@@ -52828,7 +52828,7 @@
<h5 id=preprocessing-the-input-stream><span class=secno>8.2.2.2 </span>Preprocessing the input stream</h5>
<p>Given an encoding, the bytes in the input stream must be
- converted to Unicode characters for the tokeniser, as described by
+ converted to Unicode characters for the tokenizer, as described by
the rules for that encoding, except that the leading U+FEFF BYTE
ORDER MARK character, if any, must not be stripped by the encoding
layer (it is stripped by the rule below).</p> <!-- this is to
@@ -53365,7 +53365,7 @@
<h4 id=tokenization><span class=secno>8.2.4 </span><dfn>Tokenization</dfn></h4>
<p>Implementations must act as if they used the following state
- machine to tokenise HTML. The state machine must start in the
+ machine to tokenize HTML. The state machine must start in the
<a href=#data-state>data state</a>. Most states consume a single character,
which may have various side-effects, and either switches the state
machine to a new state to <em>reconsume</em> the same character, or
@@ -53378,7 +53378,7 @@
model flag</dfn> that is set after certain tokens are emitted. The
flag has several states: <i title="">PCDATA</i>, <i title="">RCDATA</i>, <i title="">CDATA</i>, and <i title="">PLAINTEXT</i>. Initially it must be in the PCDATA
state. In the RCDATA and CDATA states, a further <dfn id=escape-flag>escape
- flag</dfn> is used to control the behavior of the tokeniser. It is
+ flag</dfn> is used to control the behavior of the tokenizer. It is
either true or false, and initially must be set to the false
state. The <a href=#insertion-mode>insertion mode</a> and the <a href=#stack-of-open-elements>stack of open
elements</a> also affects tokenization.</p>
@@ -53404,7 +53404,7 @@
insert additional characters into the stream. (For example, the
<code><a href=#script>script</a></code> element can result in scripts executing and
using the <a href=#dynamic-markup-insertion>dynamic markup insertion</a> APIs to insert
- characters into the stream being tokenised.)</p>
+ characters into the stream being tokenized.)</p>
<p>When a start tag token is emitted with its <i>self-closing
flag</i> set, if the flag is not <dfn id=acknowledge-self-closing-flag title="acknowledge
@@ -53420,10 +53420,10 @@
<p>When an end tag token is emitted with its <i>self-closing
flag</i> set, that is a <a href=#parse-error>parse error</a>.</p>
- <p>Before each step of the tokeniser, the user agent must first
+ <p>Before each step of the tokenizer, the user agent must first
check the <a href=#parser-pause-flag>parser pause flag</a>. If it is true, then the
- tokeniser must abort the processing of any nested invocations of the
- tokeniser, yielding control back to the caller. If it is false, then
+ tokenizer must abort the processing of any nested invocations of the
+ tokenizer, yielding control back to the caller. If it is false, then
the user agent may then check to see if either one of the scripts in
the <a href=#list-of-scripts-that-will-execute-as-soon-as-possible>list of scripts that will execute as soon as
possible</a> or the first script in the <a href=#list-of-scripts-that-will-execute-asynchronously>list of scripts
@@ -53431,7 +53431,7 @@
loading</a>. If one has, then it must be <a href=#executing-a-script-block title="executing a
script block">executed</a> and removed from its list.</p>
- <p>The tokeniser state machine consists of the states defined in the
+ <p>The tokenizer state machine consists of the states defined in the
following subsections.</p>
<!-- XXX should go through these reordering the entries so that
@@ -53580,7 +53580,7 @@
<p>If the <a href=#content-model-flag>content model flag</a> is set to the RCDATA or
CDATA states but no start tag token has ever been emitted by this
- instance of the tokeniser (<a href=#fragment-case>fragment case</a>), or, if the
+ instance of the tokenizer (<a href=#fragment-case>fragment case</a>), or, if the
<a href=#content-model-flag>content model flag</a> is set to the RCDATA or CDATA states
and the next few characters do not match the tag name of the last
start tag token emitted (compared in an <a href=#ascii-case-insensitive>ASCII
@@ -54701,7 +54701,7 @@
has to render the <code>Document</code> so that it is available to
the user, or when it has to begin accepting user input.</p>
- <p>As each token is emitted from the tokeniser, the user agent must
+ <p>As each token is emitted from the tokenizer, the user agent must
process the token according to the rules given in the section
corresponding to the current <a href=#insertion-mode>insertion mode</a>.</p>
@@ -54900,10 +54900,10 @@
<ol><li><p><a href=#insert-an-html-element>Insert an HTML element</a> for the token.</li>
<li><p>If the algorithm that was invoked is the <a href=#generic-cdata-element-parsing-algorithm>generic CDATA
- element parsing algorithm</a>, switch the tokeniser's
+ element parsing algorithm</a>, switch the tokenizer's
<a href=#content-model-flag>content model flag</a> to the CDATA state; otherwise the
algorithm invoked was the <a href=#generic-rcdata-element-parsing-algorithm>generic RCDATA element parsing
- algorithm</a>, switch the tokeniser's <a href=#content-model-flag>content model
+ algorithm</a>, switch the tokenizer's <a href=#content-model-flag>content model
flag</a> to the RCDATA state.</li>
<li><p>Let the <a href=#original-insertion-mode>original insertion mode</a> be the current
@@ -55391,7 +55391,7 @@
and push it onto the <a href=#stack-of-open-elements>stack of open
elements</a>.</li>
- <li><p>Switch the tokeniser's <a href=#content-model-flag>content model flag</a> to
+ <li><p>Switch the tokenizer's <a href=#content-model-flag>content model flag</a> to
the CDATA state.</li>
<li><p>Let the <a href=#original-insertion-mode>original insertion mode</a> be the current
@@ -56512,7 +56512,7 @@
one. (Newlines at the start of <code><a href=#the-textarea-element>textarea</a></code> elements are
ignored as an authoring convenience.)</li>
- <li><p>Switch the tokeniser's <a href=#content-model-flag>content model flag</a> to
+ <li><p>Switch the tokenizer's <a href=#content-model-flag>content model flag</a> to
the RCDATA state.</li>
<li><p>Let the <a href=#original-insertion-mode>original insertion mode</a> be the
@@ -56811,8 +56811,8 @@
<p><a href=#running-a-script title="running a script">Run</a> the <var title="">script</var>. This might cause some script to execute,
which might cause <a href=#dom-document-write title=dom-document-write>new characters
- to be inserted into the tokeniser</a>, and might cause the
- tokeniser to output more tokens, resulting in a <a href=#nestedParsing>reentrant invocation of the parser</a>.</p>
+ to be inserted into the tokenizer</a>, and might cause the
+ tokenizer to output more tokens, resulting in a <a href=#nestedParsing>reentrant invocation of the parser</a>.</p>
<p>Decrement the parser's <a href=#script-nesting-level>script nesting level</a> by
one. If the parser's <a href=#script-nesting-level>script nesting level</a> is zero,
@@ -56829,7 +56829,7 @@
call to <code title=dom-document-write><a href=#dom-document-write>document.write()</a></code>:</dt>
<dd><p>Set the <a href=#parser-pause-flag>parser pause flag</a> to true, and abort
- the processing of any nested invocations of the tokeniser,
+ the processing of any nested invocations of the tokenizer,
yielding control back to the caller. (Tokenization will resume
when the caller returns to the "outer" tree construction
stage.)</dd>
@@ -57693,7 +57693,7 @@
rules. <a href=#refsSVG>[SVG]</a></p>
<p class=note>Even if this causes <a href=#dom-document-write title=dom-document-write>new characters to be inserted into the
- tokeniser</a>, the parser will not be executed reentrantly,
+ tokenizer</a>, the parser will not be executed reentrantly,
since the <a href=#parser-pause-flag>parser pause flag</a> is true.</p>
<p>Decrement the parser's <a href=#script-nesting-level>script nesting level</a> by
@@ -63288,12 +63288,12 @@
<p>To ease the transition from HTML4 Transitional documents to the
language defined in <em>this</em> specification, conformance
- checkers are encouraged to categorise errors that represent usage of
+ checkers are encouraged to categorize errors that represent usage of
old obsolete features that generally have no effect (as defined
below) into a separate part of their report, to allow authors to
distinguish between likely mistakes and mere vestigial markup.</p>
- <p>The following errors may be categorised as described above:</p>
+ <p>The following errors may be categorized as described above:</p>
<ul><!-- downplayed list --><li>
@@ -63726,6 +63726,7 @@
Jens Bannmann,
Jens Fendler,
Jens Lindström,
+ Jens Meiert,
Jeroen van der Meer,
Jim Jewett,
Jim Ley,
@@ -63862,6 +63863,7 @@
Sam Weinig,
Sander van Lambalgen,
Scott Hess,
+ Sean Fraser,
Sean Hogen,
Sean Knapp,
Sebastian Schnitzenbaumer,
Modified: source
===================================================================
--- source 2009-04-18 01:16:51 UTC (rev 2962)
+++ source 2009-04-18 06:33:45 UTC (rev 2963)
@@ -1817,7 +1817,7 @@
the order given, aborting at the first step that returns a
value. This algorithm will either return a number greater than or
equal to 1.0, or an error; if a number is returned, then it is
- further categorised as either a percentage or a length.</p>
+ further categorized as either a percentage or a length.</p>
<ol>
@@ -2365,7 +2365,7 @@
<h5>Months</h5>
<p>A <dfn title="concept-month">month</dfn> consists of a specific
- proleptic Gregorian date with no timezone information and no date
+ proleptic Gregorian date with no time-zone information and no date
information beyond a year and a month. <a
href="#refsGREGORIAN">[GREGORIAN]</a></p>
@@ -2461,8 +2461,8 @@
<h5>Dates</h5>
<p>A <dfn title="concept-date">date</dfn> consists of a specific
- proleptic Gregorian date with no timezone information, consisting of
- a year, a month, and a day. <a
+ proleptic Gregorian date with no time-zone information, consisting
+ of a year, a month, and a day. <a
href="#refsGREGORIAN">[GREGORIAN]</a></p>
<p>A string is a <dfn>valid date string</dfn> representing a year
@@ -2561,7 +2561,7 @@
<h5>Times</h5>
<p>A <dfn title="concept-time">time</dfn> consists of a specific
- time with no timezone information, consisting of an hour, a minute,
+ time with no time-zone information, consisting of an hour, a minute,
a second, and a fraction of a second.</p>
<p>A string is a <dfn>valid time string</dfn> representing an hour
@@ -2820,7 +2820,7 @@
-->
<p>A string is a <dfn>valid global date and time string</dfn>
- representing a date, time, and a timezone offset if it consists of
+ representing a date, time, and a time-zone offset if it consists of
the following components in the given order:</p>
<ol>
@@ -2844,18 +2844,18 @@
<li>Either a U+002B PLUS SIGN character (+) or a U+002D
HYPHEN-MINUS (-) character, representing the sign of the
- timezone offset</li>
+ time-zone offset</li>
<li>Two <span title="concept-datetime-digit">digits</span>,
representing the hours component <var title="">hour</var> of
- the timezone offset, in the range 0 ≤ <var
+ the time-zone offset, in the range 0 ≤ <var
title="">hour</var> ≤ 23</li>
<li>A U+003A COLON character (:)</li>
<li>Two <span title="concept-datetime-digit">digits</span>,
representing the minutes component <var title="">minute</var>
- of the timezone offset, in the range 0 ≤ <var
+ of the time-zone offset, in the range 0 ≤ <var
title="">minute</var> ≤ 59</li>
</ol>
@@ -2918,7 +2918,7 @@
used. However, it seems unlikely that it would be given in the
Gregorian calendar, so I assume sites use the Julian one. -->
- <li>The time and timezone components are not optional.</li>
+ <li>The time and time-zone components are not optional.</li>
<li>Dates before the year zero can't be represented as a datetime
in this version of HTML.</li>
@@ -2933,7 +2933,7 @@
<p>The rules to <dfn>parse a global date and time string</dfn> are
as follows. This will either return a time in UTC, with associated
- timezone information for round tripping or display purposes, or
+ time-zone information for round tripping or display purposes, or
nothing. If at any point the algorithm says that it "fails", this
means that it is aborted at that point and returns nothing.</p>
@@ -2963,7 +2963,7 @@
<li><p>If <var title="">position</var> is beyond the end of <var
title="">input</var>, then fail.</p></li>
- <li><p><span>Parse a timezone component</span> to obtain <var
+ <li><p><span>Parse a time-zone component</span> to obtain <var
title="">timezone<sub title="">hours</sub></var> and <var
title="">timezone<sub title="">minutes</sub></var>. If this returns
nothing, then fail.</p>
@@ -2978,7 +2978,7 @@
subtracting <var title="">timezone<sub title="">hours</sub></var>
hours and <var title="">timezone<sub title="">minutes</sub></var>
minutes. That moment in time is a moment in the UTC
- timezone.</p></li>
+ time zone.</p></li>
<li><p>Let <var title="">timezone</var> be <var
title="">timezone<sub title="">hours</sub></var> hours and <var
@@ -2990,9 +2990,9 @@
</ol>
- <p>The rules to <dfn>parse a timezone component</dfn>, given an <var
+ <p>The rules to <dfn>parse a time-zone component</dfn>, given an <var
title="">input</var> string and a <var title="">position</var>, are
- as follows. This will either return timezone hours and timezone
+ as follows. This will either return time-zone hours and time-zone
minutes, or nothing. If at any point the algorithm says that it
"fails", this means that it is aborted at that point and returns
nothing.</p>
@@ -3292,7 +3292,7 @@
<li><p>If the <var title="">date present</var> and <var
title="">time present</var> flags are both true, <span>parse a
- timezone component</span> to obtain <var title="">timezone<sub
+ time-zone component</span> to obtain <var title="">timezone<sub
title="">hours</sub></var> and <var title="">timezone<sub
title="">minutes</sub></var>. If this returns nothing, then
fail.</p>
@@ -3325,7 +3325,7 @@
title="">second</var>, subtracting <var title="">timezone<sub
title="">hours</sub></var> hours and <var title="">timezone<sub
title="">minutes</sub></var> minutes, that moment in time being a
- moment in the UTC timezone; let <var title="">timezone</var> be
+ moment in the UTC time zone; let <var title="">timezone</var> be
<var title="">timezone<sub title="">hours</sub></var> hours and
<var title="">timezone<sub title="">minutes</sub></var> minutes
from UTC; and return <var title="">time</var> and <var
@@ -4148,7 +4148,7 @@
<p>If parsing <var title="">url</var> resulted in a <span
title="url-host"><host></span> component, then replace the
- matching subtring of <var title="">url</var> with the string that
+ matching substring of <var title="">url</var> with the string that
results from expanding any sequences of percent-encoded octets in
that component that are valid UTF-8 sequences into Unicode
characters as defined by UTF-8.</p>
@@ -7075,7 +7075,7 @@
title="dom-document-lastModified"><code>lastModified</code></dfn>
attribute, on getting, must return the date and time of the
<code>Document</code>'s source file's last modification, in the
- user's local timezone, in the following format:</p>
+ user's local time zone, in the following format:</p>
<ol>
@@ -8168,7 +8168,7 @@
any language information, the default value is unknown (the empty
string).</p>
- <p>If the resulting value is not a recognised language code, then it
+ <p>If the resulting value is not a recognized language code, then it
must be treated as an unknown language (as if the value was the
empty string).</p>
@@ -8231,11 +8231,11 @@
the presentation layer, potentially determined from the value of the
<code title="attr-dir">dir</code> attribute on the
element. Otherwise, if the element's <code
- title="attr-dir">dir</code> attribute has the state <i>ltr</i>,
- the element's directionality is 'ltr' (left-to-right); if the
- attribute has the state <i>rtl</i>, the element's directionality
- is 'rtl' (right-to-left); and oherwise, the element's directionality
- is the same as its parent element, or 'ltr' if there is no parent
+ title="attr-dir">dir</code> attribute has the state <i>ltr</i>, the
+ element's directionality is 'ltr' (left-to-right); if the attribute
+ has the state <i>rtl</i>, the element's directionality is 'rtl'
+ (right-to-left); and otherwise, the element's directionality is the
+ same as its parent element, or 'ltr' if there is no parent
element.</p>
<hr>
@@ -8652,9 +8652,9 @@
embedded content are all types of flow content. Embedded content is
also a type of phrasing content."></object></p>
- <p>In addition, certain elements are categorised as <span
+ <p>In addition, certain elements are categorized as <span
title="form-associated element">form-associated elements</span> and
- further subcategorised so so to define their role in various
+ further subcategorized so so to define their role in various
form-related processing models.</p>
<!-- XXX list all the elements for each kind of element in the
@@ -8677,7 +8677,7 @@
<div class="example">
- <p>Thus, in the XML serialisation, one can use RDF, like this:</p>
+ <p>Thus, in the XML serialization, one can use RDF, like this:</p>
<pre><html xmlns="http://www.w3.org/1999/xhtml"
xmlns:r="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
@@ -8699,7 +8699,7 @@
</body>
</html></pre>
- <p>This isn't possible in the HTML serialisation, however.</p>
+ <p>This isn't possible in the HTML serialization, however.</p>
</div>
@@ -9339,7 +9339,7 @@
that it can be closed by the <code
title="dom-document-open">document.open()</code> and <code
title="dom-document-close">document.close()</code> methods, and
- that the tokeniser will wait for an explicit call to <code
+ that the tokenizer will wait for an explicit call to <code
title="dom-document-close">document.close()</code> before emitting
an end-of-file token). The encoding <span
title="concept-encoding-confidence">confidence</span> is
@@ -9362,7 +9362,7 @@
<p>If <var title="">type</var> is <em>not</em> now an <span>ASCII
case-insensitive</span> match for the string
- "<code>text/html</code>", then act as if the tokeniser had emitted
+ "<code>text/html</code>", then act as if the tokenizer had emitted
a start tag token with the tag name "pre", then set the <span>HTML
parser</span>'s <span>tokenization</span> stage's <span>content
model flag</span> to <i>PLAINTEXT</i>.</p>
@@ -9505,12 +9505,12 @@
<li>
- <p>Otherwise, the tokeniser must process the characters that were
+ <p>Otherwise, the tokenizer must process the characters that were
inserted, one at a time, processing resulting tokens as they are
- emitted, and stopping when the tokeniser reaches the insertion
- point or when the processing of the tokeniser is aborted by the
+ emitted, and stopping when the tokenizer reaches the insertion
+ point or when the processing of the tokenizer is aborted by the
tree construction stage (this can happen if a <code>script</code>
- end tag token is emitted by the tokeniser).
+ end tag token is emitted by the tokenizer).
<p class="note">If the <code
title="dom-document-write">document.write()</code> method was
@@ -10136,7 +10136,7 @@
<p>The next page might be a part of the same site. Note how the
title describes the subject matter unambiguously, while the first
- header assumes the reader knowns what the context is and therefore
+ header assumes the reader knows what the context is and therefore
won't wonder if the dances are Salsa or Waltz:</p>
<pre> <title>Dances used during bee mating rituals</title>
@@ -11123,7 +11123,7 @@
character (') U+0022 QUOTATION MARK character ("), then let <var
title="">quote</var> be that character, and advance <var
title="">position</var> to the next character. Otherwise, let
- <var title="">quote</var> be the empty stirng.</p></li>
+ <var title="">quote</var> be the empty string.</p></li>
<li><p>Let <var title="">url</var> be equal to the substring of
<var title="">input</var> from the character at <var
@@ -11292,7 +11292,7 @@
or character escapes of any kind.</li>
<li id="charset512">The element containing the character encoding
- declaration must be serialised completely within the first 512
+ declaration must be serialized completely within the first 512
bytes of the document.</li>
<li>There can only be one character encoding declaration in the
@@ -11774,7 +11774,7 @@
<li>The <code>script</code> element has a <code
title="attr-script-src">src</code> attribute set where previously
- the elment had no such attribute.</li>
+ the element had no such attribute.</li>
</ul>
@@ -12773,9 +12773,9 @@
<nav>
<h1>Navigation</h1>
<ul>
- <li><a href="articles.html">Index of all articles</a><li>
- <li><a href="today.html">Things sheeple need to wake up for today</a><li>
- <li><a href="successes.html">Sheeple we have managed to wake</a><li>
+ <li><a href="articles.html">Index of all articles</a></li>
+ <li><a href="today.html">Things sheeple need to wake up for today</a></li>
+ <li><a href="successes.html">Sheeple we have managed to wake</a></li>
</ul>
</nav>
<article>
@@ -12985,7 +12985,7 @@
<div class="example">
<p>Here are some examples of valid headers. In each case, the
- emphasised text represents the text that would be used as the
+ emphasized text represents the text that would be used as the
header in an application extracting header data and ignoring
subheadings.</p>
@@ -14615,7 +14615,7 @@
provided to convert the markup into a cloud of differently-sized
words, but for user agents that do not support CSS or are not
visual, the markup contains annotations like "(popular)" or
- "(rare)" to categorise the various tags by frequency, thus enabling
+ "(rare)" to categorize the various tags by frequency, thus enabling
all users to benefit from the information.</p>
<p>The <code>ul</code> element is used (rather than
@@ -14997,9 +14997,9 @@
<p>This next example shows a typical use of the <code>cite</code>
element:</p>
- <pre><p>My favourite book is <cite>The Reality Dysfunction</cite> by
-Peter F. Hamilton. My favourite comic is <cite>Pearls Before
-Swine</cite> by Stephan Pastis. My favourite track is <cite>Jive
+ <pre><p>My favorite book is <cite>The Reality Dysfunction</cite> by
+Peter F. Hamilton. My favorite comic is <cite>Pearls Before
+Swine</cite> by Stephan Pastis. My favorite track is <cite>Jive
Samba</cite> by the Cannonball Adderley Sextet.</p></pre>
</div>
@@ -15205,7 +15205,7 @@
is also sometimes used for attribution.</p>
<p class="note">The <code>small</code> element does not
- "de-emphasize" or lower the importance of text emphasised by the
+ "de-emphasize" or lower the importance of text emphasized by the
<code>em</code> element or marked as important with the
<code>strong</code> element.</p>
@@ -15334,7 +15334,7 @@
<p>This is another example showing the use of <code>mark</code> to
highlight a part of quoted text that was originally not
- emphasised. In this example, common typographic conventions have
+ emphasized. In this example, common typographic conventions have
led the author to explicitly style <code>mark</code> elements in
quotes to render in italics.</p>
@@ -15695,7 +15695,7 @@
<p>I've liked model trains since at least 1983.</p></pre>
<p>Using a styling technology that supports restyling times, the
- first paragraph from the above snipet could be rendered as follows:</p>
+ first paragraph from the above snippet could be rendered as follows:</p>
<blockquote><p>I usually have a snack at 4pm.</p></blockquote>
@@ -15714,7 +15714,7 @@
<p>User agents, to obtain the <dfn
title="concept-time-date">date</dfn>, <dfn
title="concept-time-time">time</dfn>, and <dfn
- title="concept-time-timezone">timezone</dfn> represented by a
+ title="concept-time-timezone">time zone</dfn> represented by a
<code>time</code> element, must follow these steps:</p>
<ol>
@@ -15733,16 +15733,16 @@
<li>If <var title="">result</var> is empty (because the parsing
failed), then the <span title="concept-time-date">date</span> is
unknown, the <span title="concept-time-time">time</span> is unknown,
- and the <span title="concept-time-timezone">timezone</span> is
+ and the <span title="concept-time-timezone">time zone</span> is
unknown.</li>
<li>Otherwise: if <var title="">result</var> contains a date, then
that is the <span title="concept-time-date">date</span>; if <var
title="">result</var> contains a time, then that is the <span
title="concept-time-time">time</span>; and if <var
- title="">result</var> contains a timezone, then the timezone is the
- element's <span title="concept-time-timezone">timezone</span>. (A
- timezone can only be present if both a date and a time are also
+ title="">result</var> contains a time zone, then the time zone is the
+ element's <span title="concept-time-timezone">time zone</span>. (A
+ time zone can only be present if both a date and a time are also
present.)</li>
</ol>
@@ -15757,7 +15757,7 @@
<p>Returns a <code>Date</code> object representing the date
component of the element's value, at midnight in the UTC
- timezone.</p>
+ time zone.</p>
<p>Returns null if there is no date.</p>
@@ -15769,7 +15769,7 @@
<p>Returns a <code>Date</code> object representing the time
component of the element's value, on 1970-01-01 in the UTC
- timezone.</p>
+ time zone.</p>
<p>Returns null if there is no time.</p>
@@ -15780,10 +15780,10 @@
<dd>
<p>Returns a <code>Date</code> object representing the time
- corresponding to 1970-01-01 00:00 UTC in the timezone given by the
+ corresponding to 1970-01-01 00:00 UTC in the time zone given by the
element's value.</p>
- <p>Returns null if there is no timezone.</p>
+ <p>Returns null if there is no time zone.</p>
</dd>
@@ -15802,15 +15802,15 @@
must return null if the <span title="concept-time-time">time</span> is
unknown, and otherwise must return the time corresponding to the
given <span title="concept-time-time">time</span> of 1970-01-01, with
- the timezone UTC.</p>
+ the time zone UTC.</p>
<p>The <dfn title="dom-time-timezone"><code>timezone</code></dfn> DOM
attribute must return null if the <span
- title="concept-time-timezone">timezone</span> is unknown, and otherwise
+ title="concept-time-timezone">time zone</span> is unknown, and otherwise
must return the time corresponding to 1970-01-01 00:00 UTC in the
- given <span title="concept-time-timezone">timezone</span>, with the
- timezone set to UTC (i.e. the time corresponding to 1970-01-01 at
- 00:00 UTC plus the offset corresponding to the timezone).</p>
+ given <span title="concept-time-timezone">time zone</span>, with the
+ time zone set to UTC (i.e. the time corresponding to 1970-01-01 at
+ 00:00 UTC plus the offset corresponding to the time zone).</p>
</div>
@@ -16201,11 +16201,11 @@
<p>If the <code title="attr-meter-min">min</code> attribute
attribute is specified, then the <var title="">minimum</var> is
- that attribue's value; otherwise, it is 0.</p>
+ that attribute's value; otherwise, it is 0.</p>
<p>If the <code title="attr-meter-max">max</code> attribute
attribute is specified, then the <var title="">maximum</var> is
- that attribue's value; otherwise, it is 1.</p>
+ that attribute's value; otherwise, it is 1.</p>
<p>If there is exactly one number in the contents of the element,
then <var title="">value</var> is that number; otherwise, <var
@@ -16640,7 +16640,7 @@
variable in prose:</p>
<pre><p>If there are <var>n</var> pipes leading to the ice
cream factory then I expect at <em>least</em> <var>n</var>
-flavours of ice cream to be available for purchase!</p></pre>
+flavors of ice cream to be available for purchase!</p></pre>
</div>
<p>For mathematics, in particular for anything beyond the simplest
@@ -17472,7 +17472,7 @@
timestamp (the value is non-conforming; it is not a <span>valid
global date and time string</span>). Otherwise, the modification is
marked as having been made at the given datetime. User agents should
- use the associated timezone information to determine which timezone
+ use the associated time-zone information to determine which time zone
to present the given datetime in.</p>
</div>
@@ -17576,7 +17576,7 @@
<p>In the following example, a list that started empty had items
added and removed from it over time. The bits in the example that
- have been emphasised show the parts that are the "current" state of
+ have been emphasized show the parts that are the "current" state of
the list. The list item numbers don't take into account the edits,
though.</p>
@@ -17909,7 +17909,7 @@
(e.g. scripts) embedded in the image resource. User agents must only
display the first page of a multipage resource (e.g. a PDF
file). User agents must not allow the resource to act in an
- interactive fashion, but should honour any animation in the
+ interactive fashion, but should honor any animation in the
resource.</p>
<p>This specification does not specify which image types are to be
@@ -18267,7 +18267,7 @@
<pre><article>
<h1>My cats</h1>
<h2>Fluffy</h2>
- <p>Fluffy is my favourite.</p>
+ <p>Fluffy is my favorite.</p>
<img src="fluffy.jpg" alt="She likes playing with a ball of yarn.">
<p>She's just too cute.</p>
<h2>Miles</h2>
@@ -18396,10 +18396,10 @@
<pre><p>In the common case, the data handled by the tokenization stage
comes from the network, but it can also come from script.</p>
<p><strong><img src="images/parsing-model-overview.png" alt="The network
-passes data to the Tokeniser stage, which passes data to the Tree
+passes data to the Tokenizer stage, which passes data to the Tree
Construction stage. From there, data goes to both the DOM and to
Script Execution. Script Execution is linked to the DOM, and, using
-document.write(), passes data to the Tokeniser."></strong></p></pre>
+document.write(), passes data to the Tokenizer."></strong></p></pre>
</div>
@@ -18608,11 +18608,11 @@
<p>A flowchart that repeats the previous paragraph in graphical form:</p>
- <pre><p>The network passes data to the Tokeniser stage, which
+ <pre><p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<strong><p><img src="images/parsing-model-overview.png" alt=""></p></strong></pre>
<p>In these cases, it would be wrong to include alternative text
@@ -18624,36 +18624,36 @@
representation, and would thus require alternative text.</p>
<pre><!-- Using the title="" attribute -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<p><strong><img src="images/parsing-model-overview.png" alt=""
title="Flowchart representation of the parsing model."></strong></p></pre>
<pre><!-- Using <figure> and <legend> -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<figure>
<strong><img src="images/parsing-model-overview.png" alt="The Network leads
- to the Tokeniser, which leads to the Tree Construction. The Tree
+ to the Tokenizer, which leads to the Tree Construction. The Tree
Construction leads to two items. The first is Script Execution, which
- leads via document.write() back to the Tokeniser. The second item
+ leads via document.write() back to the Tokenizer. The second item
from which Tree Construction leads is the DOM. The DOM is related to
the Script Execution."></strong>
<legend>Flowchart representation of the parsing model.</legend>
</figure></pre>
<pre class="bad"><!-- This is WRONG. Do not do this. Instead, do what the above examples do. -->
-<p>The network passes data to the Tokeniser stage, which
+<p>The network passes data to the Tokenizer stage, which
passes data to the Tree Construction stage. From there, data goes
to both the DOM and to Script Execution. Script Execution is
linked to the DOM, and, using document.write(), passes data to
-the Tokeniser.</p>
+the Tokenizer.</p>
<p><img src="images/parsing-model-overview.png"
alt="Flowchart representation of the parsing model."></p>
<!-- Never put the image's caption in the alt="" attribute! --></pre>
@@ -19132,7 +19132,7 @@
<p>Markup generators (such as WYSIWYG authoring tools) should,
wherever possible, obtain alternative text from their
- users. However, it is recognised that in many cases, this will not
+ users. However, it is recognized that in many cases, this will not
be possible.</p>
<p>For images that are the sole contents of links, markup generators
@@ -19145,7 +19145,7 @@
the assumption that the image is a purely decorative image that
doesn't add any information but is still specific to the surrounding
content, or omit the <code title="attr-img-alt">alt</code> attribute
- altogther, under the assumption that the image is a key part of the
+ altogether, under the assumption that the image is a key part of the
content.</p>
<p>Markup generators should generally avoid using the image's own
@@ -19303,7 +19303,7 @@
title="attr-iframe-sandbox-allow-scripts">allow-scripts</code>. When
the attribute is set, the content is treated as being from a unique
<span>origin</span>, forms and scripts are disabled, links are
- prevented from targetting other <span title="browsing
+ prevented from targeting other <span title="browsing
context">browsing contexts</span>, and plugins are disabled. The
<code
title="attr-iframe-sandbox-allow-same-origin">allow-same-origin</code>
@@ -21263,7 +21263,7 @@
<p><dfn>A type that the user agent knows it cannot render</dfn> is
one that describes a resource that the user agent definitely does
- not support, for example because it doesn't recognise the container
+ not support, for example because it doesn't recognize the container
type, or it doesn't support the listed codecs.</p>
<dl class="domintro">
@@ -23771,7 +23771,7 @@
<hr>
- <p>If a hostile page embeds victom content, the threat is that the
+ <p>If a hostile page embeds victim content, the threat is that the
embedding page could obtain information from the content that it
would not otherwise have access to. The API does expose some
information: the existence of the media, its type, its duration, its
@@ -27584,7 +27584,7 @@
<p><img src="images/sample-usemap.png" alt="A line with four shapes in it, equally spaced: a red hollow box, a green circle, a blue triangle, and a yellow four-pointed star."></p>
- <p>If we wanted just the coloured areas to be clickable, we could
+ <p>If we wanted just the colored areas to be clickable, we could
do it as follows:</p>
<pre><p>
@@ -30691,7 +30691,7 @@
<p>The
<span>indices of the supported indexed properties</span> at any
- instant are the indicies supported by the object returned by the
+ instant are the indices supported by the object returned by the
<code title="dom-form-elements">elements</code> attribute at that
instant.</p>
@@ -30822,7 +30822,7 @@
<dt>Contexts in which this element may be used:</dt>
<dd>Where <span>flow content</span> is expected.</dd>
<dt>Content model:</dt>
- <dd>One <code>legend</code> element follwed by <span>flow content</span>.</dd>
+ <dd>One <code>legend</code> element followed by <span>flow content</span>.</dd>
<dt>Content attributes:</dt>
<dd><span>Global attributes</span></dd>
<dd><code title="attr-fieldset-disabled">disabled</code></dd>
@@ -31330,7 +31330,7 @@
and <code title="dom-input-stepDown">stepDown()</code> methods, are
specific to certain states. The following table <span
class="impl">is non-normative and</span> summarises which content
- attributes, DOM attrbutes, and methods apply to each state:</p>
+ attributes, DOM attributes, and methods apply to each state:</p>
<table class="applies">
<thead>
@@ -32294,7 +32294,7 @@
<p>When an <code>input</code> element's <code
title="attr-input-type">type</code> attribute changes state, and
when the element is first created, the element's rendering and
- behaviour must change to the new state's accordingly and the
+ behavior must change to the new state's accordingly and the
<dfn>value sanitization algorithm</dfn>, if one is defined for the
<code title="attr-input-type">type</code> attribute's new state,
must be invoked.</p>
@@ -33027,7 +33027,7 @@
title="concept-fe-value">value</span> to a string representing a
specific <span title="concept-datetime">global date and
time</span>. <span class="impl">User agents may display the date and
- time in whatever timezone is appropriate for the user.</span></p>
+ time in whatever time zone is appropriate for the user.</span></p>
<div class="impl">
@@ -33040,8 +33040,8 @@
set the <span title="concept-fe-value">value</span> to a string that
is not a <span>valid global date and time string</span> expressed in
UTC, though user agents may allow the user to set and view the time
- in another timezone and silently translate the time to and from the
- UTC timezone in the <span title="concept-fe-value">value</span>. If
+ in another time zone and silently translate the time to and from the
+ UTC time zone in the <span title="concept-fe-value">value</span>. If
the user agent provides a user interface for selecting a <span
title="concept-datetime">global date and time</span>, then the <span
title="concept-fe-value">value</span> must be set to a <span>valid
@@ -33063,7 +33063,7 @@
of the element is a <span>valid global date and time string</span>,
then adjust the time so that the <span
title="concept-fe-value">value</span> represents the same point in
- time but expressed in the UTC timezone, otherwise, set it to the
+ time but expressed in the UTC time zone, otherwise, set it to the
empty string instead.</p>
</div>
@@ -33296,7 +33296,7 @@
follows:</strong> Return a <span>valid date string</span> that
represents the <span title="concept-date">date</span> current at the
time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -33463,7 +33463,7 @@
follows:</strong> Return a <span>valid month string</span> that
represents the <span title="concept-month">month</span> current at
the time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -33630,7 +33630,7 @@
follows:</strong> Return a <span>valid week string</span> that
represents the <span title="concept-week">week</span> current at the
time represented by <var title="">input</var> in the UTC
- timezone.</p>
+ time zone.</p>
</div>
@@ -35037,7 +35037,7 @@
<code>input</code> element. User agents must not run executable code
embedded in the image resource. User agents must only display the
first page of a multipage resource. User agents must not allow the
- resource to act in an interactive fashion, but should honour any
+ resource to act in an interactive fashion, but should honor any
animation in the resource.</p>
<p>The <span title="concept-task">task</span> that is <span
@@ -36821,7 +36821,7 @@
<p>The <code title="dom-select-options">options</code> collection is
also mirrored on the <code>HTMLSelectElement</code> object. The
<span>indices of the supported indexed properties</span> at any
- instant are the indicies supported by the object returned by the
+ instant are the indices supported by the object returned by the
<code title="dom-select-options">options</code> attribute at that
instant. The <span>names of the supported named properties</span> at
any instant are the names supported by the object returned by the
@@ -37286,7 +37286,7 @@
value. If the <var title="">selected</var> argument is present and
true, the new object must have its <span
title="concept-option-selectedness">selectedness</span> set to true;
- otherwise the fouth argument is absent or false, and the <span
+ otherwise the fourth argument is absent or false, and the <span
title="concept-option-selectedness">selectedness</span> must be set
to false, even if the <var title="">defaultSelected</var> argument
is present and true.</p>
@@ -37495,9 +37495,9 @@
<ol>
- <li><p>Replace every occurance of a U+000D CARRIAGE RETURN (CR)
+ <li><p>Replace every occurrence of a U+000D CARRIAGE RETURN (CR)
character not followed by a U+000A LINE FEED (LF) character, and
- every occurance of a U+000A LINE FEED (LF) character not proceeded
+ every occurrence of a U+000A LINE FEED (LF) character not proceeded
by a U+000D CARRIAGE RETURN (CR) character, by a two-character
string consisting of a U+000D CARRIAGE RETURN - U+000A LINE FEED
(CRLF) character pair.</p></li>
@@ -38782,7 +38782,7 @@
element.</p></li>
<li><p>Otherwise, if <var title="">field</var> <span
- title="concept-fv-valid">satisfies its constaints</span>, then
+ title="concept-fv-valid">satisfies its constraints</span>, then
move on to the next element.</p></li>
<li><p>Otherwise, add <var title="">field</var> to <var
@@ -38877,7 +38877,7 @@
<dd>
- <p>Sets a custom error, so that the elemnt would fail to
+ <p>Sets a custom error, so that the element would fail to
validate. The given message is the message to be shown to the user
when reporting the problem to the user.</p>
@@ -39052,7 +39052,7 @@
title="dom-cva-checkValidatity"><code>checkValidity()</code></dfn>
method is invoked, if the element is a <span>candidate for
constraint validation</span> and does not <span
- title="concept-fv-valid">satisfy its constaints</span>, the user
+ title="concept-fv-valid">satisfy its constraints</span>, the user
agent must <span>fire a simple event</span> named <code
title="event-invalid">invalid</code> at the element and return
false. Otherwise, it must only return true without doing anything
@@ -39062,7 +39062,7 @@
title="dom-cva-validationMessage"><code>validationMessage</code></dfn>
attribute must return the empty string if the element is not a
<span>candidate for constraint validation</span> or if it is one but
- it <span title="concept-fv-valid">satisfies its constaints</span>;
+ it <span title="concept-fv-valid">satisfies its constraints</span>;
otherwise, it must return a suitably localised message that the user
agent would show the user if this were the only form with a validity
constraint problem. If the element is <span>suffering from a custom
@@ -39283,7 +39283,7 @@
the user <span
title="concept-input-type-image-coordinate">indicated a
coordinate</span>. Let <var title="">x</var> be the <var
- title="">x</var>-component of the coordindate selected by the
+ title="">x</var>-component of the coordinate selected by the
user, and let <var title="">y</var> be the <var
title="">y</var>-component of the coordinate selected by the
user.</p></li>
@@ -39606,7 +39606,7 @@
title="">unreserved</code> production in the URI Generic Syntax,
and then, treating the result as a US-ASCII string, further
%-escape all the U+0025 PERCENT SIGN characters in the resulting
- string and replace the first occurance of "<code
+ string and replace the first occurrence of "<code
title="">%%%%</code>" in <var title="">action</var> with the
resulting double-escaped string. <a
href="#refsRFC3986">[RFC3986]</a></p>
@@ -39617,7 +39617,7 @@
title="">data</var> that, if interpreted as US-ASCII, do not
match the <code title="">unreserved</code> production in the URI
Generic Syntax, and then, treating the result as a US-ASCII
- string, replace the first occurance of "<code
+ string, replace the first occurrence of "<code
title="">%%</code>" in <var title="">action</var> with the
resulting escaped string. <a
href="#refsRFC3986">[RFC3986]</a></p>
@@ -39697,8 +39697,8 @@
title="">application/x-www-form-urlencoded</code> encoding
algorithm</span>, interpreted as a US-ASCII string.</p>
- <p>Replace occurances of U+002B PLUS SIGN characters (+) in <var
- title="">headers</var> with the string "<code
+ <p>Replace occurrences of U+002B PLUS SIGN characters (+) in
+ <var title="">headers</var> with the string "<code
title="">%20</code>".</p>
<p>Let <var title="">destination</var> consist of all the
@@ -40132,7 +40132,7 @@
be shown or hidden. To honor a request for the details to be shown,
the user agent must set the <code
title="attr-details-open">open</code> attribute on the element to
- the value <code title="">open</code>. To honour a request for the
+ the value <code title="">open</code>. To honor a request for the
details to be hidden, the user agent must remove the <code
title="attr-details-open">open</code> attribute from the
element.</p>
@@ -43088,7 +43088,7 @@
title="attr-bb-type">type</code> attribute is in a state other than
the <i title="attr-bb-type-null-state">null</i> state and the user
agent supports that state's <i>action</i> (i.e. when the attribute's
- value is one that the user agent recognises and supports), and false
+ value is one that the user agent recognizes and supports), and false
otherwise.</p>
<p>The <dfn title="dom-bb-disabled"><code>disabled</code></dfn> DOM
@@ -46845,7 +46845,7 @@
<dt>Parsing</dt>
- <dd><p>The <span>HTML parser</span> tokenising a single byte, and
+ <dd><p>The <span>HTML parser</span> tokenizing a single byte, and
then processing any resulting tokens, is a task.</p></dd>
@@ -48456,7 +48456,7 @@
<var title="">url</var> argument passed to one of these methods does
not contain the exact literal string "<code>%s</code>", or if <span
title="resolve a url">resolving</span> the <var title="">url</var>
- argument with the first occurance of the string "<code
+ argument with the first occurrence of the string "<code
title="">%s</code>" removed, relative to the <span>first
script</span>'s <span title="script's base URL">base URL</span>, is
not successful.</p>
@@ -48555,8 +48555,8 @@
<p><strong>Leaking secure URLs.</strong> User agents should not send
HTTPS URLs to third-party sites registered as content handlers, in
the same way that user agents do not send <code
- title="http-referer">Referer</code> headers from secure sites to
- third-party sites.</p>
+ title="http-referer">Referer</code> (sic) HTTP headers from secure
+ sites to third-party sites.</p>
<p><strong>Leaking credentials.</strong> User agents must never send
username or password information in the URLs that are escaped and
@@ -49353,7 +49353,7 @@
<li>
- <p>Pick the approprate substeps:</p>
+ <p>Pick the appropriate substeps:</p>
<dl class="switch">
@@ -49843,7 +49843,7 @@
either completely downloaded or failed.</p>
<p>If the download failed (e.g. the connection times out, or the
- user cancels the download), then run these sebsteps:</p>
+ user cancels the download), then run these substeps:</p>
<ol>
@@ -51456,13 +51456,13 @@
actually wants to use this ability, so requiring it here seems
like unnecessary work. -->
- <p>HTTP 401 responses that do not include a challenge recognised
+ <p>HTTP 401 responses that do not include a challenge recognized
by the user agent must be processed as if they had no challenge,
e.g. rendering the entity body as if the response had been 200
OK.</p>
<p>User agents may show the entity body of an HTTP 401 response
- even when the response do include a recognised challenge, with the
+ even when the response do include a recognized challenge, with the
option to login being included in a non-modal fashion, to enable
the information provided by the server to be used by the user
before authenticating. Similarly, user agents should allow the
@@ -51632,7 +51632,7 @@
<li><p>Wait for a user-agent defined amount of time, as desired
by the user agent implementor. (This is intended to allow the
- user agent to optimise the user experience in the face of
+ user agent to optimize the user experience in the face of
performance concerns.)</p></li>
<li><p>If the <code>Document</code> object has no parser, or its
@@ -51668,11 +51668,11 @@
document as the <span>input stream</span> for that parser.</p>
<p class="note">The <span>input stream</span> converts bytes into
- characters for use in the <span>tokeniser</span><!-- XXX xref
- -->. This process relies, in part, on character encoding information
- found in the real <span title="Content-Type">Content-Type
- metadata</span> of the resource; the "sniffed type" is not used for
- this purpose.</p>
+ characters for use in the <span
+ title="tokenization">tokenizer</span>. This process relies, in part,
+ on character encoding information found in the real <span
+ title="Content-Type">Content-Type metadata</span> of the resource;
+ the "sniffed type" is not used for this purpose.</p>
<!-- next two paragraphs are nearly identical to the navigate-text
section, keep them in sync -->
@@ -51733,7 +51733,7 @@
title="attr-html-manifest">manifest</code> attribute happens
only once the root element is parsed, any URLs referenced by
processing instructions before the root element (such as <code
- title=""><?xml-styleesheet?></code> and <code
+ title=""><?xml-stylesheet?></code> and <code
title=""><?xbl?></code> PIs) will be fetched from the network and
cannot be cached.</p> <!-- XXX any ideas for avoiding this, that
aren't a PI themselves? We can't delay the processing, since the
@@ -51766,11 +51766,11 @@
context</span>, the user agent should create a <code>Document</code>
object, mark it as being an <span title="HTML documents">HTML
document</span>, create an <span>HTML parser</span>, associate it
- with the document, act as if the tokeniser had emitted a start tag
+ with the document, act as if the tokenizer had emitted a start tag
token with the tag name "pre", set the <span>tokenization</span>
stage's <span>content model flag</span> to <i>PLAINTEXT</i>, and
begin to pass the stream of characters in the plain text document to
- that tokeniser.</p>
+ that tokenizer.</p>
<p>The rules for how to convert the bytes of the plain text document
into actual characters are defined in RFC 2046, RFC 2646, and
@@ -53967,11 +53967,11 @@
<p>User agents should allow the user to adjust this behavior, for
example in conjunction with a setting that disables the sending of
- HTTP <code title="http-referer">Referer</code> headers. Based on the
- user's preferences, UAs may either <span>ignore</span> the <code
- title="attr-hyperlink-ping">ping</code> attribute altogether, or
- selectively ignore URLs in the list (e.g. ignoring any third-party
- URLs).</p>
+ HTTP <code title="http-referer">Referer</code> (sic) headers. Based
+ on the user's preferences, UAs may either <span>ignore</span> the
+ <code title="attr-hyperlink-ping">ping</code> attribute altogether,
+ or selectively ignore URLs in the list (e.g. ignoring any
+ third-party URLs).</p>
<p>For URLs that are HTTP URLs, the requests must be performed by
<span title="fetch">fetching</span> the specified URLs using the
@@ -53994,20 +53994,20 @@
title="http-ping-to">Ping-To</code> HTTP header with, as its value,
the address of the <span>absolute URL</span> of the target of the
hyperlink. The request must not include a <code
- title="http-referer">Referer</code> HTTP header. <!-- because
+ title="http-referer">Referer</code> (sic) HTTP header. <!-- because
otherwise it would look like a trustable same-origin POST --></dd>
<dt>Otherwise, if the origins are different, but the document
containing the hyperlink being audited was not retrieved over an
encrypted connection</dt>
- <dd>The request must include a <code title="">Referer</code> HTTP
- header [sic] with, as its value, the <span title="the document's
- address">address</span> of the document containing the hyperlink, a
- <code title="http-ping-from">Ping-From</code> HTTP header with the
- same value, and a <code title="http-ping-to">Ping-To</code> HTTP
- header with, as its value, the address of the target of the
- hyperlink.</dd>
+ <dd>The request must include a <code title="">Referer</code> (sic)
+ HTTP header [sic] with, as its value, the <span title="the
+ document's address">address</span> of the document containing the
+ hyperlink, a <code title="http-ping-from">Ping-From</code> HTTP
+ header with the same value, and a <code
+ title="http-ping-to">Ping-To</code> HTTP header with, as its value,
+ the address of the target of the hyperlink.</dd>
<dt>Otherwise, the origins are different and the document
containing the hyperlink being audited was retrieved over an
@@ -54016,8 +54016,8 @@
<dd>The request must include a <code
title="http-ping-to">Ping-To</code> HTTP header with, as its value,
the address of the target of the hyperlink. The request must
- neither include a <code title="">Referer</code> HTTP header nor
- include a <code title="http-ping-from">Ping-From</code> HTTP
+ neither include a <code title="">Referer</code> (sic) HTTP header
+ nor include a <code title="http-ping-from">Ping-From</code> HTTP
header.</dd>
</dl>
@@ -54256,7 +54256,7 @@
<td><code title="rel-noreferrer">noreferrer</code></td>
<td><em>not allowed</em></td>
<td><span>Hyperlink</span></td>
- <td>Requires that the user agent not send an HTTP <code title="">Referer</code> header if the user follows the hyperlink.</td>
+ <td>Requires that the user agent not send an HTTP <code title="">Referer</code> (sic) header if the user follows the hyperlink.</td>
</tr>
<tr>
@@ -54827,9 +54827,9 @@
<p>If a user agent follows a link defined by an <code>a</code> or
<code>area</code> element that has the <code
title="rel-noreferrer">noreferrer</code> keyword, the user agent
- must not include a <code title="">Referer</code> HTTP header (<span
- title="concept-http-equivalent-headers">or equivalent</span> for
- other protocols) in the request.</p>
+ must not include a <code title="">Referer</code> (sic) HTTP header
+ (<span title="concept-http-equivalent-headers">or equivalent</span>
+ for other protocols) in the request.</p>
<p>This keyword also <a href="#noopener">causes the <code
title="dom-opener">opener</code> attribute to remain null</a> if the
@@ -55503,7 +55503,7 @@
<p>User agents may track focus for each <span>browsing
context</span> or <code>Document</code> individually, or may support
- only one focused elment per <span>top-level browsing context</span>
+ only one focused element per <span>top-level browsing context</span>
— user agents should follow platform conventions in this
regard.</p>
@@ -56327,7 +56327,7 @@
</div>
<div class="example">
- <p>In the following document fragment, the emphasised parts
+ <p>In the following document fragment, the emphasized parts
indicate the selection.</p>
<pre><p>The cute girl likes <em>the </em><cite><em>Oxford English</em> Dictionary</cite>.</p></pre>
<p>If a script invoked <code
@@ -58804,7 +58804,7 @@
<dd>
- <p>Returns teh value of the command, as described in the list below.</p>
+ <p>Returns the value of the command, as described in the list below.</p>
</dd>
@@ -59320,7 +59320,7 @@
<pre>EXAMPLE primes/worker.js</pre>
- <p>The bulk of this code is simply an unoptimised search for a prime
+ <p>The bulk of this code is simply an unoptimized search for a prime
number. To send a message back to the page, the <code
title="dom-DedicatedWorkerGlobalScope-postMessage">postMessage()</code>
method is used to post a message when a prime is found.</p>
@@ -62614,7 +62614,7 @@
<ol>
<li><p>Read a byte from the client. Assuming everything is going
- according to plan, it will be a 0x00 byte. Behaviour for the server
+ according to plan, it will be a 0x00 byte. Behavior for the server
is undefined if the byte is not 0x00.</p></li>
<li><p>Let <var title="">raw data</var> be an empty byte
@@ -64439,10 +64439,10 @@
<p><img src="images/parsing-model-overview.png" alt=""></p>
- <p id="nestedParsing">There is only one set of state for the
- tokeniser stage and the tree construction stage, but the tree
+ <p id="nestedParsing">There is only one set of states for the
+ tokenizer stage and the tree construction stage, but the tree
construction stage is reentrant, meaning that while the tree
- construction stage is handling one token, the tokeniser might be
+ construction stage is handling one token, the tokenizer might be
resumed, causing further tokens to be emitted and processed before
the first token's processing is complete.</p>
@@ -64467,7 +64467,7 @@
<h4>The <dfn>input stream</dfn></h4>
- <p>The stream of Unicode characters that consists the input to the
+ <p>The stream of Unicode characters that comprises the input to the
tokenization stage will be initially seen by the user agent as a
stream of bytes (typically coming over the network or from the local
file system). The bytes encode the actual characters according to a
@@ -64941,7 +64941,7 @@
<h5>Preprocessing the input stream</h5>
<p>Given an encoding, the bytes in the input stream must be
- converted to Unicode characters for the tokeniser, as described by
+ converted to Unicode characters for the tokenizer, as described by
the rules for that encoding, except that the leading U+FEFF BYTE
ORDER MARK character, if any, must not be stripped by the encoding
layer (it is stripped by the rule below).</p> <!-- this is to
@@ -65551,7 +65551,7 @@
<h4><dfn>Tokenization</dfn></h4>
<p>Implementations must act as if they used the following state
- machine to tokenise HTML. The state machine must start in the
+ machine to tokenize HTML. The state machine must start in the
<span>data state</span>. Most states consume a single character,
which may have various side-effects, and either switches the state
machine to a new state to <em>reconsume</em> the same character, or
@@ -65566,7 +65566,7 @@
title="">RCDATA</i>, <i title="">CDATA</i>, and <i
title="">PLAINTEXT</i>. Initially it must be in the PCDATA
state. In the RCDATA and CDATA states, a further <dfn>escape
- flag</dfn> is used to control the behavior of the tokeniser. It is
+ flag</dfn> is used to control the behavior of the tokenizer. It is
either true or false, and initially must be set to the false
state. The <span>insertion mode</span> and the <span>stack of open
elements</span> also affects tokenization.</p>
@@ -65592,7 +65592,7 @@
insert additional characters into the stream. (For example, the
<code>script</code> element can result in scripts executing and
using the <span>dynamic markup insertion</span> APIs to insert
- characters into the stream being tokenised.)</p>
+ characters into the stream being tokenized.)</p>
<p>When a start tag token is emitted with its <i>self-closing
flag</i> set, if the flag is not <dfn title="acknowledge
@@ -65608,10 +65608,10 @@
<p>When an end tag token is emitted with its <i>self-closing
flag</i> set, that is a <span>parse error</span>.</p>
- <p>Before each step of the tokeniser, the user agent must first
+ <p>Before each step of the tokenizer, the user agent must first
check the <span>parser pause flag</span>. If it is true, then the
- tokeniser must abort the processing of any nested invocations of the
- tokeniser, yielding control back to the caller. If it is false, then
+ tokenizer must abort the processing of any nested invocations of the
+ tokenizer, yielding control back to the caller. If it is false, then
the user agent may then check to see if either one of the scripts in
the <span>list of scripts that will execute as soon as
possible</span> or the first script in the <span>list of scripts
@@ -65619,7 +65619,7 @@
loading</span>. If one has, then it must be <span title="executing a
script block">executed</span> and removed from its list.</p>
- <p>The tokeniser state machine consists of the states defined in the
+ <p>The tokenizer state machine consists of the states defined in the
following subsections.</p>
<!-- XXX should go through these reordering the entries so that
@@ -65782,7 +65782,7 @@
<p>If the <span>content model flag</span> is set to the RCDATA or
CDATA states but no start tag token has ever been emitted by this
- instance of the tokeniser (<span>fragment case</span>), or, if the
+ instance of the tokenizer (<span>fragment case</span>), or, if the
<span>content model flag</span> is set to the RCDATA or CDATA states
and the next few characters do not match the tag name of the last
start tag token emitted (compared in an <span>ASCII
@@ -67069,7 +67069,7 @@
has to render the <code>Document</code> so that it is available to
the user, or when it has to begin accepting user input.</p>
- <p>As each token is emitted from the tokeniser, the user agent must
+ <p>As each token is emitted from the tokenizer, the user agent must
process the token according to the rules given in the section
corresponding to the current <span>insertion mode</span>.</p>
@@ -67294,10 +67294,10 @@
<li><p><span>Insert an HTML element</span> for the token.</p></li>
<li><p>If the algorithm that was invoked is the <span>generic CDATA
- element parsing algorithm</span>, switch the tokeniser's
+ element parsing algorithm</span>, switch the tokenizer's
<span>content model flag</span> to the CDATA state; otherwise the
algorithm invoked was the <span>generic RCDATA element parsing
- algorithm</span>, switch the tokeniser's <span>content model
+ algorithm</span>, switch the tokenizer's <span>content model
flag</span> to the RCDATA state.</p></li>
<li><p>Let the <span>original insertion mode</span> be the current
@@ -67831,7 +67831,7 @@
and push it onto the <span>stack of open
elements</span>.</p></li>
- <li><p>Switch the tokeniser's <span>content model flag</span> to
+ <li><p>Switch the tokenizer's <span>content model flag</span> to
the CDATA state.</p></li>
<li><p>Let the <span>original insertion mode</span> be the current
@@ -69053,7 +69053,7 @@
one. (Newlines at the start of <code>textarea</code> elements are
ignored as an authoring convenience.)</p></li>
- <li><p>Switch the tokeniser's <span>content model flag</span> to
+ <li><p>Switch the tokenizer's <span>content model flag</span> to
the RCDATA state.</p></li>
<li><p>Let the <span>original insertion mode</span> be the
@@ -69374,8 +69374,8 @@
<p><span title="running a script">Run</span> the <var
title="">script</var>. This might cause some script to execute,
which might cause <span title="dom-document-write">new characters
- to be inserted into the tokeniser</span>, and might cause the
- tokeniser to output more tokens, resulting in a <a
+ to be inserted into the tokenizer</span>, and might cause the
+ tokenizer to output more tokens, resulting in a <a
href="#nestedParsing">reentrant invocation of the parser</a>.</p>
<p>Decrement the parser's <span>script nesting level</span> by
@@ -69398,7 +69398,7 @@
title="dom-document-write">document.write()</code>:</dt>
<dd><p>Set the <span>parser pause flag</span> to true, and abort
- the processing of any nested invocations of the tokeniser,
+ the processing of any nested invocations of the tokenizer,
yielding control back to the caller. (Tokenization will resume
when the caller returns to the "outer" tree construction
stage.)</p></dd>
@@ -70341,7 +70341,7 @@
<p class="note">Even if this causes <span
title="dom-document-write">new characters to be inserted into the
- tokeniser</span>, the parser will not be executed reentrantly,
+ tokenizer</span>, the parser will not be executed reentrantly,
since the <span>parser pause flag</span> is true.</p>
<p>Decrement the parser's <span>script nesting level</span> by
@@ -74245,12 +74245,12 @@
<p>To ease the transition from HTML4 Transitional documents to the
language defined in <em>this</em> specification, conformance
- checkers are encouraged to categorise errors that represent usage of
+ checkers are encouraged to categorize errors that represent usage of
old obsolete features that generally have no effect (as defined
below) into a separate part of their report, to allow authors to
distinguish between likely mistakes and mere vestigial markup.</p>
- <p>The following errors may be categorised as described above:</p>
+ <p>The following errors may be categorized as described above:</p>
<ul><!-- downplayed list -->
@@ -74725,6 +74725,7 @@
Jens Bannmann,
Jens Fendler,
Jens Lindström,
+ Jens Meiert,
Jeroen van der Meer,
Jim Jewett,
Jim Ley,
@@ -74861,6 +74862,7 @@
Sam Weinig,
Sander van Lambalgen,
Scott Hess,
+ Sean Fraser,
Sean Hogen,
Sean Knapp,
Sebastian Schnitzenbaumer,
More information about the Commit-Watchers
mailing list