[e] (0) Typos, thanks to foolip!

Affected topics: DOM APIs, HTML, Offline Web Applications, Video Text Tracks, Video and Audio

git-svn-id: http://svn.whatwg.org/webapps@7465 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -20332,7 +20332,7 @@ <h4 id=the-blockquote-element><span class=secno>4.5.4 </span>The <dfn><code>bloc
 &lt;p&gt;He continued with a number of similar points, ending with:&lt;/p&gt;
 &lt;blockquote&gt;Finally, one should be prepared for the threat 
 of breakdown in negotiations at any given moment and not 
-be cowed by the possiblity.&lt;/blockquote&gt;
+be cowed by the possibility.&lt;/blockquote&gt;
 &lt;p&gt;We shall now discuss these points...</pre>
 
   </div>
@@ -33722,7 +33722,7 @@ <h6 id=text-track-model><span class=secno>4.8.10.12.1 </span>Text track model</h
     <p class=example>For example, a traditional TV station broadcast
     streamed on the Web and augmented with Web-specific interactive
     features could include text tracks with metadata for ad
-    targetting, trivia game data during game shows, player states
+    targeting, trivia game data during game shows, player states
     during sports games, recipe information during food programs, and
     so forth. As each program starts and ends, new tracks might be
     added or removed from the stream, and as each one is added, the
@@ -35878,7 +35878,7 @@ <h5 id=user-interface><span class=secno>4.8.10.13 </span>User interface</h5>
 
   <div class=example>
 
-   <p>This video (an advertisment) autoplays, but to avoid annoying
+   <p>This video (an advertisement) autoplays, but to avoid annoying
    users, it does so without sound, and allows the user to turn the
    sound on.</p>
 
@@ -46784,7 +46784,7 @@ <h4 id=the-label-element><span class=secno>4.10.6 </span>The <dfn><code>label</c
   behavior, in particular what its <a href=#activation-behavior>activation behavior</a>
   might be, if anything, should match the platform's label behavior.
   The <a href=#activation-behavior>activation behavior</a> of a <code><a href=#the-label-element>label</a></code> element
-  for events targetted at <a href=#interactive-content>interactive content</a> descendants
+  for events targeted at <a href=#interactive-content>interactive content</a> descendants
   of a <code><a href=#the-label-element>label</a></code> element, and any descendants of those
   <a href=#interactive-content>interactive content</a> descendants, must be to do
   nothing.</p>
@@ -50505,7 +50505,7 @@ <h6 id="range-state-(type=range)"><span class=secno>4.10.7.1.14 </span><dfn titl
 
    <p><img alt="A vertical slider control whose primary color is black and whose background color is beige, with the slider having five tick marks, one long one at each extremity, and three short ones clustered around the midpoint." height=75 src=http://images.whatwg.org/sample-range.png width=49><p>Note how the UA determined the orientation of the control from
    the ratio of the style-sheet-specified height and width properties.
-   The colors were similiarly derived from the style sheet. The tick
+   The colors were similarly derived from the style sheet. The tick
    marks, however, were derived from the markup. In particular, the
    <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute has not
    affected the placement of tick marks, the UA deciding to only use
@@ -58216,7 +58216,7 @@ <h5 id=form-submission-algorithm><span class=secno>4.10.22.3 </span>Form submiss
     elements, this newline normalization is already performed during
     the conversion of the control's <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a> into the
     control's <a href=#concept-fe-value title=concept-fe-value>value</a> (which also
-    performs any necesary line wrapping). In the case of
+    performs any necessary line wrapping). In the case of
     <code><a href=#the-input-element>input</a></code> elements <code title=attr-input-type><a href=#attr-input-type>type</a></code> attributes in the <a href="#file-upload-state-(type=file)" title=attr-input-type-file>File Upload</a> state, the value
     is not normalized.</p>
 
@@ -61064,7 +61064,7 @@ <h4 id=downloading-resources><span class=secno>4.12.4 </span>Downloading resourc
     alter <var title="">filename</var> to add a known-safe <a href=#concept-extension title=concept-extension>extension</a> (e.g. "<code title="">.txt</code>").</p>
 
     <p class=note>This last step would make it impossible to
-    download executables, which might not be desireable. As always,
+    download executables, which might not be desirable. As always,
     implementors are forced to balance security and usability in this
     matter.</p>
 
@@ -71972,7 +71972,7 @@ <h4 id=unloading-documents><span class=secno>6.6.11 </span>Unloading documents</
    <a href=#ignore-opens-during-unload-counter>ignore-opens-during-unload counter</a> by one.</li>
 
    <li><p>If the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
-   flag is false, then jump to the step labled <i>unload event</i>
+   flag is false, then jump to the step labeled <i>unload event</i>
    below (i.e. skip firing the <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> even and don't rerun the
    <a href=#unloading-document-visibility-change-steps>unloading document visibility change steps</a>).</li>
 
@@ -72186,7 +72186,7 @@ <h3 id=offline><span class=secno>6.7 </span>Offline Web applications</h3>
        that allows you to "activate" a particular manifest name for a
        given appcache.
 
-       So each appcache group would be futher subdivided into named
+       So each appcache group would be further subdivided into named
        subgroups, and for a given manifest URL with such a group of
        subgroups, one subgroup would be the default one at a time. The
        inactive ones would just lie dormant, but and the active ones
@@ -78090,7 +78090,7 @@ <h3 id=inert-subtrees><span class=secno>8.2 </span>Inert subtrees</h3>
   <p>A subtree of a <code><a href=#document>Document</a></code> can be marked as
   <dfn id=inert>inert</dfn>. When a node or one of its ancestors is
   <a href=#inert>inert</a>, then the user agent must act as if the element
-  was absent for the purposes of targetting user interaction events,
+  was absent for the purposes of targeting user interaction events,
   may ignore the node for the purposes of text search user interfaces
   (commonly known as "find in page"), and may prevent the user from
   selecting text in that node. User agents should allow the user to
@@ -80514,7 +80514,7 @@ <h4 id=drag-and-drop-processing-model><span class=secno>8.7.5 </span>Drag-and-dr
   must run the following steps. User agents must act as if these steps
   were run even if the drag actually started in another document or
   application and the user agent was not aware that the drag was
-  occuring until it intersected with a document under the user agent's
+  occurring until it intersected with a document under the user agent's
   purview.</p>
 
   <ol><li>
@@ -86688,12 +86688,12 @@ <h4 id=message-ports><span class=secno>10.5.3 </span>Message ports</h4>
     <ol><li>
 
       <p>Let <var title="">new owner</var> be the owner of <var title="">target port</var>, if there is a <var title="">target
-      port</var>, or else some arbitrary owner. (This <var title="">new owner</var> is used when transfering objects below.
+      port</var>, or else some arbitrary owner. (This <var title="">new owner</var> is used when transferring objects below.
       If there is no <var title="">target port</var>, the
       <code><a href=#transferable>Transferable</a></code> objects given in the second argument,
       if any, are still <a href=#transfer-a-transferable-object title="transfer a Transferable
-      object">transfered</a>, but since they are then discarded, it
-      doesn't matter where they are transfered to.)</p>
+      object">transferred</a>, but since they are then discarded, it
+      doesn't matter where they are transferred to.)</p>
 
      </li>
 

index

@@ -20332,7 +20332,7 @@ be conceded to have merits.</blockquote>
 <p>He continued with a number of similar points, ending with:</p>
 <blockquote>Finally, one should be prepared for the threat 
 of breakdown in negotiations at any given moment and not 
-be cowed by the possiblity.</blockquote>
+be cowed by the possibility.</blockquote>
 &lt;p&gt;We shall now discuss these points...</pre>
 
   </div>
@@ -33722,7 +33722,7 @@ interface <dfn id=mediacontroller>MediaController</dfn> : <a href=#eventtarget>E
     <p class=example>For example, a traditional TV station broadcast
     streamed on the Web and augmented with Web-specific interactive
     features could include text tracks with metadata for ad
-    targetting, trivia game data during game shows, player states
+    targeting, trivia game data during game shows, player states
     during sports games, recipe information during food programs, and
     so forth. As each program starts and ends, new tracks might be
     added or removed from the stream, and as each one is added, the
@@ -35878,7 +35878,7 @@ The General Relativistic Field Equations</pre>
 
   <div class=example>
 
-   <p>This video (an advertisment) autoplays, but to avoid annoying
+   <p>This video (an advertisement) autoplays, but to avoid annoying
    users, it does so without sound, and allows the user to turn the
    sound on.</p>
 
@@ -46784,7 +46784,7 @@ interface <dfn id=htmlformelement>HTMLFormElement</dfn> : <a href=#htmlelement>H
   behavior, in particular what its <a href=#activation-behavior>activation behavior</a>
   might be, if anything, should match the platform's label behavior.
   The <a href=#activation-behavior>activation behavior</a> of a <code><a href=#the-label-element>label</a></code> element
-  for events targetted at <a href=#interactive-content>interactive content</a> descendants
+  for events targeted at <a href=#interactive-content>interactive content</a> descendants
   of a <code><a href=#the-label-element>label</a></code> element, and any descendants of those
   <a href=#interactive-content>interactive content</a> descendants, must be to do
   nothing.</p>
@@ -50505,7 +50505,7 @@ interface <dfn id=htmlformelement>HTMLFormElement</dfn> : <a href=#htmlelement>H
 
    <p><img alt="A vertical slider control whose primary color is black and whose background color is beige, with the slider having five tick marks, one long one at each extremity, and three short ones clustered around the midpoint." height=75 src=http://images.whatwg.org/sample-range.png width=49><p>Note how the UA determined the orientation of the control from
    the ratio of the style-sheet-specified height and width properties.
-   The colors were similiarly derived from the style sheet. The tick
+   The colors were similarly derived from the style sheet. The tick
    marks, however, were derived from the markup. In particular, the
    <code title=attr-input-step><a href=#attr-input-step>step</a></code> attribute has not
    affected the placement of tick marks, the UA deciding to only use
@@ -58216,7 +58216,7 @@ fur
     elements, this newline normalization is already performed during
     the conversion of the control's <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a> into the
     control's <a href=#concept-fe-value title=concept-fe-value>value</a> (which also
-    performs any necesary line wrapping). In the case of
+    performs any necessary line wrapping). In the case of
     <code><a href=#the-input-element>input</a></code> elements <code title=attr-input-type><a href=#attr-input-type>type</a></code> attributes in the <a href="#file-upload-state-(type=file)" title=attr-input-type-file>File Upload</a> state, the value
     is not normalized.</p>
 
@@ -61064,7 +61064,7 @@ fur
     alter <var title="">filename</var> to add a known-safe <a href=#concept-extension title=concept-extension>extension</a> (e.g. "<code title="">.txt</code>").</p>
 
     <p class=note>This last step would make it impossible to
-    download executables, which might not be desireable. As always,
+    download executables, which might not be desirable. As always,
     implementors are forced to balance security and usability in this
     matter.</p>
 
@@ -71972,7 +71972,7 @@ dictionary <dfn id=pagetransitioneventinit>PageTransitionEventInit</dfn> : <a hr
    <a href=#ignore-opens-during-unload-counter>ignore-opens-during-unload counter</a> by one.</li>
 
    <li><p>If the <code><a href=#document>Document</a></code>'s <a href=#page-showing>page showing</a>
-   flag is false, then jump to the step labled <i>unload event</i>
+   flag is false, then jump to the step labeled <i>unload event</i>
    below (i.e. skip firing the <code title=event-pagehide><a href=#event-pagehide>pagehide</a></code> even and don't rerun the
    <a href=#unloading-document-visibility-change-steps>unloading document visibility change steps</a>).</li>
 
@@ -72186,7 +72186,7 @@ dictionary <dfn id=pagetransitioneventinit>PageTransitionEventInit</dfn> : <a hr
        that allows you to "activate" a particular manifest name for a
        given appcache.
 
-       So each appcache group would be futher subdivided into named
+       So each appcache group would be further subdivided into named
        subgroups, and for a given manifest URL with such a group of
        subgroups, one subgroup would be the default one at a time. The
        inactive ones would just lie dormant, but and the active ones
@@ -78090,7 +78090,7 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
   <p>A subtree of a <code><a href=#document>Document</a></code> can be marked as
   <dfn id=inert>inert</dfn>. When a node or one of its ancestors is
   <a href=#inert>inert</a>, then the user agent must act as if the element
-  was absent for the purposes of targetting user interaction events,
+  was absent for the purposes of targeting user interaction events,
   may ignore the node for the purposes of text search user interfaces
   (commonly known as "find in page"), and may prevent the user from
   selecting text in that node. User agents should allow the user to
@@ -80514,7 +80514,7 @@ dictionary <dfn id=drageventinit>DragEventInit</dfn> : <a href=#mouseeventinit>M
   must run the following steps. User agents must act as if these steps
   were run even if the drag actually started in another document or
   application and the user agent was not aware that the drag was
-  occuring until it intersected with a document under the user agent's
+  occurring until it intersected with a document under the user agent's
   purview.</p>
 
   <ol><li>
@@ -86688,12 +86688,12 @@ interface <dfn id=messagechannel>MessageChannel</dfn> {
     <ol><li>
 
       <p>Let <var title="">new owner</var> be the owner of <var title="">target port</var>, if there is a <var title="">target
-      port</var>, or else some arbitrary owner. (This <var title="">new owner</var> is used when transfering objects below.
+      port</var>, or else some arbitrary owner. (This <var title="">new owner</var> is used when transferring objects below.
       If there is no <var title="">target port</var>, the
       <code><a href=#transferable>Transferable</a></code> objects given in the second argument,
       if any, are still <a href=#transfer-a-transferable-object title="transfer a Transferable
-      object">transfered</a>, but since they are then discarded, it
-      doesn't matter where they are transfered to.)</p>
+      object">transferred</a>, but since they are then discarded, it
+      doesn't matter where they are transferred to.)</p>
 
      </li>