[css-2015] Swap order of sections

Author: fantasai

css-2015/Overview.bs

@@ -419,6 +419,41 @@ Requirements for Responsible Implementation of CSS</h2>
 			Note: Vendors should consult the WG explicitly and not make assumptions on this point,
 			as a pre-CR spec that hasn't changed in awhile is usually more out-of-date than stable.
 
+
+		<h4 id="proprietary">
+		Proprietary and Non-standardized Features</h4>
+
+			Issue: Rewritten as open vs. closed systems instead of Web vs. non-Web, per szilles' request.
+
+			A CSS feature is a <dfn>proprietary extension</dfn> if it is meant for use
+			in a closed environment accessible only to a single vendor's user agent(s).
+			A UA should support such <a>proprietary extensions</a>
+			only through a vendor-prefixed syntax
+			and not expose them to open (multi-UA) environments such as the World Wide Web.
+
+			<details class=why>
+				<summary>Why?</summary>
+				The prefixing requirement allows shipping specialized features in closed environments
+				without conflicting with future additions to standard CSS.
+				The restriction on exposure to open systems is to prevent
+				accidentally causing the public CSS environment
+				to depend on an unstandardized <a>proprietary extensions</a>.
+			</details>
+
+			<div class="example">
+				For example,
+				Firefox's XUL-based UI, Apple's iTunes UI, and Microsoft's Universal Windows Platform app
+				use extensions to CSS implemented by their respective UAs.
+				So long as these UAs do not allow Web content to access these features,
+				they do not provide an opportunity for such content
+				to become dependent on their <a>proprietary extensions</a>.
+			</div>
+
+			Even if a feature is intended to eventually be used in the Web,
+			if it hasn't yet been standardized
+			it should still not be exposed to the Web.
+
+
 		<h4 id="de-facto">
 		Market Pressure and De Facto Standards</h4>
 
@@ -427,7 +462,7 @@ Requirements for Responsible Implementation of CSS</h2>
 			If a feature is <a>unstable</a>, yet
 
 			*	at least three UAs implement the feature
-				(or a browser has broken the other rules and shipped for broad use
+				(or a UA has broken the other rules and shipped for broad use
 				an <a>unstable</a> or otherwise non-standard feature in a production release),
 			*	<em>and</em> the implementations have rough interoperability,
 			*	<em>and</em> the CSS Working Group has recorded consensus
@@ -476,39 +511,6 @@ Requirements for Responsible Implementation of CSS</h2>
 			<ins>and avoid other obstacles (e.g., platform dependency, licensing restrictions)
 			to their competitors shipping the feature.</ins>
 
-		<h4 id="proprietary">
-		Proprietary and Non-standardized Features</h4>
-
-			Issue: Rewritten as open vs. closed systems instead of Web vs. non-Web, per szilles' request.
-
-			A CSS feature is a <dfn>proprietary extension</dfn> if it is meant for use
-			in a closed environment accessible only to a single vendor's user agent(s).
-			A UA should support such <a>proprietary extensions</a>
-			only through a vendor-prefixed syntax
-			and not expose them to open (multi-UA) environments such as the World Wide Web.
-
-			<details class=why>
-				<summary>Why?</summary>
-				The prefixing requirement allows shipping specialized features in closed environments
-				without conflicting with future additions to standard CSS.
-				The restriction on exposure to open systems is to prevent
-				accidentally causing the public CSS environment
-				to depend on an unstandardized <a>proprietary extensions</a>.
-			</details>
-
-			<div class="example">
-				For example,
-				Firefox's XUL-based UI, Apple's iTunes UI, and Microsoft's Universal Windows Platform app
-				use extensions to CSS implemented by their respective UAs.
-				So long as these UAs do not allow Web content to access these features,
-				they do not provide an opportunity for such content
-				to become dependent on their <a>proprietary extensions</a>.
-			</div>
-
-			Even if a feature is intended to eventually be used in the Web,
-			if it hasn't yet been standardized
-			it should still not be exposed to the Web.
-
 
 <h3 id="testing">Implementations of CR-level Features</h3>