[css-layout-api] Update linking style.

Author: bfgeek

css-layout-api/Overview.bs

@@ -98,11 +98,11 @@ Introduction {#intro}
 
 <em>This section is not normative.</em>
 
-The layout stage of CSS is responsible for generating and positioning <a>fragments</a> from the
-<a>box tree</a>.
+The layout stage of CSS is responsible for generating and positioning [=fragments=] from the [=box
+tree=].
 
-This specification describes an API which allows developers to layout a <a>box</a> in response to
-computed style and <a>box tree</a> changes.
+This specification describes an API which allows developers to layout a [=box=] in response to
+computed style and [=box tree=] changes.
 
 Layout API Containers {#layout-api-containers}
 ==============================================
@@ -113,29 +113,29 @@ to the <<display-inside>> production: <code>layout(<<ident>>)</code>.
 <dl dfn-for="display" dfn-type=value>
     <dt><dfn>layout()</dfn>
     <dd>
-        This value causes an element to generate a <a>layout API container</a> box.
+        This value causes an element to generate a [=layout API container=] box.
 </dl>
 
 A <dfn>layout API container</dfn> is the box generated by an element with a <<display-inside>>
-<a>computed value</a> ''layout()''.
+[=computed value=] ''layout()''.
 
-A <a>layout API container</a> establishes a new <dfn>layout API formatting context</dfn> for its
+A [=layout API container=] establishes a new <dfn>layout API formatting context</dfn> for its
 contents. This is the same as establishing a block formatting context, except that the layout
 provided by the author is used instead of the block layout.
 For example, floats do not intrude into the layout API container, and the layout API container's
 margins do not collapse with the margins of its contents.
 
-All inflow children of a <a>layout API container</a> are called <dfn>layout API children</dfn> and
-are laid out using the author defined layout.
+All inflow children of a [=layout API container=] are called <dfn>layout API children</dfn> and are
+laid out using the author defined layout.
 
-<a>Layout API containers</a> form a containing block for their contents
-<a href="https://www.w3.org/TR/CSS2/visudet.html#containing-block-details">exactly like block
+[=Layout API containers=] form a containing block for their contents <a
+href="https://www.w3.org/TR/CSS2/visudet.html#containing-block-details">exactly like block
 containers do</a>. [[!CSS21]]
 
 Note: In a future level of the specification there may be a way to override the containing block
     behaviour.
 
-The 'overflow' property applies to <a>layout API containers</a>. This is discussed in
+The 'overflow' property applies to [=layout API containers=]. This is discussed in
 [[#interaction-overflow]].
 
 As the layout is entirely up to the author, properties which are used in other layout modes (e.g.
@@ -159,49 +159,47 @@ Layout API is supported.
 Layout API Container Painting {#painting}
 -----------------------------------------
 
-<a>Layout API Container</a> children paint exactly the same as inline blocks [[!CSS21]], except that
+[=Layout API Container=] children paint exactly the same as inline blocks [[!CSS21]], except that
 the order in which they are returned from the layout method (via
 {{FragmentResultOptions/childFragments}}) is used in place of raw document order, and 'z-index'
 values other than ''z-index/auto'' create a stacking context even if 'position' is ''static''.
 
 Box Tree Transformations {#layout-api-box-tree}
 -----------------------------------------------
 
-The <a>layout API children</a> can act in different ways depending on the value of <a for="document
-layout definition">layout options'</a> {{LayoutOptions/childDisplay}} (set by
-<code>layoutOptions</code> on the class).
+The [=layout API children=] can act in different ways depending on the value of [=document layout
+definition/layout options'=] {{LayoutOptions/childDisplay}} (set by <code>layoutOptions</code> on
+the class).
 
-If the value of <a for="document layout definition">layout options'</a>
-{{LayoutOptions/childDisplay}} is <code>"block"</code> the 'display' value of that child is
-<a>blockified</a>. This is similar to children of <a>flex containers</a> or <a>grid containers</a>.
-See [[!css3-display]].
+If the value of [=document layout definition/layout options'=] {{LayoutOptions/childDisplay}} is
+<code>"block"</code> the 'display' value of that child is [=blockified=]. This is similar to
+children of [=flex containers=] or [=grid containers=]. See [[!css3-display]].
 
-If the value of <a for="document layout definition">layout options'</a>
-{{LayoutOptions/childDisplay}} is <code>"normal"</code>, no <a>blockification</a> occurs. Instead
-children with a <<display-outside>> <a>computed value</a> of ''inline'' (a <a>root inline box</a>)
-will produce a single {{LayoutFragment}} representing each line when
-{{LayoutChild/layoutNextFragment()}} is called.
+If the value of [=document layout definition/layout options'=] {{LayoutOptions/childDisplay}} is
+<code>"normal"</code>, no [=blockification=] occurs. Instead children with a <<display-outside>>
+[=computed value=] of ''inline'' (a [=root inline box=]) will produce a single {{LayoutFragment}}
+representing each line when {{LayoutChild/layoutNextFragment()}} is called.
 
 Note: This allows authors to adjust the available inline size of each line, and position each line
     separately.
 
-Children of a {{LayoutChild}} which represents <a>root inline box</a> also have some additional
+Children of a {{LayoutChild}} which represents [=root inline box=] also have some additional
 transformations.
 
- - A <a>block-level</a> box inside a <a>inline-level</a> box is <a>inlinified</a> I.e. its
+ - A [=block-level=] box inside a [=inline-level=] box is [=inlinified=] I.e. its
      <<display-outside>> is set to ''inline''.
 
- - A <a>float</a> inside a <a>inline-level</a> box is not taken out of flow. Instead it must be
-     treated as inflow, and be <a>inlinified</a>.
+ - A [=float=] inside a [=inline-level=] box is not taken out of flow. Instead it must be treated as
+     inflow, and be [=inlinified=].
 
-In both of the above cases the children become <a>atomic inlines</a>.
+In both of the above cases the children become [=atomic inlines=].
 
 Note: User agents would not perform any "inline splitting" or fragmenting when they encounter a
-    <a>block-level</a> box.
+    [=block-level=] box.
 
 <div class="note">
     Note: In the example below "inline-span" would be represented as a single {{LayoutChild}} with
-    both "block" and "float" being <a>atomic inlines</a>.
+    both "block" and "float" being [=atomic inlines=].
     <pre class="lang-html">
         &lt;span id="inline-span">
           Text