[css-break] Clarify parallel breaks by using flow -> formatting context, now that we have a good definition for that. Improve linking.

Author: fantasai

css-break/Overview.bs

@@ -99,7 +99,7 @@ Fragmentation Model and Terminology</h2>
     </dd>
     <dt><dfn>fragmented flow</dfn></dt>
     <dd>
-      A content flow that is being laid out in a <i>fragmentation context</i>.
+      Content that is being laid out in a <i>fragmentation context</i>.
       The <i>fragmented flow</i> consists of the content of a (possibly anonymous) box
       called the <dfn>fragmentation root</dfn>.
     </dd>
@@ -146,11 +146,11 @@ Fragmentation Model and Terminology</h2>
 Parallel Fragmentation Flows</h3>
 
   <p>
-    When multiple flows are laid out parallel to each other,
-    fragmentation is performed independently in each flow.
+    When multiple <a>formatting contexts</a> are laid out parallel to each other,
+    fragmentation is performed independently in each <a>formatting context</a>.
     For example, if an element is floated,
     then a forced break inside the float
-    will not affect the content wrapping outside the float
+    will not affect the content outside the float
     (except insofar as it may increase the height of the float).
   </p>
 
@@ -525,7 +525,7 @@ Page Break Aliases: the 'page-break-before', 'page-break-after', and 'page-break
 Rules for Breaking</h2>
 
   <p>
-    A fragmented flow may be broken across fragmentainers at a number of
+    A <a>fragmented flow</a> may be broken across <a>fragmentainers</a> at a number of
     <a href="#possible-breaks">possible break points</a>. In the case of
     <a href="#forced-breaks">forced breaks</a>, the UA is required to
     break the flow at that point. In the case of
@@ -705,7 +705,7 @@ Unforced Breaks</h3>
   <dl>
     <dt>Rule 1</dt>
     <dd>
-      A fragmented flow may break at a <a href="#btw-blocks">class A break point</a> only if
+      A <a>fragmented flow</a> may break at a <a href="#btw-blocks">class A break point</a> only if
       all the 'break-after' and 'break-before' values applicable to this
       break point allow it, which is when at least one of them forces a
       break or when none of them forbid it
@@ -772,7 +772,7 @@ Unforced Breaks</h3>
 <h3 id="best-breaks">
 Optimizing Unforced Breaks</h3>
 
-  <p>While CSS3 requires that a fragmented flow must break at allowed
+  <p>While CSS3 requires that a <a>fragmented flow</a> must break at allowed
     break points in order to avoid overflowing the fragmentainers in its
     fragmentation context, it does not define whether content breaks
     at a particular <a href="#unforced-breaks">allowed break</a>.

css-break/Overview.html

@@ -54,7 +54,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="http://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">CSS Fragmentation Module Level 3</h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2015-10-27">27 October 2015</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2015-12-01">1 December 2015</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -234,7 +234,7 @@ <h2 class="heading settled" data-level="2" id="fragmentation-model"><span class=
       (Descendants of the <a data-link-type="dfn" href="#fragmentation-root">fragmentation root</a> may have other block flow directions,
       but fragmentation proceeds according to the block flow direction applied to the <a data-link-type="dfn" href="#fragmentation-root">fragmentation root</a>.) 
     <dt><dfn data-dfn-type="dfn" data-export="" id="fragmented-flow">fragmented flow<a class="self-link" href="#fragmented-flow"></a></dfn>
-    <dd> A content flow that is being laid out in a <a data-link-type="dfn" href="#fragmentation-context">fragmentation context</a>.
+    <dd> Content that is being laid out in a <a data-link-type="dfn" href="#fragmentation-context">fragmentation context</a>.
       The <a data-link-type="dfn" href="#fragmented-flow">fragmented flow</a> consists of the content of a (possibly anonymous) box
       called the <dfn data-dfn-type="dfn" data-export="" id="fragmentation-root">fragmentation root<a class="self-link" href="#fragmentation-root"></a></dfn>. 
     <dt><dfn data-dfn-type="dfn" data-export="" id="fragmentation-direction">fragmentation direction<a class="self-link" href="#fragmentation-direction"></a></dfn>
@@ -259,11 +259,11 @@ <h2 class="heading settled" data-level="2" id="fragmentation-model"><span class=
     and similarly creates box fragments when it breaks <a href="http://www.w3.org/TR/CSS21/visuren.html#inline-boxes">inline boxes</a> across <a href="http://www.w3.org/TR/CSS21/visuren.html#line-box">line boxes</a>.
     However, inline breaking is not covered here; see <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a>/<a data-link-type="biblio" href="#biblio-css3text">[CSS3TEXT]</a>. </p>
    <h3 class="heading settled" data-level="2.1" id="parallel-flows"><span class="secno">2.1. </span><span class="content"> Parallel Fragmentation Flows</span><a class="self-link" href="#parallel-flows"></a></h3>
-   <p> When multiple flows are laid out parallel to each other,
-    fragmentation is performed independently in each flow.
+   <p> When multiple <a data-link-type="dfn" href="https://drafts.csswg.org/css-display-3/#formatting-context">formatting contexts</a> are laid out parallel to each other,
+    fragmentation is performed independently in each <a data-link-type="dfn" href="https://drafts.csswg.org/css-display-3/#formatting-context">formatting context</a>.
     For example, if an element is floated,
     then a forced break inside the float
-    will not affect the content wrapping outside the float
+    will not affect the content outside the float
     (except insofar as it may increase the height of the float). </p>
    <p> The following are examples of parallel flows
     whose contents will fragment independently: </p>
@@ -509,7 +509,7 @@ <h3 class="heading settled" data-level="3.4" id="page-break-properties"><span cl
       <td><span class="css">page</span> 
    </table>
    <h2 class="heading settled" data-level="4" id="breaking-rules"><span class="secno">4. </span><span class="content"> Rules for Breaking</span><a class="self-link" href="#breaking-rules"></a></h2>
-   <p> A fragmented flow may be broken across fragmentainers at a number of <a href="#possible-breaks">possible break points</a>. In the case of <a href="#forced-breaks">forced breaks</a>, the UA is required to
+   <p> A <a data-link-type="dfn" href="#fragmented-flow">fragmented flow</a> may be broken across <a data-link-type="dfn" href="#fragmentainer">fragmentainers</a> at a number of <a href="#possible-breaks">possible break points</a>. In the case of <a href="#forced-breaks">forced breaks</a>, the UA is required to
     break the flow at that point. In the case of <a href="#unforced-breaks">unforced breaks</a>, the UA has to choose
     among the possible breaks that are allowed. </p>
    <p> To guarantee progress, fragmentainers are assumed to have a minimum <a data-link-type="dfn" href="https://drafts.csswg.org/css-writing-modes-3/#block-size">block size</a> of 1px regardless of their used size. </p>
@@ -613,7 +613,7 @@ <h3 class="heading settled" data-level="4.4" id="unforced-breaks"><span class="s
     at a <a href="#possible-breaks">possible break point</a> is allowed: </p>
    <dl>
     <dt>Rule 1
-    <dd> A fragmented flow may break at a <a href="#btw-blocks">class A break point</a> only if
+    <dd> A <a data-link-type="dfn" href="#fragmented-flow">fragmented flow</a> may break at a <a href="#btw-blocks">class A break point</a> only if
       all the <a class="property" data-link-type="propdesc" href="#propdef-break-after">break-after</a> and <a class="property" data-link-type="propdesc" href="#propdef-break-before">break-before</a> values applicable to this
       break point allow it, which is when at least one of them forces a
       break or when none of them forbid it
@@ -650,7 +650,7 @@ <h3 class="heading settled" data-level="4.4" id="unforced-breaks"><span class="s
     so that each fragmentainer has a non-zero amount of content,
     in order to guarantee progress through the content. </span></p>
    <h3 class="heading settled" data-level="4.5" id="best-breaks"><span class="secno">4.5. </span><span class="content"> Optimizing Unforced Breaks</span><a class="self-link" href="#best-breaks"></a></h3>
-   <p>While CSS3 requires that a fragmented flow must break at allowed
+   <p>While CSS3 requires that a <a data-link-type="dfn" href="#fragmented-flow">fragmented flow</a> must break at allowed
     break points in order to avoid overflowing the fragmentainers in its
     fragmentation context, it does not define whether content breaks
     at a particular <a href="#unforced-breaks">allowed break</a>.