W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2009

html5/spec Overview.html,1.2131,1.2132

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 19 Apr 2009 00:32:20 +0000
To: public-html-commits@w3.org
Message-Id: <E1LvKxI-00078F-HK@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv27401

Modified Files:
	Overview.html 
Log Message:
Typos: round 4. (whatwg r2968)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2131
retrieving revision 1.2132
diff -u -d -r1.2131 -r1.2132
--- Overview.html	19 Apr 2009 00:17:34 -0000	1.2131
+++ Overview.html	19 Apr 2009 00:32:17 -0000	1.2132
@@ -1721,7 +1721,7 @@
   scripting language, or any of the DOM and WebAPI specifications
   beyond those described above. However, the language described by
   this specification is biased towards CSS as the styling language,
-  JavsScript as the scripting language, and HTTP as the network
+  JavaScript as the scripting language, and HTTP as the network
   protocol, and several features assume that those languages and
   protocols are in use.</p>
 
@@ -1757,7 +1757,7 @@
   <h4 id=common-conformance-requirements-for-apis-exposed-to-javascript><span class=secno>2.2.3 </span>Common conformance requirements for APIs exposed to
   JavaScript</h4>
 
-  <p class=XXX>This section will eventually be removed in favour of WebIDL.</p>
+  <p class=XXX>This section will eventually be removed in favor of WebIDL.</p>
 
   <p class=XXX>A lot of arrays/lists/<a href=#collections-0 title=collections>collection</a>s
   in this spec assume zero-based indexes but use the term "<var title="">index</var>th" liberally. We should define those to be
@@ -3491,7 +3491,7 @@
 
    <li><p>Return <var title="">result</var>.</p>
 
-  </ol><p>The <dfn id=rules-for-serialising-simple-color-values>rules for serialising simple color values</dfn> given a
+  </ol><p>The <dfn id=rules-for-serializing-simple-color-values>rules for serializing simple color values</dfn> given a
   <a href=#simple-color>simple color</a> are as given in the following
   algorithm:</p>
 
@@ -4184,7 +4184,7 @@
 
     <p>If the <a href=#absolute-url>absolute URL</a> identified by the hyperlink is
     being shown to the user, or if any data derived from that URL is
-    affecting the display, then the <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute should be <a href=#resolve-a-url title="resolve a url">reresolved</a> relative to the element
+    affecting the display, then the <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code> attribute should be <a href=#resolve-a-url title="resolve a url">re-resolved</a> relative to the element
     and the UI updated appropriately.</p>
 
     <p class=example>For example, the CSS <code title=selector-link><a href=#selector-link>:link</a></code>/<code title=selector-visited><a href=#selector-visited>:visited</a></code> pseudo-classes might have
@@ -4193,7 +4193,7 @@
     <p>If the hyperlink has a <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and its <a href=#absolute-url title="absolute URL">absolute URL(s)</a> are being shown to the
     user, then the <code title=attr-hyperlink-ping><a href=#ping>ping</a></code>
     attribute's tokens should be <a href=#resolve-a-url title="resolve a
-    url">reresolved</a> relative to the element and the UI updated
+    url">r-eresolved</a> relative to the element and the UI updated
     appropriately.</p>
 
    </dd>
@@ -4206,7 +4206,7 @@
     <p>If the <a href=#absolute-url>absolute URL</a> identified by the <code title="">cite</code> attribute is being shown to the user, or if
     any data derived from that URL is affecting the display, then the
     <a href=#url>URL</a> should be <a href=#resolve-a-url title="resolve a
-    url">reresolved</a> relative to the element and the UI updated
+    url">re-resolved</a> relative to the element and the UI updated
     appropriately.</p>
 
    </dd>
@@ -5243,7 +5243,7 @@
   encoding is rarely used for publicly-facing Web content.</p>
 
   <p>Support for UTF-32 is not recommended. This encoding is rarely
-  used, and frequently misimplemented.</p>
+  used, and frequently implemented incorrectly.</p>
 
   <p class=note>This specification does not make any attempt to
   support EBCDIC-based encodings and UTF-32 in its algorithms; support
@@ -21291,7 +21291,7 @@
   way to render fragments of documents, rendered using CSS, straight
   to the canvas. This would be provided in preference to a dedicated
   way of doing multiline layout.<h6 id=images><span class=secno>4.8.11.1.10 </span>Images</h6><p>To draw images onto the canvas, the <dfn id=dom-context-2d-drawimage title=dom-context-2d-drawImage><code>drawImage</code></dfn> method
-  can be used.<p>This method can be invoked with three different sets of argments:<ul class=brief><li><code title="">drawImage(<var title="">image</var>, <var title="">dx</var>, <var title="">dy</var>)</code>
+  can be used.<p>This method can be invoked with three different sets of arguments:<ul class=brief><li><code title="">drawImage(<var title="">image</var>, <var title="">dx</var>, <var title="">dy</var>)</code>
    <li><code title="">drawImage(<var title="">image</var>, <var title="">dx</var>, <var title="">dy</var>, <var title="">dw</var>, <var title="">dh</var>)</code>
    <li><code title="">drawImage(<var title="">image</var>, <var title="">sx</var>, <var title="">sy</var>, <var title="">sw</var>, <var title="">sh</var>, <var title="">dx</var>, <var title="">dy</var>, <var title="">dw</var>, <var title="">dh</var>)</code>
   </ul><p>Each of those three can take either an
@@ -23193,16 +23193,16 @@
   an ID of a <code><a href=#the-th-element>th</a></code> element taking part in the same <a href=#concept-table title=concept-table>table</a> as the <code><a href=#the-td-element>td</a></code> or
   <code><a href=#the-th-element>th</a></code> element<span class=impl> (as defined by the
   <a href=#table-model>table model</a>)</span>.<p>A <code><a href=#the-th-element>th</a></code> element with ID <var title="">id</var> is said
-  to be <i>directly targetted</i> by all <code><a href=#the-td-element>td</a></code> and
+  to be <i>directly targeted</i> by all <code><a href=#the-td-element>td</a></code> and
   <code><a href=#the-th-element>th</a></code> elements in the same <a href=#concept-table title=concept-table>table</a> that have <code title=attr-tdth-headers><a href=#attr-tdth-headers>headers</a></code> attributes whose values
   include as one of their tokens the ID <var title="">id</var>. A
   <code><a href=#the-th-element>th</a></code> element <var title="">A</var> is said to be
-  <i>targetted</i> by a <code><a href=#the-th-element>th</a></code> or <code><a href=#the-td-element>td</a></code> element
+  <i>targeted</i> by a <code><a href=#the-th-element>th</a></code> or <code><a href=#the-td-element>td</a></code> element
   <var title="">B</var> if either <var title="">A</var> is <i>directly
-  targetted</i> by <var title="">B</var> or if there exists an element
-  <var title="">C</var> that is itself <i>targetted</i> by the element
+  targeted</i> by <var title="">B</var> or if there exists an element
+  <var title="">C</var> that is itself <i>targeted</i> by the element
   <var title="">B</var> and <var title="">A</var> is <i>directly
-  targetted</i> by <var title="">C</var>.<p>A <code><a href=#the-th-element>th</a></code> element must not be <i>targetted</i> by
+  targeted</i> by <var title="">C</var>.<p>A <code><a href=#the-th-element>th</a></code> element must not be <i>targeted</i> by
   itself.<div class=impl>
 
   <p>The <code title=attr-tdth-colspan><a href=#attr-tdth-colspan>colspan</a></code>, <code title=attr-tdth-rowspan><a href=#attr-tdth-rowspan>rowspan</a></code>, and <code title=attr-tdth-headers><a href=#attr-tdth-headers>headers</a></code> attributes take part in the
@@ -27367,7 +27367,7 @@
   it. User agents must not allow the user to set the <a href=#concept-fe-value title=concept-fe-value>value</a> to a string that is not a
   <a href=#valid-lowercase-simple-color>valid lowercase simple color</a>. If the user agent
   provides a user interface for selecting a color, then the <a href=#concept-fe-value title=concept-fe-value>value</a> must be set to the result of
-  using the <a href=#rules-for-serialising-simple-color-values>rules for serialising simple color values</a> to
+  using the <a href=#rules-for-serializing-simple-color-values>rules for serializing simple color values</a> to
   the user's selection. User agents must not allow the user to set the
   <a href=#concept-fe-value title=concept-fe-value>value</a> to the empty string.</p>
   
@@ -28748,7 +28748,7 @@
   Upload</a> control that consists of a single button that brings
   up a file selection dialog: when the dialog is closed, if that the
   <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>file selection</a>
-  changed as a result, then the user has commited a new <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>file selection</a>.</p>
+  changed as a result, then the user has committed a new <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>file selection</a>.</p>
 
   <p class=example>Another example of a user interface with a commit
   action would be a <a href=#date-state title=attr-input-type-date>Date</a>
@@ -37673,7 +37673,7 @@
   method is waiting.</p>
 
   <p>The <dfn id=dom-confirm title=dom-confirm><code>confirm(<var title="">message</var>)</code></dfn> method, when invoked, must
-  release the <a href=#storage-mutex>storage mutex</a> andshow the given <var title="">message</var> to the user, and ask the user to respond with
+  release the <a href=#storage-mutex>storage mutex</a> and show the given <var title="">message</var> to the user, and ask the user to respond with
   a positive or negative response. The user agent must then
   <a href=#pause>pause</a> as the method waits for the user's response. If
   the user responds positively, the method must return true, and if
@@ -38145,7 +38145,7 @@
   methods could be presented to the user</a> below.</p>
 
   <p>The arguments to the methods have the following meanings and
-  corresponding implementaion requirements:</p>
+  corresponding implementation requirements:</p>
 
   <dl><dt><var title="">protocol</var> (<code title=dom-navigator-registerProtocolHandler><a href=#dom-navigator-registerprotocolhandler>registerProtocolHandler()</a></code> only)</dt>
 
@@ -38217,7 +38217,7 @@
      <p>...and then, much later, while visiting <code title="">http://www.example.net/</code>, clicked on a link such
      as:</p>
 
-     <pre>&lt;a href="chickenk&iuml;wi.soup"&gt;Download our Chicken Kiwi soup!&lt;/a&gt;</pre>
+     <pre>&lt;a href="chickenk&iuml;wi.soup"&gt;Download our Chicken K&iuml;wi soup!&lt;/a&gt;</pre>
 
      <p>...then, assuming this <code>chickenk&iuml;wi.soup</code> file
      was served with the MIME type <code>application/x-soup</code>,
@@ -38504,7 +38504,7 @@
  
     </dl><p class=note>A URL in the list can be flagged with multiple
     different types, and thus an entry can end up being categorized as
-    multiple entries. For example, an entry can be a manfiest entry
+    multiple entries. For example, an entry can be a manifest entry
     and an explicit entry at the same time, if the manifest is listed
     within the manifest.</p>
 
@@ -38556,7 +38556,7 @@
   cache</a>.</p>
 
   <p>A <code>Document</code> initially is not associated with an
-  <a href=#application-cache>application cache</a>, buu can become associated with one
+  <a href=#application-cache>application cache</a>, but can become associated with one
   early during the page load process, when steps <a href=#parser-appcache>in the parser</a> and in the <a href=#navigate title=navigate>navigation</a> sections that cause <a href=#concept-appcache-init title=concept-appcache-init>cache selection</a> to occur.</p>
 
   <p>A <code>SharedWorkerGlobalScope</code> is can be associated with
@@ -42392,7 +42392,7 @@
   <p>When an element is <i>focused</i>, key events received by the
   document must be targeted at that element. There may be no element
   focused; when no element is focused, key events received by the
-  document must be targetted at <a href=#the-body-element-0>the body element</a>.</p>
+  document must be targeted at <a href=#the-body-element-0>the body element</a>.</p>
 
   <p>User agents may track focus for each <a href=#browsing-context>browsing
   context</a> or <code>Document</code> individually, or may support
@@ -45866,7 +45866,7 @@
 
   <ol><li>
 
-    <p>If one of the ports is already entangled, then unentangle it
+    <p>If one of the ports is already entangled, then disentangle it
     and the port that it was entangled with.</p>
 
     <p class=note>If those two previously entangled ports were the
@@ -45903,7 +45903,7 @@
    its initial closed state.</li>
 
    <li><p><a href=#entangle>Entangle</a> the <var title="">remote port</var>
-   and <var title="">new port</var> objects. The <var title="">original port</var> object will be unentangled by this
+   and <var title="">new port</var> objects. The <var title="">original port</var> object will be disentangled by this
    process.</li>
 
    <li><p>Return <var title="">new port</var>. It is the
@@ -46059,7 +46059,7 @@
   <hr><p>The <dfn id=dom-messageport-close title=dom-MessagePort-close><code>close()</code></dfn>
   method, when called on a port <var title="">local port</var> that is
   entangled with another port, must cause the user agents to
-  unentangle the two ports. If the method is called on a port that is
+  disentangle the two ports. If the method is called on a port that is
   not entangled, then the method must do nothing.</p>
 
   <hr><p>The following are the <a href=#event-handler-attributes-0>event handler attributes</a> (and their corresponding <a href=#event-handler-event-type title="event handler event type">event handler event types</a>)
@@ -55730,19 +55730,19 @@
 }
 col[valign=top], thead[valign=top], tbody[valign=top],
 tfoot[valign=top], tr[valign=top], td[valign=top], th[valign=top] {
-  vertial-align: top;
+  vertical-align: top;
 }
 col[valign=middle], thead[valign=middle], tbody[valign=middle],
 tfoot[valign=middle], tr[valign=middle], td[valign=middle], th[valign=middle] {
-  vertial-align: middle;
+  vertical-align: middle;
 }
 col[valign=bottom], thead[valign=bottom], tbody[valign=bottom],
 tfoot[valign=bottom], tr[valign=bottom], td[valign=bottom], th[valign=bottom] {
-  vertial-align: bottom;
+  vertical-align: bottom;
 }
 col[valign=baseline], thead[valign=baseline], tbody[valign=baseline],
 tfoot[valign=baseline], tr[valign=baseline], td[valign=baseline], th[valign=baseline] {
-  vertial-align: baseline;
+  vertical-align: baseline;
 }</pre>
 
   <p>The <code><a href=#center>center</a></code> element, the <code><a href=#the-caption-element>caption</a></code> element
@@ -56410,7 +56410,7 @@
   when its <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in
   the <a href=#image-button-state title=attr-input-type-image>Image Button</a> state
   does not <a href=#represents title=represents>represent</a> an image, but the
-  element already has instrinsic dimensions (e.g. from the
+  element already has intrinsic dimensions (e.g. from the
   <a href=#dimension-attributes>dimension attributes</a> or CSS rules), and either the user
   agent has reason to believe that the image will become
   <i>available</i> and be rendered in due course or the
@@ -56611,8 +56611,8 @@
   <p>The CSS snippets below set the 'binding' property to a
   user-agent-defined value, represented below by keywords like <code title=""><i title="">bb</i></code>. The rules then described for
   these bindings are only expected to apply if the element's 'binding'
-  property has not been overriden (e.g. by the author) to have another
-  value.</p>
+  property has not been overridden (e.g. by the author) to have
+  another value.</p>
 
   <p>Exactly how the bindings are implemented is not specified by this
   specification. User agents are encouraged to make their bindings set
@@ -57791,6 +57791,7 @@
   Andy Heydon,
   Anne van Kesteren,
   Anthony Boyd,
+  Anthony Bryan,
   Anthony Hickson,
   Anthony Ricaud,
   Antti Koivisto,
@@ -57848,6 +57849,7 @@
   Daniel Bratell,
   Daniel Brooks,
   Daniel Brumbaugh Keeney,
+  Daniel Davis,
   Daniel Glazman,
   Daniel Peng,
   Daniel Schattenkirchner,
Received on Sunday, 19 April 2009 00:32:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 19 April 2009 00:32:29 GMT