Reference conventions from HTML. And some minor cleanup. https://www.…

…w3.org/Bugs/Public/show_bug.cgi?id=16312

Overview.html

@@ -7,7 +7,7 @@
 
 <p><a class="logo" href="//www.whatwg.org/"><img alt="WHATWG" height="100" src="//resources.whatwg.org/logo-xhr.svg" width="100"></a>
 <h1 class="head" id="xmlhttprequest-ls">XMLHttpRequest</h1>
-<h2 class="no-num no-toc" id="living-standard-—-last-updated-5-november-2013">Living Standard — Last Updated 5 November 2013</h2>
+<h2 class="no-num no-toc" id="living-standard-—-last-updated-11-november-2013">Living Standard — Last Updated 11 November 2013</h2>
 
 <dl>
  <dt>This Version:
@@ -36,7 +36,7 @@ <h2 class="no-num no-toc" id="living-standard-—-last-updated-5-november-2013">
 <p class="copyright"><a href="http://creativecommons.org/publicdomain/zero/1.0/" rel="license"><img alt="CC0" src="http://i.creativecommons.org/p/zero/1.0/80x15.png"></a>
 To the extent possible under law, the editor has waived all copyright and
 related or neighboring rights to this work. In addition, as of
-5 November 2013, the editor has made this specification available
+11 November 2013, the editor has made this specification available
 under the
 <a href="http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0" rel="license">Open Web Foundation Agreement Version 1.0</a>,
 which is available at
@@ -48,8 +48,8 @@ <h2 class="no-num no-toc" id="living-standard-—-last-updated-5-november-2013">
 
 <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
 
-<p>The XMLHttpRequest specification defines an API that provides scripted
-client functionality for transferring data between a client and a server.
+<p>XMLHttpRequest defines an API that provides scripted client functionality for
+transferring data between a client and a server.
 
 
 
@@ -215,7 +215,7 @@ <h3 id="extensibility"><span class="secno">2.1 </span>Extensibility</h3>
 
 <h2 id="terminology"><span class="secno">3 </span>Terminology</h2>
 
-<p>This specification heavily borrows terminology, from DOM,
+<p>This specification uses terminology, cross-linked throughout, from DOM,
 DOM Parsing and Serialization, Encoding, Fetch, File API, HTML, HTTP, Typed Array, URL,
 Web IDL, and XML.
 
@@ -231,6 +231,8 @@ <h2 id="terminology"><span class="secno">3 </span>Terminology</h2>
 <a href="#refsWEBIDL">[WEBIDL]</a>
 <a href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a>
 
+<p>It uses the typographic conventions from HTML. <a href="#refsHTTP">[HTTP]</a>
+
 <p>The term <dfn id="user-credentials">user credentials</dfn> for the purposes of this
 specification means cookies, HTTP authentication, and client-side SSL
 certificates. Specifically it does not refer to proxy authentication or the
@@ -1384,7 +1386,7 @@ <h4 id="the-getresponseheader()-method"><span class="secno">4.6.3 </span>The <co
  <li><p>Return null.
 </ol>
 
-<p class="note">The Fetch specification filters
+<p class="note">The Fetch Standard filters
 <a class="external" href="http://fetch.spec.whatwg.org/#concept-response-headers" title="concept-response-headers">headers</a> exposed by
 <code title="dom-XMLHttpRequest-getResponseHeader"><a href="#dom-xmlhttprequest-getresponseheader">getResponseHeader()</a></code>.
 <a href="#refsFETCH">[FETCH]</a>
@@ -1422,7 +1424,7 @@ <h4 id="the-getallresponseheaders()-method"><span class="secno">4.6.4 </span>The
 <a class="external" href="http://fetch.spec.whatwg.org/#concept-header" title="concept-header">header</a> separated by a 0x3A 0x20
 byte pair.
 
-<p class="note">The Fetch specification filters
+<p class="note">The Fetch Standard filters
 <a class="external" href="http://fetch.spec.whatwg.org/#concept-response-headers" title="concept-response-headers">headers</a> exposed by
 <code title="dom-XMLHttpRequest-getAllResponseHeaders"><a href="#dom-xmlhttprequest-getallresponseheaders">getAllResponseHeaders()</a></code>.
 <a href="#refsFETCH">[FETCH]</a>
@@ -1571,7 +1573,7 @@ <h4 id="response-entity-body-0"><span class="secno">4.6.5 </span>Response entity
    <li><p>Let <var title="">document</var> be a
    <a class="external" href="http://dom.spec.whatwg.org/#concept-document" title="concept-document">document</a> that
    represents the result parsing <a href="#response-entity-body">response entity body</a> following the rules set
-   forth in the HTML specification for an HTML parser with scripting disabled and
+   forth in the HTML Standard for an HTML parser with scripting disabled and
    <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#a-known-definite-encoding">a known definite encoding</a> <var>charset</var>.
    <a href="#refsHTML">[HTML]</a>
 

Overview.src.html

@@ -51,8 +51,8 @@ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated [DATE: 3 August 2
 
 <h2 class="no-num no-toc" id="specabstract">Abstract</h2>
 
-<p>The XMLHttpRequest specification defines an API that provides scripted
-client functionality for transferring data between a client and a server.
+<p>XMLHttpRequest defines an API that provides scripted client functionality for
+transferring data between a client and a server.
 
 
 
@@ -170,7 +170,7 @@ <h3 id="extensibility">Extensibility</h3>
 
 <h2 id="terminology">Terminology</h2>
 
-<p>This specification heavily borrows terminology, from DOM,
+<p>This specification uses terminology, cross-linked throughout, from DOM,
 DOM Parsing and Serialization, Encoding, Fetch, File API, HTML, HTTP, Typed Array, URL,
 Web IDL, and XML.
 
@@ -186,6 +186,8 @@ <h2 id="terminology">Terminology</h2>
 <span data-anolis-ref>WEBIDL</span>
 <span data-anolis-ref>XML</span> <span data-anolis-ref>XMLNS</span>
 
+<p>It uses the typographic conventions from HTML. <span data-anolis-ref>HTTP</span>
+
 <p>The term <dfn>user credentials</dfn> for the purposes of this
 specification means cookies, HTTP authentication, and client-side SSL
 certificates. Specifically it does not refer to proxy authentication or the
@@ -1339,7 +1341,7 @@ <h4>The <code title>getResponseHeader()</code> method</h4>
  <li><p>Return null.
 </ol>
 
-<p class=note>The Fetch specification filters
+<p class=note>The Fetch Standard filters
 <span data-anolis-spec=fetch title=concept-response-headers>headers</span> exposed by
 <code title="dom-XMLHttpRequest-getResponseHeader">getResponseHeader()</code>.
 <span data-anolis-ref>FETCH</span>
@@ -1377,7 +1379,7 @@ <h4>The <code title>getAllResponseHeaders()</code> method</h4>
 <span data-anolis-spec=fetch title=concept-header>header</span> separated by a 0x3A 0x20
 byte pair.
 
-<p class=note>The Fetch specification filters
+<p class=note>The Fetch Standard filters
 <span data-anolis-spec=fetch title=concept-response-headers>headers</span> exposed by
 <code title="dom-XMLHttpRequest-getAllResponseHeaders">getAllResponseHeaders()</code>.
 <span data-anolis-ref>FETCH</span>
@@ -1526,7 +1528,7 @@ <h4>Response entity body</h4>
    <li><p>Let <var title>document</var> be a
    <span data-anolis-spec=dom title=concept-document>document</span> that
    represents the result parsing <span>response entity body</span> following the rules set
-   forth in the HTML specification for an HTML parser with scripting disabled and
+   forth in the HTML Standard for an HTML parser with scripting disabled and
    <span data-anolis-spec=html>a known definite encoding</span> <var>charset</var>.
    <span data-anolis-ref>HTML</span>