[css-inline] Fix markup errors

Author: fantasai

css-inline/Overview.bs

@@ -34,7 +34,7 @@ At Risk: the 'initial-letter-wrap' property
 
 Issue: The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added.
 
-<h3 id="dominant-baseline property">
+<h3 id="dominant-baseline-property">
 Dominant Baselines: the 'dominant-baseline' property</h3>
 
 	<pre class="propdef">
@@ -228,7 +228,7 @@ Alignment Shift: 'baseline-shift' longhand</h4>
 		(The UA should use the parent’s font data to find this offset whenever possible.)
 	</dl>
 
-	<p>User agents <em>may</em> additionally support the keyword <dfn for=baseline-shift type=value>baseline</dfn>
+	<p>User agents <em>may</em> additionally support the keyword <dfn for=baseline-shift>baseline</dfn>
 	as computing to ''0''
 	if is necessary for them to support legacy SVG content.
 	Issue: We would prefer to remove this, and are looking for feedback from SVG user agents as to whether it's necessary.

css-inline/Overview.html

@@ -110,7 +110,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="status"><span class="conten
 	W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/32061/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group;
 	that page also includes instructions for disclosing a patent.
 	An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>. </p>
-   <p> This document is governed by the <a href="http://www.w3.org/2014/Process-20140801/" id="w3c_process_revision">1 August 2014 W3C Process Document</a>. </p>
+   <p> This document is governed by the <a href="http://www.w3.org/2015/Process-20150901/" id="w3c_process_revision">1 September 2015 W3C Process Document</a>. </p>
    <p></p>
   </div>
   <div data-fill-with="at-risk">
@@ -126,7 +126,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="cont
     <li>
      <a href="#line-height"><span class="secno">1</span> <span class="content">Line Heights and Baseline Alignment</span></a>
      <ul class="toc">
-      <li><a href="#dominant-baseline property"><span class="secno">1.1</span> <span class="content"> Dominant Baselines: the <span class="property">dominant-baseline</span> property</span></a>
+      <li><a href="#dominant-baseline-property"><span class="secno">1.1</span> <span class="content"> Dominant Baselines: the <span class="property">dominant-baseline</span> property</span></a>
       <li>
        <a href="#transverse-alignment"><span class="secno">1.2</span> <span class="content"> Transverse Box Alignment: the <span class="property">vertical-align</span> property</span></a>
        <ul class="toc">
@@ -210,7 +210,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="cont
    <h2 class="heading settled" data-level="1" id="line-height"><span class="secno">1. </span><span class="content">Line Heights and Baseline Alignment</span><a class="self-link" href="#line-height"></a></h2>
    <p class="issue" id="issue-6ab9884f"><a class="self-link" href="#issue-6ab9884f"></a>This section is being rewritten. Refer to <a href="http://www.w3.org/TR/CSS2/visudet.html#line-height">section 10.8</a> of <a data-link-type="biblio" href="#biblio-css21">[CSS21]</a> for the normative CSS definition or the <a href="http://www.w3.org/TR/2002/WD-css3-linebox-20020515/">2002 Working Draft</a> if you want pretty pictures. (But ignore the old text, half of it’s wrong. We’re not specifying which half, that’s to be determined.) <strong>The CSS2 specification should be used as the guideline for implementation.</strong></p>
    <p class="issue" id="issue-95a9f423"><a class="self-link" href="#issue-95a9f423"></a> The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added.</p>
-   <h3 class="heading settled" data-level="1.1" id="dominant-baseline property"><span class="secno">1.1. </span><span class="content"> Dominant Baselines: the <a class="property" data-link-type="propdesc" href="#propdef-dominant-baseline">dominant-baseline</a> property</span><a class="self-link" href="#dominant-baseline%20property"></a></h3>
+   <h3 class="heading settled" data-level="1.1" id="dominant-baseline-property"><span class="secno">1.1. </span><span class="content"> Dominant Baselines: the <a class="property" data-link-type="propdesc" href="#propdef-dominant-baseline">dominant-baseline</a> property</span><a class="self-link" href="#dominant-baseline-property"></a></h3>
    <table class="definition propdef" data-link-for-hint="dominant-baseline">
     <tbody>
      <tr>
@@ -415,7 +415,7 @@ <h4 class="heading settled" data-level="1.2.2" id="baseline-shift-property"><spa
     <dd>Raise by the offset appropriate for superscripts of the parent’s box.
 		(The UA should use the parent’s font data to find this offset whenever possible.) 
    </dl>
-   <p>User agents <em>may</em> additionally support the keyword <dfn data-dfn-for="baseline-shift" data-dfn-type="dfn" data-noexport="" id="baseline" type="value">baseline<a class="self-link" href="#baseline"></a></dfn> as computing to <span class="css">0</span> if is necessary for them to support legacy SVG content.
+   <p>User agents <em>may</em> additionally support the keyword <dfn data-dfn-for="baseline-shift" data-dfn-type="dfn" data-noexport="" id="baseline">baseline<a class="self-link" href="#baseline"></a></dfn> as computing to <span class="css">0</span> if is necessary for them to support legacy SVG content.
 	Issue: We would prefer to remove this, and are looking for feedback from SVG user agents as to whether it’s necessary. </p>
    <h2 class="heading settled" data-level="2" id="initial-letter-styling"><span class="secno">2. </span><span class="content"> Initial Letters</span><a class="self-link" href="#initial-letter-styling"></a></h2>
    <p class="issue" id="issue-f90429eb"><a class="self-link" href="#issue-f90429eb"></a>The editors would appreciate any examples of drop initials in non-western scripts, especially Arabic and Indic scripts.</p>