[css-overflow-3] Editorial tweaks

Improvements based on a review by fantasai

Author: frivoal

css-overflow-3/Overview.bs

@@ -822,7 +822,7 @@ Limiting Visible Lines: the 'line-clamp' shorthand property</h2>
 	See the corresponding longhand properties for details
 	about how this mechanism operates.
 
-	Note: For the time being,
+	Issue: For the time being,
 	experiemental implementations are encouraged
 	to follow the full behavior defined by this shorthand and its longhands,
 	but to only expose the shorthand to authors.
@@ -934,10 +934,6 @@ Forcing a break after a set number of lines: the 'max-lines' property</h2>
 <h2 id="fragmentation">
 Fragmentation of overflow: the 'continue' property</h2>
 
-The 'continue' property gives authors the ability
-to turn a box into a [=fragmentation container=] (see [[!CSS-BREAK-3]])
-and to specify that content after the [=fragmentation break=] must be discarded.
-
 	<pre class=propdef>
 		Name: continue
 		Value: ''continue/auto'' | ''discard''
@@ -949,6 +945,10 @@ and to specify that content after the [=fragmentation break=] must be discarded.
 		Canonical order: <abbr title="follows order of property value definition">per grammar</abbr>
 	</pre>
 
+The 'continue' property gives authors the ability
+to turn a box into a [=fragmentation container=] (see [[!CSS-BREAK-3]])
+and to specify that content after the [=fragmentation break=] must be discarded.
+
 Issue: This property is meant to generalize and replace the <code>region-fragment</code> property from [[CSS-REGIONS-1]].
 Once it is sufficiently stable in this specification,
 <code>region-fragment</code> should be removed from the regions specification in favor of this.
@@ -960,16 +960,16 @@ Once it is sufficiently stable in this specification,
 			If the box has more content than can fit,
 			the excess content is handled according to the usual rules:
 
-			* If the box is not a [=fragmentation container=]
-				or if it is the last [=fragmentation container=] in a [=fragmentation context=]
-				which does not automatically generate more as needed (for example the last region in a region chain, see [[CSS-REGIONS-1]]),
-				content that doesn't fit into the box overflows,
-				as specified by the 'overflow' property.
+			If the box is not a [=fragmentation container=]
+			or if it is the last [=fragmentation container=] in a [=fragmentation context=]
+			which does not automatically generate more as needed (for example the last region in a region chain, see [[CSS-REGIONS-1]]),
+			content that doesn't fit into the box overflows,
+			as specified by the 'overflow' property.
 
-			* Otherwise (i.e. the box is a non-last fragmentation container),
-				the remainer of the [=fragmented flow=] after the [=fragmentation break=] (if any)
-				is flowed to the next [=fragmentation container=] in the [=fragmentation context=].
-				The 'overflow' property continues to govern how to handle the contents of a box that extend outside one of that box’s edges
+			Otherwise (i.e. the box is a non-last fragmentation container),
+			the remainer of the [=fragmented flow=] after the [=fragmentation break=] (if any)
+			is flowed to the next [=fragmentation container=] in the [=fragmentation context=].
+			The 'overflow' property continues to govern how to handle the contents of a box that extend outside one of that box’s edges
 
 		<dt><dfn>discard</dfn>
 		<dd>
@@ -986,13 +986,19 @@ Once it is sufficiently stable in this specification,
 			is treated as the end of the <a>fragmentation container</a>,
 			and the rest of the <a>fragmented flow</a> is laid out in
 			the next <a>fragmentation container</a> in the <a>fragmentation context</a>.
-			The remaining content after the [=fragmentation break=]  is discarded,
+			The remaining content after the [=fragmentation break=] is discarded,
 			similar to if it were ''display: none'':
+			* Just as the content is visually hidden, it is not made available for speech rendering
+			* It does not allow user interaction
+			* [=Positioned=] elements whose static position is in the discarded content are not rendered.
+
+				Issue: Are we sure about that?
+				Discussions in the <a href="https://lists.w3.org/Archives/Public/www-style/2018Jul/0030.html">Syndey F2F meeting</a>
+				seemed to generally converge on this,
+				but other possibilities were raised.
 			* It is neither rendered,
 				nor measured as part of the box’s contents for the purpose of
 				finding its <a lt="min-content block size">min-content</a>, <a>max-content</a>, or <a lt="automatic size">automatic</a> <a>block sizes</a>
-			* It does not allow user interaction
-			* [=Positioned=] elements whose static position is in the discarded content are not rendered
 
 			However, since intrinsic sizes are calculated across all <a>fragmentation containers</a>,
 			this content <em>is</em> taken into account