[css-grid] Prep for WD; tweak issue wording; mark sample algorithm as explicitly non-normative as intended (and evidenced in the title).

Author: fantasai

css-grid/Overview.bs

@@ -1,8 +1,10 @@
 <h1>CSS Grid Layout Module Level 1</h1>
 
 <pre class='metadata'>
-Status: ED
-Work Status: Refining
+Deadline: 2017-06-30
+Date: 2016-09-30
+Status: CR
+Work Status: Testing
 Shortname: css-grid
 Level: 1
 Group: csswg
@@ -895,7 +897,9 @@ Sizing Grid Containers</h3>
 
 	In both inline and block formatting contexts,
 	the <a>grid container</a>’s ''auto'' <a>block size</a> is its max-content size.
-	<span class="issue">The block layout spec should define this?</span>
+
+	<span class="note">The block layout spec should probably define this,
+	but it isn't written yet.</span>
 
 	The <a>max-content size</a> of a <a>grid container</a> is
 	the sum of the <a>grid container’s</a> track sizes (including gutters)
@@ -3599,8 +3603,9 @@ Grid Sizing Algorithm</h3>
 			had that size and all other rows were infinite.
 
 		<div class="issue">
-			Alternatively, we could
-			assume the <a>available space</a> that it would have as the maximum of:
+			Would it help to have <a href="https://lists.w3.org/Archives/Public/www-style/2016Jan/0128.html">heuristics</a>
+			that attempt a more accurate initial estimate?
+			E.g. assuming the <a>available space</a> that it would have as the maximum of:
 
 			<ul>
 				<li>
@@ -3622,8 +3627,8 @@ Grid Sizing Algorithm</h3>
 					or a ''max-content'', ''auto'', or <<flex>> max sizing function.
 			</ul>
 
-			This is likely to reduce the amount of re-layout passes that are necessary,
-			but will it produce a different result in any cases?
+			This is may reduce the amount of re-layout passes that are necessary,
+			but will it produce a different or better result in any cases?
 			Should we adopt it into the spec?
 		</div>
 
@@ -3645,10 +3650,6 @@ Grid Sizing Algorithm</h3>
 				and <a spec=css-multicol>multi-column elements</a>.
 			</div>
 
-			Issue: Is one cycle enough?
-
-			Issue: Would it help to have <a href="https://lists.w3.org/Archives/Public/www-style/2016Jan/0128.html">smarter heuristics</a> for the initial size calculation?
-
 		<li>
 			Finally, the <a>grid container</a> is sized
 			using the resulting size of the <a>grid</a> as its content size,
@@ -4193,10 +4194,12 @@ Fragmenting Grid Layout</h2>
 <h3 id="fragmentation-alg">
 Sample Fragmentation Algorithm</h3>
 
-	<p class="issue">
-		This is just a rough draft.
-		This section needs to be severely cross-checked with the [[CSS-FLEXBOX-1]] algorithm.
-		Feedback overall is welcome; please reference the rules above instead as implementation guidance.
+	<p><em>This section is non-normative.</em>
+
+	<p class="note">
+		This is a rough draft of one possible fragmentation algorithm,
+		and still needs to be severely cross-checked with the [[CSS-FLEXBOX-1]] algorithm for consistency.
+		Feedback is welcome; please reference the rules above instead as implementation guidance.
 
 	<ol>
 		<li>