[html5] r8459 - [e] (0) Typo in history section Fixing https://www.w3.org/Bugs/Public/show_bug.c [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2014-02-04 11:56:30 -0800 (Tue, 04 Feb 2014)
New Revision: 8459

Modified:
   complete.html
   index
   source
Log:
[e] (0) Typo in history section
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24488
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2014-02-04 19:37:51 UTC (rev 8458)
+++ complete.html	2014-02-04 19:56:30 UTC (rev 8459)
@@ -66973,7 +66973,7 @@
 
   <p class=note>Since each <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> might have a
   different <a href=#event-loop>event loop</a>, the actual state of the <a href=#joint-session-history>joint session history</a> can
-  be someone nebulous. For example, two sibling <code><a href=#the-iframe-element>iframe</a></code> elements could both <a href=#traverse-the-history title="traverse the history">traverse</a> from one unique origin to another at the same time,
+  be somewhat nebulous. For example, two sibling <code><a href=#the-iframe-element>iframe</a></code> elements could both <a href=#traverse-the-history title="traverse the history">traverse</a> from one unique origin to another at the same time,
   so their precise order might not be well-defined; similarly, since they might only find out about
   each other later, they might disagree about the length of the <a href=#joint-session-history>joint session
   history</a>.</p>

Modified: index
===================================================================
--- index	2014-02-04 19:37:51 UTC (rev 8458)
+++ index	2014-02-04 19:56:30 UTC (rev 8459)
@@ -66973,7 +66973,7 @@
 
   <p class=note>Since each <code><a href=#document>Document</a></code> in a <a href=#browsing-context>browsing context</a> might have a
   different <a href=#event-loop>event loop</a>, the actual state of the <a href=#joint-session-history>joint session history</a> can
-  be someone nebulous. For example, two sibling <code><a href=#the-iframe-element>iframe</a></code> elements could both <a href=#traverse-the-history title="traverse the history">traverse</a> from one unique origin to another at the same time,
+  be somewhat nebulous. For example, two sibling <code><a href=#the-iframe-element>iframe</a></code> elements could both <a href=#traverse-the-history title="traverse the history">traverse</a> from one unique origin to another at the same time,
   so their precise order might not be well-defined; similarly, since they might only find out about
   each other later, they might disagree about the length of the <a href=#joint-session-history>joint session
   history</a>.</p>

Modified: source
===================================================================
--- source	2014-02-04 19:37:51 UTC (rev 8458)
+++ source	2014-02-04 19:56:30 UTC (rev 8459)
@@ -74632,7 +74632,7 @@
 
   <p class="note">Since each <code>Document</code> in a <span>browsing context</span> might have a
   different <span>event loop</span>, the actual state of the <span>joint session history</span> can
-  be someone nebulous. For example, two sibling <code>iframe</code> elements could both <span
+  be somewhat nebulous. For example, two sibling <code>iframe</code> elements could both <span
   data-x="traverse the history">traverse</span> from one unique origin to another at the same time,
   so their precise order might not be well-defined; similarly, since they might only find out about
   each other later, they might disagree about the length of the <span>joint session