[css-grid] Add issue.

Author: tabatkins

css-grid/Overview.html

@@ -2372,8 +2372,9 @@ <h3 class="heading settled heading" data-level=9.2 id=row-align><span class=secn
 		the inline axis is horizontal,
 		and so the <a class=property data-link-type=propdesc title=justify-*>justify-*</a> properties align the <a data-link-type=dfn href=#grid-item title="grid items">grid items</a> horizontally.
 
-		<pre>TODO: provide example
-</pre>	</div>
+		<p class=issue id=issue-3a8dda12><a class=self-link href=#issue-3a8dda12></a>
+			TODO: provide example
+	</div>
 
 
 <h3 class="heading settled heading" data-level=9.3 id=column-align><span class=secno>9.3 </span><span class=content>
@@ -3333,6 +3334,8 @@ <h2 class="no-num heading settled" id=issues-index><span class=content>Issues In
 		instead of always using 1,1 by default.
 
 <a href=#issue-4e6cc4f1> ↵ </a></div><div class=issue>
+			TODO: provide example
+	<a href=#issue-3a8dda12> ↵ </a></div><div class=issue>
 			Currently this algorithm embodies several heuristics which regulate the growth of spanning <a data-link-type=dfn href=#grid-item title="grid items">Grid items</a> to accommodate certain use cases. (E.g. the game example in Figures 2 and 3 above.) These heuristics should be a normative part of this specification to ensure interoperability. To the extent additional use cases can be identified that cannot be satisfied by following the current heuristics, the normative algorithm can be updated, or additional mechanisms can be introduced for fine-grained control of content-based TrackSizingFunction.
 
 		<a href=#issue-7a82b645> ↵ </a></div><div class=issue>

css-grid/Overview.src.html

@@ -2425,9 +2425,8 @@ <h3 id='row-align'>
 		the inline axis is horizontal,
 		and so the 'justify-*' properties align the <a>grid items</a> horizontally.
 
-		<pre>
-TODO: provide example
-		</pre>
+		<p class='issue'>
+			TODO: provide example
 	</div>