[css-multicol-1] references to paged vs continuous media should be fragmented vs continuous contexts #1746

Author: rachelandrew

css-multicol-1/Overview.bs

@@ -509,8 +509,8 @@ Two assumptions are being made by the pseudo-algorithm:
 
 	For the purpose of finding the number of auto-repeated tracks, the UA must floor the track size to a UA-specified value to avoid division by zero. It is suggested that this floor be 1px or less.
 
-	In paged media, user agents may perform this calculation on a
-	per-page basis.
+	In fragmented contexts such as in paged media, user agents may perform this calculation on a
+	per-fragment basis.
 
 	The used value for 'column-count' is calculated without
 	regard for explicit column breaks or constrained column heights,
@@ -779,7 +779,7 @@ Spanning columns</h2>
 			Content in the normal flow that appears before the
 			element is automatically balanced across all columns in the immediately preceding column row before the
 			element appears.
-			The element [=establishes an independent formatting context=].
+			The element establishes an independent <a>formatting context</a>.
 
 			Note: Whether the element establishes a new <a>formatting context</a>
 			does not depend on whether the element is a descendent of a multicol or not.
@@ -878,8 +878,8 @@ h2 {
 	</div>
 
 	<div class="example">
-		In paged media spanning elements are honored on all pages.
-		In this example, the first three paragraphs have column breaks after them.
+		In fragmented contexts spanning elements are honored in all fragments.
+		In this example, we are in paged media, and the first three paragraphs have column breaks after them.
 		An spanning <code>H2</code> element appears after the fourth paragraph.
 
 
@@ -951,29 +951,29 @@ Filling columns</h2>
 		<dt><dfn>balance</dfn>
 		<dd>
 			Balance content equally between columns, as far as possible.
-			In paged media, only the last page is balanced.
+			In fragmented contexts, only the last fragment is balanced.
 
 		<dt><dfn>balance-all</dfn>
 		<dd>
 			Balance content equally between columns, as far as possible.
-			In paged media, all pages are balanced.
+			In fragmented contexts, all fragments are balanced.
 
 		<dt><dfn>auto</dfn>
 		<dd>
 			fill columns sequentially
 	</dl>
 
 	<!--
-	In continuous media, this property will only be consulted if the
+	In continuous contexts, this property will only be consulted if the
 	length of columns has been constrained. Otherwise, columns will
 	automatically be balanced.
 	-->
 
-	In continuous media, this property does not have any effect when there are overflow columns.
+	In continuous contexts, this property does not have any effect when there are overflow columns.
 
 	<!--
-	In paged media, this property will only have
-	effect on the last page the multicol container appears on.
+	In fragmented contexts, this property will only have
+	effect on the last fragment the multicol container appears in.
 	-->
 
 	<div class="example">
@@ -1112,12 +1112,12 @@ Pagination and overflow outside multicol containers</h3>
 
 		<li>
 			explicit column breaks. In this case, additional column boxes are
-			created in the inline direction for continuous media, and
-			additional column boxes are moved to the next page(s) for paged
+			created in the inline direction for continuous contexts, and
+			additional column boxes are moved to the next fragment(s) for fragmented
 			media.
 	</ul>
 
-	Columns that appear outside the multicol container in continuous media
+	Columns that appear outside the multicol container in continuous contexts
 	are called <dfn>overflow columns</dfn>. Overflow columns can effect the height of the multicol container.
 
 	<div class="example">
@@ -1143,7 +1143,7 @@ Pagination and overflow outside multicol containers</h3>
 
 	<div class="example">
 
-		In continuous media overflow columns can effect the height of the multicol container. In this example a column appears in the overflow which has four lines of text. The multicol container is made tall enough to accomodate this column.
+		In continuous contexts overflow columns can effect the height of the multicol container. In this example a column appears in the overflow which has four lines of text. The multicol container is made tall enough to accomodate this column.
 
 		<figure>
 			<img src="images/overflow-column-effects-height.svg" alt="Four columns, overflow column is taller than the first three">
@@ -1153,7 +1153,7 @@ Pagination and overflow outside multicol containers</h3>
 	</div>
 
 	<div class="example">
-		In paged media, the overflow content goes into column on subsequent pages.
+		In fragmented contexts, the overflow content goes into columns in subsequent fragments.
 		Given the same content as in the previous example
 		and a page box that only has room for five lines of formatted text,
 		this would appear on the first page:
@@ -1218,6 +1218,7 @@ This appendix is <em>informative</em>.
 
 <h3 id="changes-from-20171005">Changes from the <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">Working Draft (WD) of 5 October 2017</a></h3>
 <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>