[css-flexbox-1][editorial] Miscellaneous bikeshed fixes.

Author: tabatkins

css-flexbox-1/Overview.bs

@@ -441,7 +441,7 @@ Flex Layout Box Model and Terminology</h2>
 
 	Unlike block and inline layout,
 	whose layout calculations are biased to the <a href="https://www.w3.org/TR/css3-writing-modes/#abstract-box">block and inline flow directions</a>,
-	flex layout is biased to the <dfn lt="flex direction">flex directions</dfn>.
+	flex layout is biased to the <dfn export lt="flex direction">flex directions</dfn>.
 	To make it easier to talk about flex layout,
 	this section defines a set of flex flow&ndash;relative terms.
 	The 'flex-flow' value and the <a>writing mode</a>
@@ -678,7 +678,7 @@ Flex Items</h2>
 	</div>
 
 	A <a>flex item</a> [=establishes an independent formatting context=] for its contents.
-	However, flex items themselves are <dfn>flex-level</dfn> boxes, not block-level boxes:
+	However, flex items themselves are <dfn export>flex-level</dfn> boxes, not block-level boxes:
 	they participate in their container's flex formatting context,
 	not in a block formatting context.
 
@@ -822,9 +822,9 @@ Flex Item Z-Ordering</h3>
 Collapsed Items</h3>
 
 	Specifying ''visibility:collapse'' on a flex item
-	causes it to become a <dfn lt="collapsed flex item" local-lt="collapsed">collapsed flex item</dfn>,
+	causes it to become a <dfn export lt="collapsed flex item" local-lt="collapsed">collapsed flex item</dfn>,
 	producing an effect similar to ''visibility:collapse'' on a table-row or table-column:
-	the collapsed flex item is removed from rendering entirely,
+	the [=collapsed flex item=] is removed from rendering entirely,
 	but leaves behind a "strut" that keeps the flex line's cross-size stable.
 	Thus, if a flex container has only one flex line,
 	dynamically collapsing or uncollapsing items
@@ -834,7 +834,7 @@ Collapsed Items</h3>
 	Flex line wrapping <em>is</em> re-done after collapsing, however,
 	so the cross-size of a flex container with multiple lines might or might not change.
 
-	Though collapsed flex items aren't rendered,
+	Though [=collapsed flex items=] aren't rendered,
 	they do appear in the <a href="https://www.w3.org/TR/CSS2/intro.html#formatting-structure">formatting structure</a>.
 	Therefore, unlike on ''display:none'' items [[!CSS2]],
 	effects that depend on a box appearing in the formatting structure
@@ -931,7 +931,7 @@ Collapsed Items</h3>
 	</div>
 
 	To compute the size of the strut, flex layout is first performed with all items uncollapsed,
-	and then re-run with each collapsed item replaced by a strut that maintains
+	and then re-run with each [=collapsed flex item=] replaced by a strut that maintains
 	the original cross-size of the item's original line.
 	See the <a href="#layout-algorithm">Flex Layout Algorithm</a>
 	for the normative definition of how ''visibility:collapse''
@@ -1634,7 +1634,7 @@ The 'flex' Shorthand</h3>
 	Animation type: by computed value type
 	</pre>
 
-	The 'flex' property specifies the components of a <dfn>flexible length</dfn>:
+	The 'flex' property specifies the components of a flexible size:
 	the <dfn lt="flex factor">flex factors</dfn>
 	(<a lt="flex grow factor">grow</a> and <a lt="flex shrink factor">shrink</a>)
 	and the <a>flex basis</a>.
@@ -2721,24 +2721,22 @@ Cross Size Determination</h3>
 		<li id='algo-visibility'>
 			<strong>Collapse ''visibility:collapse'' items.</strong>
 			If any flex items have ''visibility: collapse'',
-			note the cross size of the line they're in as the item's <dfn>strut size</dfn>,
+			note the cross size of the line they're in as the item's |strut size|,
 			and restart layout from the beginning.
 
-			<p>
-				In this second layout round,
-				when <a href="#algo-line-break">collecting items into lines</a>,
-				treat the collapsed items as having zero <a>main size</a>.
-				For the rest of the algorithm following that step,
-				ignore the collapsed items entirely
-				(as if they were ''display:none'')
-				except that after <a href="#algo-cross-line">calculating the cross size of the lines</a>,
-				if any line's cross size is less than
-				the largest <var>strut size</var>
-				among all the collapsed items in the line,
-				set its cross size to that <var>strut size</var>.
+			In this second layout round,
+			when <a href="#algo-line-break">collecting items into lines</a>,
+			treat the collapsed items as having zero <a>main size</a>.
+			For the rest of the algorithm following that step,
+			ignore the collapsed items entirely
+			(as if they were ''display:none'')
+			except that after <a href="#algo-cross-line">calculating the cross size of the lines</a>,
+			if any line's cross size is less than
+			the largest <var>strut size</var>
+			among all the collapsed items in the line,
+			set its cross size to that <var>strut size</var>.
 
-			<p>
-				Skip this step in the second layout round.
+			Skip this step in the second layout round.
 
 		<li id='algo-stretch'>
 			<strong>Determine the used cross size of each flex item.</strong>
@@ -3702,7 +3700,7 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 
 	<ul>
 		<li id="change-2019-bracket-range-notation">
-			Changed syntax to use <a>bracketed range notation</a> to reflect the prose restrictions on negative values.
+			Changed syntax to use <a>CSS bracketed range notation</a> to reflect the prose restrictions on negative values.
 
 		<li id="change-2018-used-cross-size">
 			Clarified that the [=flex base size=] calculations
@@ -3723,7 +3721,7 @@ Changes since the <a href="https://www.w3.org/TR/2018/CR-css-flexbox-1-20181119/
 			(<a href="https://github.com/w3c/csswg-drafts/issues/5188">Issue 5188</a>)
 
 			<blockquote>
-				<p><strong>Determine the <dfn>hypothetical cross size</dfn> of each item</strong>
+				<p><strong>Determine the hypothetical cross size of each item</strong>
 				by performing layout <ins>as if it were an [=in-flow=] [=block-level box=]
 				with the used <a>main size</a> and the <ins>given</ins> available space &hellip;
 			</blockquote>
@@ -4935,7 +4933,7 @@ Substantive Changes and Bugfixes</h4>
 		<li id="change-2012-min-width">
 			Changed the behavior of the new ''min-width/auto'' initial value of 'min-width'/'min-height' to
 			<ul>
-				<li>Take into account whether 'overflow' is ''visible'',
+				<li>Take into account whether 'overflow' is ''overflow/visible'',
 					since when 'overflow' is explicitly handled, it is confusing (and unnecessary)
 					to force enough size to show all the content.
 				<li>Take into account the specified 'width'/'height',