[html5] r3774 - [e] (0) grammar fix

[whatwg at whatwg.org]

Author: ianh
Date: 2009-09-09 02:42:09 -0700 (Wed, 09 Sep 2009)
New Revision: 3774

Modified:
   index
   source
Log:
[e] (0) grammar fix

Modified: index
===================================================================
--- index	2009-09-09 07:40:25 UTC (rev 3773)
+++ index	2009-09-09 09:42:09 UTC (rev 3774)
@@ -2465,7 +2465,7 @@
   <p>The <dfn id=rules-for-parsing-non-negative-integers>rules for parsing non-negative integers</dfn> are as
   given in the following algorithm. When invoked, the steps must be
   followed in the order given, aborting at the first step that returns
-  a value. This algorithm will either return zero, a positive integer,
+  a value. This algorithm will return either zero, a positive integer,
   or an error. Leading spaces are ignored. Trailing spaces and any
   trailing garbage characters are ignored.</p>
 
@@ -2537,7 +2537,7 @@
   non-negative integers</a>, and are as given in the following
   algorithm. When invoked, the steps must be followed in the order
   given, aborting at the first step that returns a value. This
-  algorithm will either return an integer or an error. Leading spaces
+  algorithm will return either an integer or an error. Leading spaces
   are ignored. Trailing spaces and trailing garbage characters are
   ignored.</p>
 
@@ -2664,8 +2664,8 @@
 
   <p>The <dfn id=rules-for-parsing-floating-point-number-values>rules for parsing floating point number values</dfn> are
   as given in the following algorithm. This algorithm must be aborted
-  at the first step that returns something. This algorithm will either
-  return a number or an error. Leading spaces are ignored. Trailing
+  at the first step that returns something. This algorithm will return
+  either a number or an error. Leading spaces are ignored. Trailing
   spaces and garbage characters are ignored.</p>
 
   <ol><li><p>Let <var title="">input</var> be the string being
@@ -2938,7 +2938,7 @@
   <p>The <dfn id=rules-for-parsing-dimension-values>rules for parsing dimension values</dfn> are as given in
   the following algorithm. When invoked, the steps must be followed in
   the order given, aborting at the first step that returns a
-  value. This algorithm will either return a number greater than or
+  value. This algorithm will return either a number greater than or
   equal to 1.0, or an error; if a number is returned, then it is
   further categorized as either a percentage or a length.</p>
 
@@ -3429,7 +3429,7 @@
   </ol><div class=impl>
 
   <p>The rules to <dfn id=parse-a-month-string>parse a month string</dfn> are as follows. This
-  will either return a year and month, or nothing. If at any point the
+  will return either a year and month, 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>
 
@@ -3448,7 +3448,7 @@
    <li><p>Return <var title="">year</var> and <var title="">month</var>.</li>
 
   </ol><p>The rules to <dfn id=parse-a-month-component>parse a month component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return a year and a month, or
+  as follows. This will return either a year and a month, 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>
 
@@ -3503,7 +3503,7 @@
   </ol><div class=impl>
 
   <p>The rules to <dfn id=parse-a-date-string>parse a date string</dfn> are as follows. This
-  will either return a date, or nothing. If at any point the algorithm
+  will return either a date, 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>
 
@@ -3523,7 +3523,7 @@
    <li><p>Return <var title="">date</var>.</li>
 
   </ol><p>The rules to <dfn id=parse-a-date-component>parse a date component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return a year, a month, and a day, or
+  as follows. This will return either a year, a month, and a day, 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>
 
@@ -3600,7 +3600,7 @@
   <div class=impl>
 
   <p>The rules to <dfn id=parse-a-time-string>parse a time string</dfn> are as follows. This
-  will either return a time, or nothing. If at any point the algorithm
+  will return either a time, 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>
 
@@ -3621,7 +3621,7 @@
    <li><p>Return <var title="">time</var>.</li>
 
   </ol><p>The rules to <dfn id=parse-a-time-component>parse a time component</dfn>, given an <var title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return an hour, a minute, and a second,
+  as follows. This will return either an hour, a minute, and a second,
   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>
 
@@ -3710,7 +3710,7 @@
   </ol><div class=impl>
 
   <p>The rules to <dfn id=parse-a-local-date-and-time-string>parse a local date and time string</dfn> are as
-  follows. This will either return a date and time, or nothing. If at
+  follows. This will return either a date and time, 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>
 
@@ -3846,7 +3846,7 @@
   time zone is UTC.</p>
 
   <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
+  as follows. This will return either a time in UTC, with associated
   time-zone offset 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>
@@ -3887,7 +3887,7 @@
    <li><p>Return <var title="">time</var> and <var title="">timezone</var>.</li>
 
   </ol><p>The rules to <dfn id=parse-a-time-zone-offset-component>parse a time-zone offset component</dfn>, given
-  an <var title="">input</var> string and a <var title="">position</var>, are as follows. This will either return
+  an <var title="">input</var> string and a <var title="">position</var>, are as follows. This will return either
   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>
@@ -3998,7 +3998,7 @@
   </ol><div class=impl>
 
   <p>The rules to <dfn id=parse-a-week-string>parse a week string</dfn> are as follows. This
-  will either return a week-year number and week number, or
+  will return either a week-year number and week number, 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>
 
@@ -4080,7 +4080,7 @@
   <hr><p>The rules to <dfn id=parse-a-date-or-time-string>parse a date or time string</dfn> are as
   follows. The algorithm is invoked with a flag indicating if the
   <i>in attribute</i> variant or the <i>in content</i> variant is to
-  be used. The algorithm will either return a <a href=#concept-date title=concept-date>date</a>, a <a href=#concept-time title=concept-time>time</a>, a <a href=#concept-datetime title=concept-datetime>global date and time</a>, or nothing. If
+  be used. The algorithm will return either a <a href=#concept-date title=concept-date>date</a>, a <a href=#concept-time title=concept-time>time</a>, a <a href=#concept-datetime title=concept-datetime>global date and time</a>, 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>
 
@@ -4183,7 +4183,7 @@
   <p>The <dfn id=rules-for-parsing-simple-color-values>rules for parsing simple color values</dfn> are as given
   in the following algorithm. When invoked, the steps must be followed
   in the order given, aborting at the first step that returns a
-  value. This algorithm will either return a <a href=#simple-color>simple color</a>
+  value. This algorithm will return either a <a href=#simple-color>simple color</a>
   or an error.</p>
 
   <ol><li><p>Let <var title="">input</var> be the string being
@@ -4236,8 +4236,8 @@
   complicated manner, using the <dfn id=rules-for-parsing-a-legacy-color-value>rules for parsing a legacy color
   value</dfn>, which are given in the following algorithm. When
   invoked, the steps must be followed in the order given, aborting at
-  the first step that returns a value. This algorithm will either
-  return a <a href=#simple-color>simple color</a> or an error.</p>
+  the first step that returns a value. This algorithm will return
+  either a <a href=#simple-color>simple color</a> or an error.</p>
 
   <ol><li><p>Let <var title="">input</var> be the string being
    parsed.</li>

Modified: source
===================================================================
--- source	2009-09-09 07:40:25 UTC (rev 3773)
+++ source	2009-09-09 09:42:09 UTC (rev 3774)
@@ -1552,7 +1552,7 @@
   <p>The <dfn>rules for parsing non-negative integers</dfn> are as
   given in the following algorithm. When invoked, the steps must be
   followed in the order given, aborting at the first step that returns
-  a value. This algorithm will either return zero, a positive integer,
+  a value. This algorithm will return either zero, a positive integer,
   or an error. Leading spaces are ignored. Trailing spaces and any
   trailing garbage characters are ignored.</p>
 
@@ -1637,7 +1637,7 @@
   non-negative integers</span>, and are as given in the following
   algorithm. When invoked, the steps must be followed in the order
   given, aborting at the first step that returns a value. This
-  algorithm will either return an integer or an error. Leading spaces
+  algorithm will return either an integer or an error. Leading spaces
   are ignored. Trailing spaces and trailing garbage characters are
   ignored.</p>
 
@@ -1795,8 +1795,8 @@
 
   <p>The <dfn>rules for parsing floating point number values</dfn> are
   as given in the following algorithm. This algorithm must be aborted
-  at the first step that returns something. This algorithm will either
-  return a number or an error. Leading spaces are ignored. Trailing
+  at the first step that returns something. This algorithm will return
+  either a number or an error. Leading spaces are ignored. Trailing
   spaces and garbage characters are ignored.</p>
 
   <ol>
@@ -2141,7 +2141,7 @@
   <p>The <dfn>rules for parsing dimension values</dfn> are as given in
   the following algorithm. When invoked, the steps must be followed in
   the order given, aborting at the first step that returns a
-  value. This algorithm will either return a number greater than or
+  value. This algorithm will return either a number greater than or
   equal to 1.0, or an error; if a number is returned, then it is
   further categorized as either a percentage or a length.</p>
 
@@ -2730,7 +2730,7 @@
   <div class="impl">
 
   <p>The rules to <dfn>parse a month string</dfn> are as follows. This
-  will either return a year and month, or nothing. If at any point the
+  will return either a year and month, 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>
 
@@ -2757,7 +2757,7 @@
 
   <p>The rules to <dfn>parse a month component</dfn>, given an <var
   title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return a year and a month, or
+  as follows. This will return either a year and a month, 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>
 
@@ -2828,7 +2828,7 @@
   <div class="impl">
 
   <p>The rules to <dfn>parse a date string</dfn> are as follows. This
-  will either return a date, or nothing. If at any point the algorithm
+  will return either a date, 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>
 
@@ -2858,7 +2858,7 @@
 
   <p>The rules to <dfn>parse a date component</dfn>, given an <var
   title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return a year, a month, and a day, or
+  as follows. This will return either a year, a month, and a day, 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>
 
@@ -2958,7 +2958,7 @@
   <div class="impl">
 
   <p>The rules to <dfn>parse a time string</dfn> are as follows. This
-  will either return a time, or nothing. If at any point the algorithm
+  will return either a time, 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>
 
@@ -2988,7 +2988,7 @@
 
   <p>The rules to <dfn>parse a time component</dfn>, given an <var
   title="">input</var> string and a <var title="">position</var>, are
-  as follows. This will either return an hour, a minute, and a second,
+  as follows. This will return either an hour, a minute, and a second,
   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>
 
@@ -3096,7 +3096,7 @@
   <div class="impl">
 
   <p>The rules to <dfn>parse a local date and time string</dfn> are as
-  follows. This will either return a date and time, or nothing. If at
+  follows. This will return either a date and time, 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>
 
@@ -3272,7 +3272,7 @@
   time zone is UTC.</p>
 
   <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
+  as follows. This will return either a time in UTC, with associated
   time-zone offset 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>
@@ -3332,7 +3332,7 @@
 
   <p>The rules to <dfn>parse a time-zone offset component</dfn>, given
   an <var title="">input</var> string and a <var
-  title="">position</var>, are as follows. This will either return
+  title="">position</var>, are as follows. This will return either
   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>
@@ -3479,7 +3479,7 @@
   <div class="impl">
 
   <p>The rules to <dfn>parse a week string</dfn> are as follows. This
-  will either return a week-year number and week number, or
+  will return either a week-year number and week number, 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>
 
@@ -3583,7 +3583,7 @@
   <p>The rules to <dfn>parse a date or time string</dfn> are as
   follows. The algorithm is invoked with a flag indicating if the
   <i>in attribute</i> variant or the <i>in content</i> variant is to
-  be used. The algorithm will either return a <span
+  be used. The algorithm will return either a <span
   title="concept-date">date</span>, a <span
   title="concept-time">time</span>, a <span
   title="concept-datetime">global date and time</span>, or nothing. If
@@ -3723,7 +3723,7 @@
   <p>The <dfn>rules for parsing simple color values</dfn> are as given
   in the following algorithm. When invoked, the steps must be followed
   in the order given, aborting at the first step that returns a
-  value. This algorithm will either return a <span>simple color</span>
+  value. This algorithm will return either a <span>simple color</span>
   or an error.</p>
 
   <ol>
@@ -3789,8 +3789,8 @@
   complicated manner, using the <dfn>rules for parsing a legacy color
   value</dfn>, which are given in the following algorithm. When
   invoked, the steps must be followed in the order given, aborting at
-  the first step that returns a value. This algorithm will either
-  return a <span>simple color</span> or an error.</p>
+  the first step that returns a value. This algorithm will return
+  either a <span>simple color</span> or an error.</p>
 
   <ol>