[css-writing-modes] Fix terminology cross-links.

Author: fantasai

css-writing-modes/Overview.bs

@@ -20,6 +20,7 @@ At Risk: The ''digits'' value of 'text-combine-upright'.
 At Risk: The look-ahead/look-behind sequencing rules for 'text-combine-upright'.
 Ignored Terms: glyph orientation, *-left, *-right, *-top, *-bottom, block containers, text-combine-mode
 Link Defaults: css21 (property) display/min-height/max-height/min-width/max-width/clip/left/right/bottom/top, css-text-3 (property) letter-spacing, css-text-decor-3 (property) text-decoration, svg2 (property) glyph-orientation-vertical/glyph-orientation-horizontal
+Use <i> Autolinks: yes
 </pre>
 
 <style>
@@ -1873,16 +1874,17 @@ Dimensional Mapping</h3>
   <p>For example, the calculation rules in
     <a href="http://www.w3.org/TR/CSS21/visudet.html#Computing_widths_and_margins">CSS2.1 Section 10.3</a>
     are used for the inline dimension measurements:
-    they apply to the <i>inline-size</i> (which could be either the physical width or physical height)
+    they apply to the <i>inline size</i> (which could be either the physical width or physical height)
     and to the <i>inline-start</i> and <i>inline-end</i> margins, padding, and border.
     Likewise the calculation rules in
         <a href="http://www.w3.org/TR/CSS21/visudet.html#Computing_heights_and_margins">CSS2.1 Section 10.6</a>
-    are used in the block dimension: they apply to the <i>block-size</i> and to
-    the <i>block-start</i> and <i>block-end</i> margins, padding, and border. [[!CSS21]]
+    are used in the block dimension:
+    they apply to the <i>block size</i>
+    and to the <i>block-start</i> and <i>block-end</i> margins, padding, and border. [[!CSS21]]
 
   <p>As a corollary, percentages on the margin and padding properties,
     which are always calculated with respect to the containing block
-    width in CSS2.1, are calculated with respect to the <em><i>inline-size</i></em>
+    width in CSS2.1, are calculated with respect to the <em><i>inline size</i></em>
     of the containing block in CSS3.
 
 <h3 id="orthogonal-flows">
@@ -1917,13 +1919,13 @@ Orthogonal Flows</h3>
     <li>
       In the sizing phase—calculating the width and height of the
       box—the dimensions of the box and the containing block
-      are mapped to the <i>inline-size</i> and <i>block-size</i> and calculations are performed
+      are mapped to the <i>inline size</i> and <i>block size</i> and calculations are performed
       accordingly using the writing mode of
       the box establishing the <i>orthogonal flow</i>.
     <li>
       In the positioning phase—calculating the positioning offsets,
       margins, borders, and padding—the dimensions of the box and
-      its containing block are mapped to the <i>inline-size</i> and <i>block-size</i>
+      its containing block are mapped to the <i>inline size</i> and <i>block size</i>
       and calculations are performed according to the writing mode of the
       <em>containing block</em> of the box establishing the <i>orthogonal flow</i>.
   </ul>
@@ -1942,12 +1944,12 @@ Orthogonal Flows</h3>
     </div>
 
     <p>
-      For example, if a vertical block is placed inside a horizontal
-      block, then when calculating the physical height (which is the
-      <i>inline-size</i>) of the child block the physical height of the parent
-      block is used as the child's containing block <i>inline-size</i>, even
-      though the physical height is the <i>block-size</i>, not the <i>inline-size</i>, of
-      the parent block.
+      For example, if a vertical block is placed inside a horizontal block,
+      then when calculating the physical height (which is the <i>inline size</i>)
+      of the child block the physical height of the parent block is used
+      as the child's containing block <i>inline size</i>,
+      even though the physical height is the <i>block size</i>, not the <i>inline size</i>,
+      of the parent block.
 
     <p>
       On the other hand,
@@ -1961,25 +1963,27 @@ Orthogonal Flows</h3>
 <h4 id="orthogonal-auto">
 Auto-sizing in Orthogonal Flows</h4>
 
-  <p>It is common in CSS for a containing block to have a definite
-    <i>inline-size</i>, but not a definite <i>block-size</i>. This typically happens in
-    CSS2.1 when a containing block has an ''height/auto'' height, for
-    example: its width is given by the calculations in
+  <p>It is common in CSS for a containing block to have a definite <i>inline size</i>,
+    but not a definite <i>block size</i>.
+    This typically happens in CSS2.1
+    when a containing block has an ''height/auto'' height,
+    for example: its width is given by the calculations in
     <a href="http://www.w3.org/TR/CSS21/visudet.html#blockwidth">10.3.3</a>,
-    but its <i>block-size</i> depends on its contents. In such cases the
-    <i>available inline-size</i> is defined as the <i>inline-size</i> of the
-    containing block; but the <i>available block-size</i>, which
-    would otherwise be the <i>block-size</i> of the containing block, is
-    infinite.
+    but its <i>block size</i> depends on its contents.
+    In such cases the <i>available inline size</i> is defined
+    as the <i>inline size</i> of the containing block;
+    but the <i>available block size</i>,
+    which would otherwise be the <i>block size</i> of the containing block,
+    is infinite.
 
   <p>Putting a box in an <i>orthogonal flow</i> allows the opposite to happen:
-    for the <i>available blocksize</i> to be defined, but the <i>available
-    inline size</i> to be indefinite. In such cases a percentage of the
-    containing block’s <i>inline-size</i> cannot be defined, and <i>inline-axis</i>
-    computations cannot be resolved. In these cases, the initial
-    containing block's size is used as a <i>fallback</i> variable
-    in place of the <i>available inline-size</i> for calculations that
-    require a definite <i>available inline-size</i>.
+    for the <i>available block size</i> to be defined,
+    but the <i>available inline size</i> to be indefinite.
+    In such cases a percentage of the containing block’s <i>inline size</i> cannot be defined,
+    and <i>inline axis</i> computations cannot be resolved.
+    In these cases, the initial containing block's size is used
+    as a <i>fallback</i> variable in place of the <i>available inline size</i>
+    for calculations that require a definite <i>available inline size</i>.
 
   <p>See [[!CSS3-SIZING]] for further details on CSS sizing terminology and concepts.
 
@@ -1988,7 +1992,7 @@ Auto-sizing Block Containers in Orthogonal Flows</h4>
 
   <p>
     If a box establishing an <i>orthogonal flow</i> is a block container or multi-column element,
-    for the case where the box's <i>inline-size</i> is ''width/auto'':
+    for the case where the box's <i>inline size</i> is ''width/auto'':
 
   <ol>
     <li><strong>Calculate the used 'column-width':</strong>
@@ -2008,8 +2012,8 @@ Auto-sizing Block Containers in Orthogonal Flows</h4>
         <dd>the box’s <i>inline-axis</i> <a href="http://www.w3.org/TR/css3-sizing/#terms">fill-available fit</a>
         into the smaller of
         <ul>
-          <li>the box’s <i>available inline-size</i>
-          <li>the initial containing block’s <i>inline-size</i>
+          <li>the box’s <i>available inline size</i>
+          <li>the initial containing block’s <i>inline size</i>
       </dl>
 
       <div class="note">
@@ -2022,7 +2026,7 @@ Auto-sizing Block Containers in Orthogonal Flows</h4>
         is wrapped into columns in the flow direction of the containing block,
         thus avoiding T-shaped documents.
         Authors can control the measure of these columns by setting 'column-width',
-        or disable this behavior by setting the <i>inline-size</i> property
+        or disable this behavior by setting the <i>inline size</i> property
         to a non-''width/auto'' value such as ''width/max-content''.
         <br style="clear:both;">
       </div>
@@ -2039,14 +2043,14 @@ Auto-sizing Block Containers in Orthogonal Flows</h4>
     </ul>
 
     <li><strong>Calculate the used column length:</strong>
-      If the computed <i>block-size</i> is ''height/auto''
+      If the computed <i>block size</i> is ''height/auto''
       and the specified value of at least one of 'column-count' and 'column-width' was ''column-width/auto'',
-      use the box’s <i>block-size</i> (if that is <i>definite</i>),
-      else the <i>fill-available block-size</i> of the box (if that is <i>definite</i>),
-      else the box’s <i>max-content block-size</i>.
+      use the box’s <i>block size</i> (if that is <i>definite</i>),
+      else the <i>fill-available block size</i> of the box (if that is <i>definite</i>),
+      else the box’s <i>max-content block size</i>.
       Otherwise follow the normal rules for sizing a multi-column element.
       <p class="issue">
-        Should we factor in the box’s min-content block-size in this formula,
+        Should we factor in the box’s <i>min-content block size</i> in this formula,
         so that e.g. a large image will not overflow the box,
         but cause the box to overflow the containing block?
 
@@ -2057,19 +2061,19 @@ Auto-sizing Block Containers in Orthogonal Flows</h4>
   </ol>
 
   <p>
-    The used <i>inline-size</i> of the resulting multi-column element is then calculated:
+    The used <i>inline size</i> of the resulting multi-column element is then calculated:
     if the content neither line-wraps nor fragments within the multi-column element,
-    then the used <i>inline-size</i> is the <i>max-content inline-size</i> of the box's contents;
+    then the used <i>inline size</i> is the <i>max-content inline size</i> of the box's contents;
     else it is calculated from the used 'column-width', 'column-count', and 'column-gap'.
 
   <p>
-    The used <i>block-size</i> of the box is either the used column <i>block-size</i>
+    The used <i>block size</i> of the box is either the used column <i>block size</i>
     (if multiple columns were used)
-    or the <i>max-content block-size</i> of the content.
+    or the <i>max-content block size</i> of the content.
 
   <p>
     If the UA does not support CSS Multi-column Layout [[!CSS3COL]],
-    the UA may instead calculate the box's <i>inline-size</i> assuming an infinite <i>block-size</i>,
+    the UA may instead calculate the box's <i>inline size</i> assuming an infinite <i>block size</i>,
     thus laying out its contents into a single column.
     Note that this can, however, result in content that is clipped
     or otherwise inaccessible.
@@ -2079,12 +2083,12 @@ Auto-sizing Other Orthogonal Flow Roots</h4>
 
   <p>In order to limit the length of lines,
   block containers have special auto-sizing behavior (defined <a href="#auto-multicol">above</a>)
-  when their <i>available inline-size</i> is infinite
+  when their <i>available inline size</i> is infinite
   (which typically occurs when they establish an <i>orthogonal flow</i>).
 
-  <p>Other layout models simply lay out into the infinite <i>available inline-size</i>
+  <p>Other layout models simply lay out into the infinite <i>available inline size</i>
   at their <i>max-content size</i>.
-  However, they pass through the infinite <i>available inline-size</i>
+  However, they pass through the infinite <i>available inline size</i>
   to block containers they contain,
   possibly triggering that special auto-sizing behavior on those block containers
   even though they do not themselves establish an <i>orthogonal flow</i>.
@@ -2093,10 +2097,10 @@ Auto-sizing Other Orthogonal Flow Roots</h4>
     <p>For example,
       a table or <i>flex container</i> establishing an <i>orthogonal flow</i>
       is laid out into its given <i>available space</i>.
-      If its <i>available inline-size</i> is infinite,
+      If its <i>available inline size</i> is infinite,
       this effectively lays the box out at its <i>max-content size</i>.
       However, any of its table cells or <i>flex items</i> that are <i>block containers</i>
-      are laid out assuming infinite <i>available inline-size</i>
+      are laid out assuming infinite <i>available inline size</i>
       and so behave accordingly.
   </div>