[css-display-4][editorial] Fixed Bikeshed issues

Author: SebastianZ

css-display-4/Overview.bs

@@ -36,7 +36,9 @@ spec: html;
 	type: dfn;
 		text: rendered legend
 		text: inert
-	type: element; text: a
+	type: element;
+		text: a
+		text: audio
 spec:css-pseudo-4; type:selector;
 	text: ::first-letter
 	text: ::first-line
@@ -230,7 +232,7 @@ Value Definitions</h3>
 ████████  ████  ██████  ██        ████████ ██     ██    ██
 -->
 
-<h2 id='the-display-properties'>
+<h2 id="the-display-properties">
 Box Layout Modes: the 'display' property</h2>
 
 	<pre class="propdef">
@@ -545,7 +547,7 @@ Generating Marker Boxes: the ''list-item'' keyword</h3>
 
 	The <dfn value for="display, <display-list-item>">list-item</dfn> keyword
 	causes the element to generate a ''::marker'' pseudo-element [[!CSS-PSEUDO-4]]
-	with the content specified by its <l spec=css21>'list-style'</l> properties
+	with the content specified by its <code>list-style</code> properties
 	(<a href="https://www.w3.org/TR/CSS2/generate.html#lists">CSS 2.1§12.5 Lists</a>) [[!CSS2]]
 	together with a principal box of the specified type for its own contents.
 
@@ -900,7 +902,7 @@ Animating and Interpolating 'display'</h3>
 -->
 <!--
 
-<h2 id='box-suppress'>
+<h2 id="box-suppress">
 Toggling Box Generation: the 'display-or-not' property</h2>
 
 	<pre class="propdef">
@@ -981,7 +983,7 @@ Toggling Box Generation: the 'display-or-not' property</h2>
  ███████  ██     ██ ████████  ████████ ██     ██
 -->
 
-<h2 id='order-property'>
+<h2 id="order-property">
 Display Order: the 'order' property</h2>
 
 	<pre class='propdef'>
@@ -1163,7 +1165,7 @@ Reordering and Accessibility</h3>
 	A well-implemented spatial navigation feature would need to consider
 	all the layout features of CSS that modify spatial relationships.
 
-<h2 id='reading-flow'>
+<h2 id="reading-flow">
 Reading Order: the 'reading-flow' property</h2>
 
 A <dfn export>reading flow container</dfn> is a block, flex or grid container
@@ -1262,7 +1264,7 @@ ISSUE(9922): Should this property also apply to tables?
 	<div class='example'>
 		In this example there are four grid items,
 		placed on a grid and displayed visually out of DOM order.
-		The 'reading-flow' property has a value of ''grid-rows'',
+		The 'reading-flow' property has a value of ''reading-flow/grid-rows'',
 		and the document is in English.
 		The reading order of these items is therefore
 		"Item 4", "Item 2", "Item 3", "Item 1".
@@ -1349,10 +1351,10 @@ ISSUE(9922): Should this property also apply to tables?
 		In this example there are six grid items,
 		the 'grid-auto-flow' property has a value of ''dense'',
 		therefore items may display out of source order.
-		The 'reading-order' property on the item with a class of 'top' is '-1'
+		The 'reading-order' property on the item with a class of 'top' is <code>-1</code>
 		Therefore Item 4 will be the first item in reading flow.
 		The remaining items will be visited in the order they display in rows,
-		as 'reading-flow' has a value of 'grid-rows'.
+		as 'reading-flow' has a value of ''reading-flow/grid-rows''.
 
 		<pre class="lang-markup">
 		&lt;div class="wrapper"&gt;
@@ -1380,7 +1382,7 @@ ISSUE(9922): Should this property also apply to tables?
 	<div class='example'>
 		In this example there are five direct block-level children of a block container
 		where 'reading-flow' has a value of ''source-order''.
-		The third item has a 'reading-order' value of '-1'.
+		The third item has a 'reading-order' value of <code>-1</code>.
 		The reading flow visits the third item first, then the rest in source order.
 
 		<pre class="lang-markup">
@@ -1591,7 +1593,7 @@ Invisibility: the 'visibility' property</h2>
 -->
 
 
-<h2 id='run-in-layout'>
+<h2 id="run-in-layout">
 Run-In Layout</h2>
 
 	A <dfn export lt="run-in | run-in box">run-in box</dfn>
@@ -1700,7 +1702,7 @@ Run-In Layout</h2>
  ██████   ████████  ███████   ██████   ██████  ██     ██ ██     ██    ██
 -->
 
-<h2 id='glossary' class=no-num>
+<h2 id="glossary" class="no-num">
 Appendix A: Glossary</h2>
 
 	The following terms are defined here for convenience:
@@ -2043,7 +2045,7 @@ Appendix A: Glossary</h2>
  ███████  ██    ██  ███████   ██████   ███████  ██     ██ ████████
 -->
 
-<h2 class="no-num non-normative" id="unbox">
+<h2 id="unbox" class="no-num non-normative">
 Appendix B: Effects of ''display: contents'' on Unusual Elements</h2>
 
 	<em>This section is (currently) non-normative.</em>
@@ -2188,7 +2190,7 @@ MathML Elements {#unbox-mathml}
  ██████  ██        ████████  ██████
 -->
 
-<h2 class=no-num id="box-guidelines">
+<h2 id="box-guidelines" class="no-num">
 Appendix C: Box Construction Guidelines for Spec Authors</h2>
 
 	<em>This section is non-normative guidance for specification authors.</em>
@@ -2214,7 +2216,7 @@ Appendix C: Box Construction Guidelines for Spec Authors</h2>
 		Blockify them first,
 		or otherwise change their box type to one that can establish an [=independent formatting context=].
 
-<h2 class=no-num id="acknowledgments">
+<h2 id="acknowledgments" class="no-num">
 Acknowledgments</h2>
 
 	We would like to thank the many people who have attempted to separate out the disparate details of box generation over the years,
@@ -2244,7 +2246,7 @@ Acknowledgments</h2>
  ██████  ██     ██ ██     ██ ██    ██  ██████   ████████  ██████
 -->
 
-<h2 class=no-num id="changes">
+<h2 id="changes" class="no-num">
 Changes</h2>
 
 <h3 id="recent-changes">
@@ -2272,7 +2274,7 @@ Privacy Considerations</h2>
 This specification introduces no new privacy considerations.
 
 <h3 id="sec" class="no-num">
-Security Considerations</h2>
+Security Considerations</h3>
 
 This specification introduces no new security considerations.