[css-break] Fix another vocabulary glitch. <http://lists.w3.org/Archives/Public/www-style/2013Dec/0378.html>

Author: fantasai

css-break/Overview.html

@@ -1060,11 +1060,12 @@ <h3 id=unforced-breaks><span class=secno>4.4. </span> Unforced Breaks</h3>
   </dl>
 
   <p> If the above doesn't provide enough break points to keep content from
-   overflowing the page boxes, then rules 1, 2 and 4 are dropped in order to
-   find additional breakpoints. In this case the UA may use the ‘<code
-   class=css>avoid</code>’s that are in effect at those points to weigh the
-   appropriateness of the new breakpoints; however, this specification does
-   not suggest a precise algorithm.
+   overflowing the <a href="#fragmentainer"><i>fragmentainer</i></a>, then
+   rules 1, 2 and 4 are dropped in order to find additional breakpoints. In
+   this case the UA may use the ‘<code class=css>avoid</code>’s that are
+   in effect at those points to weigh the appropriateness of the new
+   breakpoints; however, this specification does not suggest a precise
+   algorithm.
 
   <p> If that still does not lead to sufficient break points, rule 3 is
    dropped as well, to find still more break points.

css-break/Overview.src.html

@@ -774,8 +774,8 @@ <h3 id="unforced-breaks">
   </dl>
   <p>
     If the above doesn't provide enough break points to keep content from
-    overflowing the page boxes, then rules 1, 2 and 4 are dropped in order
-    to find additional breakpoints.
+    overflowing the <i>fragmentainer</i>,
+    then rules 1, 2 and 4 are dropped in order to find additional breakpoints.
     In this case the UA may use the ''avoid''s that are in effect at those
     points to weigh the appropriateness of the new breakpoints; however,
     this specification does not suggest a precise algorithm.