"standards mode" => "no-quirks mode"

Align terminology with the relevant portion of the DOM spec
https://dom.spec.whatwg.org/#concept-document-no-quirks

Overview.src.html

@@ -93,7 +93,7 @@ <h2>Introduction</h2>
 
 <h3>History</h3>
 
-<p>Browsers have several rendering modes to render HTML documents. The reason for this is basically a historical accident. The CSS specification was incompatible with the behavior of existing browsers which existing Web content relied on. In order to comply with the specification while not breaking existing content, browsers introduced a new rendering mode (standards mode). Some browsers still had the shrink-wrapping behavior for images in table cells in their standards mode, and sites started relying on that, so browsers that implemented the specification's behavior introduced a third mode (limited-quirks mode). In hindsight, it would have been better to make the default CSS behavior be compatible with what the existing content relied on and providing opt-ins to different behavior. The different modes have since gained a few differences outside of CSS.
+<p>Browsers have several rendering modes to render HTML documents. The reason for this is basically a historical accident. The CSS specification was incompatible with the behavior of existing browsers which existing Web content relied on. In order to comply with the specification while not breaking existing content, browsers introduced a new rendering mode (no-quirks mode). Some browsers still had the shrink-wrapping behavior for images in table cells in their no-quirks mode, and sites started relying on that, so browsers that implemented the specification's behavior introduced a third mode (limited-quirks mode). In hindsight, it would have been better to make the default CSS behavior be compatible with what the existing content relied on and providing opt-ins to different behavior. The different modes have since gained a few differences outside of CSS.
 
 <h3>Goals</h3>
 
@@ -511,9 +511,9 @@ <h3>The unitless length quirk</h3>
 ^C
 
 I appended a ";" after each line, removed all " and ' (which shouldn't affect the font-size thing)
-and put the whole thing in a ruleset and loaded it in a quirks mode doc vs a standards mode doc in
+and put the whole thing in a ruleset and loaded it in a quirks mode doc vs a no-quirks mode doc in
 Firefox to see what was logged to the error console. There were 120465 lines, supposedly 'font'
-declarations. 157+4+6+1+1+1 errors in the console in both quirks mode and standards mode. This means
+declarations. 157+4+6+1+1+1 errors in the console in both quirks mode and no-quirks mode. This means
 none of them had unitless font-size. Most common error seemed to be to omit the font-size and/or
 font-family. This may need more research, but maybe we don't need this quirk for 'font'.
 
@@ -742,7 +742,7 @@ <h2>Quirks that maybe can be removed from implementations</h2>
 <dd><p>Opera, WebKit and IE9 (except in compat view quirks mode) don't support this quirk.</dd>
 
 <dt>The empty-cells property defaults to hide in quirks mode but show (according to CSS2 errata) in strict mode (see  bug 33244 ) (though the correct fix would be to specify it on the HTML TABLE element in quirk.css).</dt>
-<dd><p>WebKit and IE9 (except in compat view quirks and standards modes) do not support this quirk.</dd>
+<dd><p>WebKit and IE9 (except in compat view quirks and no-quirks modes) do not support this quirk.</dd>
 
 <dt>In quirks mode, the CSS parser allows {} around the contents of style attributes ( bug 99554 )</dt>
 <dd><p>WebKit and IE9 (except in compat view quirks mode) don't support this quirk. Its usage in the wild is on the same order as the "space before unit" quirk<!- - see unitless length section - ->, which Firefox doesn't support, and which Opera has dropped support for.</dd>