simonwuelker
diff --git a/‎css-tables-3/Overview.bs‎
Lines changed: 20 additions & 5 deletions b/‎css-tables-3/Overview.bs‎
Lines changed: 20 additions & 5 deletions
@@ -13,7 +13,6 @@ Former editor: Bert Bos, W3C
 Former editor: David Baron, Mozilla
 Former editor: Markus Mielke, Microsoft
 Former editor: Saloni Mira Rai, Microsoft
-!Issue Tracking: <a href="https://github.com/gregwhitworth/css-table-3/issues">Github</a>
 Abstract: This CSS module defines a two-dimensional grid-based layout system, optimized for tabular data rendering. In the table layout model, each display node is assigned to an intersection between a set of consecutive rows and a set of consecutive columns, themselves generated from the table structure and sized according to their content.
 Ignored Terms: block-level box
 </pre>
@@ -2381,15 +2380,22 @@ spec:css21; type:property; text:max-width
 
 		<p>
 			When a table doesn't fit entirely in a fragmentainer,
-				the user agent has to insert some horizontal gap 
+				the user agent has to insert some vertical gap 
 				between the rows located before and at the overflow point
 				such that the two rows end up separated in sibling fragmentainers.
+		
+		<p class="issue">
+			Add a figure clarifying this.	
+		
 		<p>
-			When there is no row fitting entirely the current fragmentainer,
+			When there is no row fitting entirely in the current fragmentainer,
 				user agents must split each cell of the row among the two fragmentainers
-				so that all fragments preserve the same height.
+				so that all fragments in the same fragmentainer preserve the same height.
 			Then, the user agent must fragment the content of each cell 
 				among its two fragments in parallel. 
+				
+		<p class="issue">
+			Add a figure clarifying this.
 
 		<p>
 			When 'break-before' or 'break-after' is applied 
@@ -2404,10 +2410,15 @@ spec:css21; type:property; text:max-width
 
 		<p>
 			When rendering the document into a paged media, 
-				user agents should repeat 
+				user agents must repeat 
 					<a href="#table-header-group">header rows</a> and 
 					<a href="#table-footer-group">footer rows</a>  
 				on each page spanned by a table.
+				
+		<p>
+			When the header rows are being repeated, user agents must 
+				leave room and potentially render the table top border.
+			The same applies for footer rows and the table bottom border.
 
 		<p>
 			When doing so doesn't leave enough space to insert at least one content row,
@@ -2416,6 +2427,10 @@ spec:css21; type:property; text:max-width
 		<p>
 			When doing so still doesn't leave enough space to insert at least one content row,
 				users agents must drop the repeated header.
+				
+		<p class="issue">
+			Should we just remove the text about paged media,
+				and extend this to every fragmentation context?
 
 <!--------------------------------------------------------------------------------->
 <h2 id="security">Security Considerations</h2>