[css-cascade-4][meta] Whoops, actually commit the change about computed value != serialization.

Author: tabatkins

css-cascade-4/Overview.bs

@@ -27,6 +27,7 @@ Include Can I Use Panels: yes
 spec:css-values; type:value; text:ex
 </pre>
 
+
 <h2 id="intro">
 Introduction</h2>
 
@@ -462,17 +463,15 @@ Computed Values</h3>
 	as defined in the “Computed Value” line of the property definition table,
 	generally absolutizing it in preparation for <a>inheritance</a>.
 
-	<div class=note>
-		The <a>computed value</a> is the value that is transferred from parent to child during <a>inheritance</a>.
-		For historical reasons,
-		it is not necessarily the value returned by the {{getComputedStyle()}} function,
-		which sometimes returns <a>used values</a>. [[CSSOM]]
-		Furthermore, the <a>computed value</a> is an abstract data representation:
-		their definitions reflect that data representation,
-		not how that data is serialized.
-		For example, serialization rules often allow omitting certain values which are implied during parsing;
-		but those values are nonetheless part of the <a>computed value</a>.
-	</div>
+	Note: The <a>computed value</a> is the value that is transferred from parent to child during <a>inheritance</a>.
+	For historical reasons,
+	it is not necessarily the value returned by the {{getComputedStyle()}} function,
+	which sometimes returns <a>used values</a>. [[CSSOM]]
+	Furthermore, the <a>computed value</a> is an abstract data representation:
+	their definitions reflect that data representation,
+	not how that data is serialized.
+	For example, serialization rules often allow omitting certain values which are implied during parsing;
+	but those values are nonetheless part of the <a>computed value</a>.
 
 	<div class="example">
 		A <a>specified value</a> can be either absolute (i.e., not relative to another value, as in ''red'' or ''2mm'')