[css-regions] Bikshed fixes

Author: frivoal

css-regions/Overview.src.html css-regions/Overview.bscss-regions/Overview.src.html renamed to css-regions/Overview.bs

@@ -390,7 +390,7 @@ <h3 id="the-flow-into-property">
 			are placed into the named flow.
 			The element or content is said to have
 			a <dfn id="specified-flow">specified flow</dfn>.
-			The values ''none'', ''inherit'', ''default'', ''auto'' and ''initial''
+			The values <code class=css>none</code>, <code class=css>inherit</code>, <code class=css>default</code>, <code class=css>auto</code> and <code class=css>initial</code>
 			are invalid flow names.
 		</dd>
 	</dl>
@@ -583,14 +583,14 @@ <h3 id="flow-from">
 	</dl>
 
 	If the 'content' property computes
-	to something else than ''normal''
-	(or ''none'' for a pseudo-element),
+	to something else than ''content/normal''
+	(or ''content/none'' for a pseudo-element),
 	the block container does not become
 	a <a>CSS Region</a>.
 	If the 'display' property
 	of the block container
 	or one of its ancestors
-	computes to ''none'',
+	computes to ''display/none'',
 	the block container does not become
 	a <a>CSS Region</a>.
 
@@ -603,7 +603,7 @@ <h3 id="flow-from">
 	Block container pseudo-elements where
 	the value of 'flow-from' computes to an
 	<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier">&lt;ident&gt;</a>
-	and the value of 'content' computes to ''none''
+	and the value of 'content' computes to ''content/none''
 	are generated as <a>CSS Regions</a>,
 	which is an update to the behavior
 	described in [[!CSS21]].
@@ -1071,7 +1071,7 @@ <h3 id="the-namedflow-interface">
 	that are in the <code>NULL</code> state.
 
 	The
-	<dfn interface><code class="idl">NamedFlowMap</code></dfn>
+	{{NamedFlowMap}}
 	interface provides a map of current
 	<a idl>NamedFlow</a> instances
 	in the document.
@@ -1107,7 +1107,7 @@ <h3 id="the-namedflow-interface">
 	uses the rest of the default map
 	<a href="http://dev.w3.org/2006/webapi/WebIDL/#es-map-members">class methods</a>.
 
-	The <dfn interface><code class="idl">NamedFlow</code></dfn>
+	The {{NamedFlow}}
 	interface offers a representation
 	of a <a>named flow</a> instance.
 
@@ -1214,7 +1214,7 @@ <h3 id="the-namedflow-interface">
 <h3 id="the-region-interface">
 The Region interface</h3>
 
-	The <dfn interface><code class="idl">Region</code></dfn>
+	The {{Region}}
 	interface is a
 	<a href="http://www.w3.org/TR/WebIDL/#idl-implements-statements">supplemental interface</a>
 	which must be implemented by all objects
@@ -1338,7 +1338,7 @@ <h3 id="the-region-interface">
 	if the 'flow-from' property
 	on the corresponding pseudo-element,
 	element or other construct
-	becomes ''none''
+	becomes ''flow-from/none''
 	but a script is still holding
 	a reference to the <a idl>Region</a> object.
 
@@ -1661,7 +1661,7 @@ <h3 id="regions-flow-content-box">
 
 	The <span>RFCB</span> is a
 	<a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>
-	with a computed 'width' of ''auto'' and whose used 'height' is resolved as detailed below.
+	with a computed 'width' of ''width/auto'' and whose used 'height' is resolved as detailed below.
 
 	Since the <span>RFCB</span> is a <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>, the ::before box and ::after box will also be block containers, though the contents of ::before and ::after may be inline within those boxes.
 
@@ -1923,15 +1923,15 @@ <h4 id="step1-phase1-example">
 Step 1 - Phase 1: Laying out RFCBs with used height of zero</h4>
 
 	Applying the rules for Step 1, Phase 1,
-	the computed ''auto'' 'width' values for the RFCBs are resolved
+	the computed ''width/auto'' 'width' values for the RFCBs are resolved
 	to used values according to the normal
 	<a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_widths_and_margins">CSS layout rules</a>
 	meaning they stretch to the width
 	of their containing block's content box.
 
 	<ol>
 		<li>RFCB-A: stretches to fit the rA content box.
-			<p>Since rA also has an ''auto'' 'width', its own used 'width' is stretched to fit the
+			<p>Since rA also has an ''width/auto'' 'width', its own used 'width' is stretched to fit the
 			<code>&lt;body&gt;</code> content box.</p>
 		</li>
 		<li>RFCB-B: stretches to fit the <code>rB</code> content box.</li>
@@ -1959,7 +1959,7 @@ <h4 id="step1-phase2-example">
 
 	The user agent lays out as much
 	of the flow into an area with RFCB-A's used 'width'.
-	rA's 'height' computes to ''auto''
+	rA's 'height' computes to ''width/auto''
 	and there is no vertical maximum height for RFCA's 'height'.
 	However, because there is a break after the first paragraph
 	in the "article" <code>named flow</code>,