[css-inline] Remove issue that isn't really an issue

Author: fantasai

css-inline/Overview.bs

@@ -180,9 +180,6 @@ Alignment Point: 'alignment-baseline' longhand</h4>
 			Align the bottom of the aligned subtree with the bottom of the line box.
 	</dl>
 
-	Issue: Putting ''alignment-baseline/top'', ''alignment-baseline/center'', and ''alignment-baseline/bottom'' in here is awkward,
-	because they're not really baselines. :/
-
 	SVG implementations <em>may</em> support the following aliases
 	in order to support legacy content:
 	<pre dfn-for=alignment-baseline dfn-type=value>

css-inline/Overview.html

@@ -360,8 +360,6 @@ <h4 class="heading settled" data-level="1.2.1" id="alignment-baseline-property">
     <dt><dfn class="css" data-dfn-for="alignment-baseline" data-dfn-type="value" data-export="" id="valdef-alignment-baseline-bottom">bottom<a class="self-link" href="#valdef-alignment-baseline-bottom"></a></dfn> 
     <dd> Align the bottom of the aligned subtree with the bottom of the line box. 
    </dl>
-   <p class="issue" id="issue-b59edfd8"><a class="self-link" href="#issue-b59edfd8"></a> Putting <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-top">top</a>, <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-center">center</a>, and <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-bottom">bottom</a> in here is awkward,
-	because they’re not really baselines. :/</p>
    <p>SVG implementations <em>may</em> support the following aliases
 	in order to support legacy content:</p>
 <pre><dfn data-dfn-for="alignment-baseline" data-dfn-type="value" data-export="" id="valdef-alignment-baseline-text-before-edge">text-before-edge<a class="self-link" href="#valdef-alignment-baseline-text-before-edge"></a></dfn> = <a data-link-type="maybe" href="#valdef-alignment-baseline-text-top">text-top</a>
@@ -1346,8 +1344,6 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
    <div class="issue"> The CSSWG would like to know which baseline values are necessary: if any can be dropped, or any need to be added.<a href="#issue-95a9f423"> ↵ </a></div>
    <div class="issue"> Should be text-over and text-under instead of text-top and text-bottom,
 	but maybe it’s better not to use those terms for consistency with legacy <a class="property" data-link-type="propdesc" href="#propdef-vertical-align">vertical-align</a>.<a href="#issue-5c2889ea"> ↵ </a></div>
-   <div class="issue"> Putting <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-top">top</a>, <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-center">center</a>, and <a class="css" data-link-type="maybe" href="#valdef-alignment-baseline-bottom">bottom</a> in here is awkward,
-	because they’re not really baselines. :/<a href="#issue-b59edfd8"> ↵ </a></div>
    <div class="issue">The editors would appreciate any examples of drop initials in non-western scripts, especially Arabic and Indic scripts.<a href="#issue-f90429eb"> ↵ </a></div>
    <div class="issue"> Should this be <span class="css">initial-letters</span> (plural) as originally discussed?
 Since it can apply to multiple letters.<a href="#issue-4601aace"> ↵ </a></div>