Add missing instances of recto/verso in prose.

Author: fantasai

css3-break/Overview.html

@@ -582,7 +582,8 @@ <h3 id=break-properties><span class=secno>3.1. </span> Forced breaks and
    than ‘<code class=css>auto</code>’, the <dfn
    id=forced-break-values>forced break values</dfn> (‘<code
    class=css>always</code>’, ‘<code class=css>left</code>’, ‘<code
-   class=css>right</code>’, ‘<code class=css>page</code>’, ‘<code
+   class=css>right</code>’, ‘<code class=css>recto</code>’, ‘<code
+   class=css>verso</code>’, ‘<code class=css>page</code>’, ‘<code
    class=css>column</code>’ and ‘<code class=css>region</code>’) take
    precedence over the <dfn id=avoid-break-values>avoid break values</dfn>
    (‘<code class=css>avoid</code>’, ‘<code
@@ -849,10 +850,11 @@ <h3 id=forced-breaks><span class=secno>4.3. </span> Forced breaks</h3>
   <p> When multiple <a href="#forced-break-values"><i>forced break
    values</i></a> apply to a single break point, they combine such all types
    of break are honored and no content-empty page boxes are generated, except
-   for at most one content-empty page as may be required by the ‘<code
-   class=css>right</code>’ or ‘<code class=css>left</code>’ values to
-   position ensuing content on a right- or left-facing page. When ‘<code
-   class=css>left</code>’ and ‘<code class=css>right</code>’ are both
+   for at most one content-empty page as may be required by the <a
+   href="#forced-break-values"><i>forced break values</i></a> to position
+   ensuing content on a specific type of page. When ‘<code
+   class=css>left</code>’, ‘<code class=css>right</code>’, ‘<code
+   class=css>recto</code>’, and/or ‘<code class=css>verso</code>’ are
    combined, the value specified on the latest element in the flow wins.
 
   <p class=note> A page break must also occur at <a

css3-break/Overview.src.html

@@ -354,7 +354,7 @@ <h3 id="break-properties">
     and the 'break-before' property of the following element.
     When these properties have values other than ''auto'',
     the <dfn>forced break values</dfn>
-    (''always'', ''left'', ''right'', ''page'', ''column'' and ''region'')
+    (''always'', ''left'', ''right'', ''recto'', ''verso'', ''page'', ''column'' and ''region'')
     take precedence over the <dfn>avoid break values</dfn>
     (''avoid'', ''avoid-page'', ''avoid-column'' and ''avoid-region'').
     See the section on <a href="#breaking-rules">rules for breaking</a>
@@ -609,10 +609,10 @@ <h3 id="forced-breaks">
     When multiple <i>forced break values</i> apply to a single break point,
     they combine such all types of break are honored and no content-empty
     page boxes are generated, except for at most one content-empty page as
-    may be required by the ''right'' or ''left'' values to position ensuing
-    content on a right- or left-facing page.
-    When ''left'' and ''right'' are both combined, the value specified on the
-    latest element in the flow wins.
+    may be required by the <i>forced break values</i>
+    to position ensuing content on a specific type of page.
+    When ''left'', ''right'', ''recto'', and/or ''verso'' are combined,
+    the value specified on the latest element in the flow wins.
   </p>
   <p class="note">
     A page break must also occur at <a href="#btw-blocks">(1)</a>