w3c
diff --git a/‎css-cascade/Overview.bs‎
Lines changed: 19 additions & 13 deletions b/‎css-cascade/Overview.bs‎
Lines changed: 19 additions & 13 deletions
@@ -43,7 +43,7 @@ Introduction</h2>
 Module Interactions</h3>
 
 	<p>This module replaces and extends
-	the rules for assigning property values, aascading, and inheritance defined in [[!CSS21]] chapter 6.
+	the rules for assigning property values, cascading, and inheritance defined in [[!CSS21]] chapter 6.
 
 	<p>Other CSS modules may expand the definitions of some of the syntax and features defined here.
 	For example, the Media Queries Level 4 specification,
@@ -70,17 +70,10 @@ Importing Style Sheets: the ''@import'' rule</h2>
 
 	<pre class='prod'>@import [ <<url>> | <<string>> ] [ supports( <<supports-condition>> ) ]? <<media-query-list>>? ;</pre>
 
-	Where the <<url>> or <<string>> gives the URL of the style sheet to be imported,
+	where the <<url>> or <<string>> gives the URL of the style sheet to be imported,
 	and the optional <<supports-condition>> and <<media-query-list>>
 	(collectively, the <dfn>import conditions</dfn>)
 	state the conditions under which it applies.
-	A <dfn><<media-query>></dfn> corresponds to the <code>media_query_list</code> production and is interpreted as a <a>media query</a>,
-	and a <dfn><<supports-condition>></dfn> corresponds to either a <code>supports_condition</code> production
-	or a <code>declaration</code> production interpreted as a <code>supports_declaration_condition</code> production
-	and is interpreted as an ''@supports'' condition.
-
-	Issue: Feedback on the the <css>supports()</css> syntax is hereby solicited,
-	since none so far has been received.
 
 	If a <<string>> is provided,
 	it must be interpreted as a <<url>> with the same value.
@@ -96,13 +89,12 @@ Importing Style Sheets: the ''@import'' rule</h2>
 		</pre>
 	</div>
 
+<h3 id=conditional-import>
+Conditional ''@import'' Rules</h3>
+
 	The <a>import conditions</a> allow the import to be media&ndash; or feature-support&ndash;dependent.
 	In the absence of any <a>import conditions</a>, the import is unconditional.
 	(Specifying ''@media/all'' for the <<media-query-list>> has the same effect.)
-
-	The evaluation and full syntax of the <a>import conditions</a>
-	are defined by the <a href="http://www.w3.org/TR/css3-mediaqueries/">Media Queries</a> [[!MEDIAQ]]
-	and <a href="http://www.w3.org/TR/css-conditional/">CSS Conditional Rules</a> [[!CSS3-CONDITIONAL]] specifications.
 	If the <a>import conditions</a> do not match,
 	the rules in the imported stylesheet do not apply,
 	exactly as if the imported stylesheet were wrapped in ''@media'' and/or ''@supports'' blocks with the given conditions.
@@ -136,6 +128,20 @@ Importing Style Sheets: the ''@import'' rule</h2>
 		</pre>
 	</div>
 
+	A <dfn><<media-query>></dfn> corresponds to the <code>media_query_list</code> production and is interpreted as a <a>media query</a>,
+	and a <dfn><<supports-condition>></dfn> corresponds to either a <code>supports_condition</code> production
+	or a <code>declaration</code> production interpreted as a <code>supports_declaration_condition</code> production
+	and is interpreted as an ''@supports'' condition.
+	The evaluation and full syntax of the <a>import conditions</a>
+	are defined by the <a href="http://www.w3.org/TR/css3-mediaqueries/">Media Queries</a> [[!MEDIAQ]]
+	and <a href="http://www.w3.org/TR/css-conditional/">CSS Conditional Rules</a> [[!CSS3-CONDITIONAL]] specifications.
+
+	Issue: Feedback on the the <css>supports()</css> syntax is hereby solicited,
+	since none so far has been received.
+
+<h3 id=import-processing>
+Processing Stylesheet Imports</h3>
+
 	When the same style sheet is imported or linked to a document in multiple places,
 	user agents must process (or act as though they do) each link
 	as though the link were to an independent style sheet.