w3c
diff --git a/‎css-multicol-1/Overview.bs‎
Lines changed: 25 additions & 23 deletions b/‎css-multicol-1/Overview.bs‎
Lines changed: 25 additions & 23 deletions
@@ -154,30 +154,32 @@ Introduction</h2>
 The multi-column model</h2>
 
 	A <dfn lt="multi-column container|multicol container" oldids="multi-column-element" export>multi-column container</dfn>
-	(or <em>multicol container</em> for short)
+	(or <i>multicol container</i> for short)
 	is an element whose 'column-width' or 'column-count'
 	property is not ''column-width/auto'' and therefore acts as a container for
 	multi-column layout.
 
 	In the traditional CSS box model, the content of an element is
 	flowed into the content box of the corresponding element. Multi-column
 	layout introduces a new type of container between the content box and
-	the content, namely the <dfn>column box</dfn> (or <em>column</em> for
+	the content, namely the <dfn export local-lt=column>column box</dfn> (or <i>column</i> for
 	short). The content of a multicol container is flowed into its column
 	boxes.
 
-	Column boxes in a multi-column container are arranged
-	into <em>rows</em>. Like table cells, the column boxes in a row are
-	ordered in the inline direction of the multicol container. The
-	<em>column width</em> is the length of the column box in the inline
-	direction. The <em>column height</em> is the length of the column box
-	in the block direction. All column boxes in a row have the same column width, and all
-	column boxes in a row have the same column height. Within each row in the multi-column container,
-	adjacent column boxes are separated by a <em>column gap</em>, which
-	may contain a <em>column rule</em>. All column gaps in the same row
-	are equal. All column rules in the same row are also equal, if they
-	appear; column rules only appear between columns that both have
-	content.
+	Column boxes in a multi-column container are arranged into <dfn export lt="column row" local-lt=row>rows</dfn>.
+	Like table cells,
+	the column boxes in a row are ordered
+	in the inline direction of the multicol container.
+	The <dfn export>column width</dfn> is the length of the column box in the inline direction.
+	The <dfn export>column height</dfn> is the length of the column box in the block direction.
+	All column boxes in a row have the same column width,
+	and all column boxes in a row have the same column height.
+	Within each row in the multi-column container,
+	adjacent column boxes are separated by a <dfn noexport>column gap</dfn>,
+	which may contain a <dfn noexport>column rule</dfn>.
+	All column gaps in the same row are equal.
+	All column rules in the same row are also equal, if they appear;
+	column rules only appear between columns that both have content.
 
 	In the simplest case a multicol container will contain only one row
 	of columns, and the height of each column will be equivalent to the
@@ -204,7 +206,7 @@ The multi-column model</h2>
 	constrained by the page and the content continues in a new row of
 	column boxes on the next page; a column box never splits across pages.
 
-	The same effect occurs when a <em>spanning element</em> divides the
+	The same effect occurs when a <i>spanning element</i> divides the
 	multi-column container: the columns before the spanning element are
 	balanced and shortened to fit their content. Content after the
 	spanning element then flows into a new row of column boxes.
@@ -1221,20 +1223,20 @@ This appendix is <em>informative</em>.
 <ul>
 	<li>Changed references to paged media to refer to fragmented contexts. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/1746#issuecomment-380731574">12 Apr 2018</a>.</li>
 	<li>Changed a line regarding the <code>column-fill</code> property:
-	<br><em>In continuous media, this property does not have any effect in
-	overflow columns.</em>
+	<br><q>In continuous media, this property does not have any effect in
+	overflow columns.</q>
 	<br>To:
-	<br><em>In continuous media, this property does not have any effect when there are overflow columns.</em> <a href="https://github.com/w3c/csswg-drafts/issues/2549">Resolved: 12 Apr 2018</a></li>
-    <li>Add a line of text plus an example to show that overflow columns can effect the multicol container height. <a href="https://github.com/w3c/csswg-drafts/issues/1745">Resolved: 12 Apr 2018</a></li>
+	<br><q>In continuous media, this property does not have any effect when there are overflow columns.</q> <a href="https://github.com/w3c/csswg-drafts/issues/2549">Resolved: 12 Apr 2018</a></li>
+	<li>Add a line of text plus an example to show that overflow columns can effect the multicol container height. <a href="https://github.com/w3c/csswg-drafts/issues/1745">Resolved: 12 Apr 2018</a></li>
 	<li>Replaced the HTML mock-up examples with SVG versions, as the examples were unclear. <a href="https://github.com/w3c/csswg-drafts/issues/1087">Issue 1087</a>.</li>
 	<li>Changed the value of normal for column-gap to be 1em, rather than a UA-specified length with a suggestion of 1em. <a href="https://github.com/w3c/csswg-drafts/issues/2145#issuecomment-378781507">Resolved: 4 Apr 2018</a></li>
 	<li>Clarified that negative values are not allowed for column-width, and that while 0 may be specified, used values will be clamped to a minimum of 1px. <a href="https://github.com/w3c/csswg-drafts/issues/1741#issuecomment-373091628">Resolved: 14 Mar 2018</a></li>
 	<li>Clarified that where there is a spanning element content is automatically balanced across all columns in the immediately preceding column row before the element appears. <a href="https://github.com/w3c/csswg-drafts/issues/1075">Resolved: 9 Nov 2017</a></li>
 	<li>Added clarification plus an additional example that spanning elements may be lower the the first level of descendents, and that in the case of margins, borders and padding on the element containing the spanning, this would be drawn above the spanner. <a href="https://github.com/w3c/csswg-drafts/issues/1072#issuecomment-342668025">Resolved: 8 Nov 2017</a></li>
-    <li>Changed the sentence <em>Column rules are painted in the inline content layer, but below all inline content inside the multicol element.</em> to <em>Column rules are painted just above the border of the multicol element. For scrollable multicol elements, note that while the border and background of the multicol element obviously aren’t scrolled, the rules need to scroll along with the columns.</em> <a href="https://github.com/w3c/csswg-drafts/issues/1739#issuecomment-342659978">Resolved: 7 Nov 2017</a></li>
-	<li>Under section The Multi-column Model, removed two sentences <em>That is, column boxes behave like block-level, table cell, and inline-block boxes as per CSS 2.1, section 10.1, item 2 CSS21. However, column boxes do not establish block container boxes for elements with ''position: fixed or position: absolute''.</em>. THese were replaced with a clarification about the principal box and a new example showing how abspos elements refer to the multicol container. <a href="https://github.com/w3c/csswg-drafts/issues/1738#issuecomment-342661881">Resolved: 7 Nov 2017</a></li>
-    <li>Removed the sentence "To indicate where column breaks should (or should not) appear, new keyword values are introduced." and following example (Example 7 in the WD published <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">5 Oct 2017</a>) as the multicol specification no longer introduces these properties. <a href="https://github.com/w3c/csswg-drafts/issues/1966">Editorial</a></li>
-    <li>Changed how we reference the element we have applied multicol to from multi-column or multicol <em>element</em> to multi-column or multicol <em>container</em>. <a href="https://github.com/w3c/csswg-drafts/issues/1965">Resolved: 22 November 2017</a></li>
+	<li>Changed the sentence <q>Column rules are painted in the inline content layer, but below all inline content inside the multicol element.</q> to <q>Column rules are painted just above the border of the multicol element. For scrollable multicol elements, note that while the border and background of the multicol element obviously aren’t scrolled, the rules need to scroll along with the columns.</q> <a href="https://github.com/w3c/csswg-drafts/issues/1739#issuecomment-342659978">Resolved: 7 Nov 2017</a></li>
+	<li>Under section The Multi-column Model, removed two sentences <q>That is, column boxes behave like block-level, table cell, and inline-block boxes as per CSS 2.1, section 10.1, item 2 CSS21. However, column boxes do not establish block container boxes for elements with ''position: fixed or position: absolute''.</q>. THese were replaced with a clarification about the principal box and a new example showing how abspos elements refer to the multicol container. <a href="https://github.com/w3c/csswg-drafts/issues/1738#issuecomment-342661881">Resolved: 7 Nov 2017</a></li>
+	<li>Removed the sentence "To indicate where column breaks should (or should not) appear, new keyword values are introduced." and following example (Example 7 in the WD published <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">5 Oct 2017</a>) as the multicol specification no longer introduces these properties. <a href="https://github.com/w3c/csswg-drafts/issues/1966">Editorial</a></li>
+	<li>Changed how we reference the element we have applied multicol to from multi-column or multicol <q>element</q> to multi-column or multicol <q>container</q>. <a href="https://github.com/w3c/csswg-drafts/issues/1965">Resolved: 22 November 2017</a></li>
 	<li>Removed the example which stated "If a tall image is moved to a column on the next page to find room for it, its natural column may be left empty. If so, the column is still considered to have content for the purpose of deciding if the column rule should be drawn." <a href="https://github.com/w3c/csswg-drafts/issues/1740">Resolved: 7 September 2017</a></li>
 </ul>