[css-grid-3][masonry][editorial] Align placement terminology with CSS Grid specs.

Author: fantasai

css-grid-3/Overview.bs

@@ -564,7 +564,7 @@ Subgrids</h3>
 
 		Note how the subgrid's first item ("subgrid.1") contributes
 		to the intrinsic size of the 2nd row in the parent grid.
-		This is possible since the subgrid specified a definite placement
+		This is possible since the subgrid specified a definite position
 		so we know which tracks it will occupy.
 		Note also that trying to subgrid the parent's [=masonry axis=]
 		results in the subgrid getting [=masonry layout=] in its [=inline axis=].
@@ -629,20 +629,20 @@ Grid Axis Track Sizing</h3>
 	Track sizing works the same as in [[css-grid-2#algo-track-sizing|CSS Grid]],
 	except that when considering which items contribute to intrinsic sizes:
 	* All items explicitly placed in that track contribute, and
-	* All items without an explicit placement contribute
+	* All items with an [=automatic grid position=] contribute
 		(regardless of whether they are ultimately placed in that track).
 
 	<div class="example">
 		For example, suppose there are two columns in the [=grid axis=]
 		and that
-		* Items A, B, and C have no explicit placement.
+		* Items A, B, and C have no explicit position.
 		* Item D is explicitly placed into the first column.
 
 		In this case, items A, B, C, and D all contribute to sizing the first column,
 		while only A, B, and C (and not D) contribute to the second column.
 	</div>
 
-	In the case of spanning items with no explicit placement,
+	In the case of spanning items with an [=automatic grid position=],
 	they are assumed to be placed at every possible start position,
 	and contribute accordingly.
 
@@ -680,8 +680,9 @@ Masonry Placement</h3>
 
 	In the [=grid axis=],
 	items can be <em>explicitly placed</em> into tracks and span them using the familiar [=grid-placement properties=]’ syntax.
-	[=Auto-placement=], however, uses the [[#masonry-layout-algorithm]],
-	placing each item into the “shortest” masonry track available.
+	Auto-placement, however, uses the [[#masonry-layout-algorithm]],
+	placing each item with an [=automatic grid position=]
+	into the “shortest” masonry track available.
 
 	<div class="example">
 		Here's a masonry layout <a href="examples/pinterest-with-span.html">example</a>
@@ -772,12 +773,12 @@ Masonry Layout and Placement Algorithm</h3>
 	For each item in [=order-modified document order=]:
 	<ol>
 		<li>
-			If the item has an definite placement in the [=grid axis=],
+			If the item has a [=definite grid position=] in the [=grid axis=],
 			use that placement.
 
 			ISSUE: Should this also update the placement cursor?
 
-Otherwise, resolve its [=grid axis=] placement using these substeps:
+			Otherwise, resolve its [=grid axis=] placement using these substeps:
 
 			<ol>
 				<li>Starting at the first [=grid axis=] line in the [=implicit grid=],
@@ -789,7 +790,7 @@ Otherwise, resolve its [=grid axis=] placement using these substeps:
 				<li>Let |possible lines| be the line that resulted in the smallest <var>max_pos</var>,
 					and all lines that result in a <var>max_pos</var> within the [=tie threshold=] of this <var>max_pos</var>.
 				<li>Choose the first line in |possible lines| greater than or equal to the [=auto-placement cursor=]
-					as the item's definite placement in the [=grid axis=];
+					as the item's position in the [=grid axis=];
 					or if there are none such, choose the first one.
 				<li>Update the [=auto-placement cursor=] to point to item's last line.
 			</ol>