[css-page] Update references in page progression section. Fix bikeshed errors.

Author: fantasai

css-page/Overview.bs

@@ -13,7 +13,7 @@ Previous Version: http://www.w3.org/TR/2013/WD-css3-page-20130314/
 Editor: Elika J. Etemad / fantasai, Invited Expert, formerly Mozilla, http://fantasai.inkedblade.net/contact
 Editor: Simon Sapin, Mozilla, formerly Kozea, http://exyr.org/about/
 Ignored terms: fit, fit-position, stacking context
-Link defaults: css-break (property) break-after, css21 (property) display, css21 (property) min-height, css21 (property) max-height, css21 (property) min-width, css21 (property) max-width, css21 (property) margin, css-content-3 (property) counter-increment, css-content-3 (property) counter-reset
+Link defaults: css-break (property) break-after, css21 (property) display, css21 (property) min-height, css21 (property) max-height, css21 (property) min-width, css21 (property) max-width, css21 (property) margin, css21 (property) counter-increment, css21 (property) counter-reset
 Abstract: This CSS module specifies how pages are generated and laid out to hold fragmented content in a paged presentation. It adds functionality for controlling page margins, page size and orientation, and headers and footers, and extends generated content to enable page numbering and running headers / footers. The process of paginating a flow into such generated pages is covered in [[!CSS3-BREAK]].
 </pre>
 
@@ -259,7 +259,7 @@ Page Backgrounds and Painting Order</h3>
 	which covers the entire page box, including its margins (regardless of 'background-clip').
 	Page backgrounds are anchored within the page box's padding area by default
 	(and honor 'background-origin' if the UA supports [[!CSS3BG]]).
-	However if 'background-attachment' is ''fixed''
+	However if 'background-attachment' is ''background-attachment/fixed''
 	then the image is positioned relative to the page box including its margins
 	(i.e. the <a spec=css-backgrounds>background positioning area</a>
 	is the page's margin box).
@@ -344,7 +344,7 @@ box:
 	A <dfn export id="content-empty">Content-empty page</dfn> is a page box whose page
 	area contains no printable content other than backgrounds and/or borders. A
 	page box whose page area contains generated content, or content whose
-	visibility is ''hidden'', or invisible content such as a zero-width space is
+	visibility is ''visibility/hidden'', or invisible content such as a zero-width space is
 	not a content-empty page. On the other hand, a page containing only a
 	background and/or borders and/or page-margin box content <em>is</em> a
 	content-empty page.
@@ -367,61 +367,61 @@ box:
 
 <h3 id="progression">Page Progression</h3>
 
-CSS distinguishes between left pages and right pages on all documents,
-whether they are printed duplex or not. Each left page is followed by a
-right page and vice versa. Left and right pages can be styled differently
-with the <a href="#left-right-first"><code>:left</code> and <code>:right</code>
-pseudo-classes</a>.
+	CSS distinguishes between left pages and right pages on all documents,
+	whether they are printed duplex or not.
+	Each left page is followed by a right page and vice versa.
+	Left and right pages can be styled differently
+	with the <a href="#left-right-first"><code>:left</code> and <code>:right</code> pseudo-classes</a>.
 
-Whether the first page of a document is a left page or a right page
-depends on the page progression of the document. The <dfn export>page progression</dfn>
-is the direction in which the printed pages of a document would be sequenced
-when laid out side-to-side. For example, English and horizontally-set Japanese
-typically progress from left to right, whereas Arabic and vertically-set
-Japanese pages typically progress from right to left. In documents with
-a left-to-right page progression the first page of the document is a right
-page, and vice versa.
+	Whether the first page of a document is a left page or a right page
+	depends on the page progression of the document.
+	The <dfn export>page progression</dfn>
+	is the direction in which the printed pages of a document would be sequenced
+	when laid out side-to-side.
+	For example, English and horizontally-set Japanese typically progress from left to right,
+	whereas Arabic and vertically-set Japanese pages typically progress from right to left.
 
-The page progression direction is determined as follows:
+	The page progression direction is determined as follows:
 
-<ul>
-	<li>If text is laid out in horizontal lines, the page progression is the
-	same as the inline progression.
-	<li>If text is laid out in vertical lines, the page progression is the
-	same as the block progression.
-</ul>
+	<ul>
+		<li>If text is laid out in horizontal lines,
+		the <a>page progression</a> is the same as the <a>inline base direction</a>.
+		<li>If text is laid out in vertical lines,
+		the <a>page progression</a> is the same as the <a>block flow direction</a>.
+	</ul>
 
-If the UA supports the 'direction' and 'writing-mode' properties
-from the CSS 3 Writing Modes Module [[CSS3-WRITING-MODES]], it must
-<a href="http://www.w3.org/TR/css3-writing-modes/#page-direction">determine</a>
-whether the first page is a left or right page from the values of those
-properties on the root element.
+	If the UA supports the 'direction' and 'writing-mode' properties
+	from the CSS 3 Writing Modes Module [[CSS3-WRITING-MODES]], it must
+	<a href="http://www.w3.org/TR/css3-writing-modes/#page-direction">determine</a>
+	the <a>page progression</a> is determed by the <a>principal writing mode</a>.
 
+	In documents with a left-to-right <a>page progression</a>
+	the first page of the document is a right page, and vice versa.
 	To explicitly force a document to begin printing on a left or right page,
 	authors can specify a <a href="http://www.w3.org/TR/css3-break/#break-before">'break-before'</a> value
 	that that propagates a page break to the root. [[!CSS3-BREAK]]
 	The UA must suppress the first (empty) page(s) in this case
 	(and the <code>:first</code> pseudo-class matches the first printed page).
 
-<div class="example">
-<pre>
-html { break-before: always }
-</pre>
+	<div class="example">
+		<pre>
+			html { break-before: always }
+		</pre>
 
-	For an HTML document with a left-to-right page progression,
-	the above style rule will cause the first page of the document
-	to print on a ':left' page
+		For an HTML document with a left-to-right page progression,
+		the above style rule will cause the first page of the document
+		to print on a ':left' page
 
-<pre>
-html { break-before: left }
-</pre>
+		<pre>
+			html { break-before: left }
+		</pre>
 
-	For an HTML document,
-	the above style rule will cause the first page of the document
-	to print on a ':left' page,
-	regardless of the page progression.
+		For an HTML document,
+		the above style rule will cause the first page of the document
+		to print on a ':left' page,
+		regardless of the page progression.
 
-</div>
+	</div>
 
 <h2 id="page-selector-and-context">
 Page Selectors and the Page Context</h2>
@@ -551,7 +551,7 @@ Blank-page pseudo-class: '':blank''</h4>
 	<a href="http://www.w3.org/TR/css3-break/#forced-breaks">forced page breaks</a>.
 
 	<div class="note">
-		Only the ''left'', ''right'', ''recto'' and ''verso'' values
+		Only the ''break-before/left'', ''break-before/right'', ''break-before/recto'' and ''break-before/verso'' values
 		of the 'break-before' and 'break-after' properties
 		can generate pages that match '':blank''.
 	</div>
@@ -1081,12 +1081,12 @@ then it must behave as if 'min-height' and 'min-width' were always zero.
 			as defined in [[!CSS21]].
 
 		<dt><dfn>min-content width</dfn>
-		<dd>Whichever of <a spec=css-sizing>min-content block-size</a>
-		or <a spec=css-sizing>min-content inline-size</a> is the physical width.
+		<dd>Whichever of <a spec=css-sizing>min-content block size</a>
+		or <a spec=css-sizing>min-content inline size</a> is the physical width.
 
 		<dt><dfn>max-content width</dfn>
-		<dd>Whichever of <a spec=css-sizing>max-content block-size</a>
-		or <a spec=css-sizing>max-content inline-size</a> is the physical width.
+		<dd>Whichever of <a spec=css-sizing>max-content block size</a>
+		or <a spec=css-sizing>max-content inline size</a> is the physical width.
 
 		<dt><dfn>outer min width</dfn>
 		<dd>Like the <a>outer width</a>,
@@ -1472,7 +1472,7 @@ Page Properties</h2>
 
 		<li>
 			As on the '::before' and '::after' pseudo-elements,
-			the ''normal'' value of the 'content' property computes to ''none''
+			the ''content/normal'' value of the 'content' property computes to ''none''
 			on page-margin boxes.
 
 		<li>
@@ -1513,11 +1513,11 @@ Page-based counters</h3>
 	flow that spans the page break. Use of the counter in this way does not affect
 	the calculation of the counter's value.
 
-	A counter named ''page'' is automatically created
+	A counter named <css>page</css> is automatically created
 	and incremented by 1 on every page of the document,
 	unless the 'counter-increment' property in the <a>page context</a>
-	explicitly specifies a different increment for the ''page'' counter.
-	The implied ''page'' counter is a real counter,
+	explicitly specifies a different increment for the <css>page</css> counter.
+	The implied <css>page</css> counter is a real counter,
 	and can be directly affected using the 'counter-increment' and 'counter-reset' properties
 	when named explicitly in those properties.
 	It can also be used in the 'counter()' and 'counters()' function forms.