w3c
diff --git a/‎css-grid-3/Overview.bs
-8 b/‎css-grid-3/Overview.bs
-8
diff --git a/‎css-grid-3/examples/align-tracks-example-1.html
-105 b/‎css-grid-3/examples/align-tracks-example-1.html
-105
diff --git a/‎css-grid-3/examples/align-tracks-example-2.html
-59 b/‎css-grid-3/examples/align-tracks-example-2.html
-59
diff --git a/‎css-grid-3/examples/graceful-degradation-example.html
-1 b/‎css-grid-3/examples/graceful-degradation-example.html
-1
diff --git a/‎css-grid-3/examples/justify-tracks-example-1.html
-1 b/‎css-grid-3/examples/justify-tracks-example-1.html
-1
diff --git a/‎css-grid-3/examples/masonry-axis-alignment-1.html
-77 b/‎css-grid-3/examples/masonry-axis-alignment-1.html
-77
diff --git a/‎css-grid-3/examples/masonry-axis-baseline-alignment-1.html
-2 b/‎css-grid-3/examples/masonry-axis-baseline-alignment-1.html
-2
@@ -693,9 +693,6 @@ Performance Notes</h2>
 	Any intrinsic track sizing in the [=grid axis=] should be cheaper too,
 	because, typically, only a subset of items contribute to the intrinsic sizing in a masonry layout,
 	contrary to a 2-axis grid where all items spanning an intrinsically-sized track contribute.
-	That said, ''justify/align-tracks: stretch'' specifically
-	adds a cost proportionate to the number of items that are resized.
-	(Note that ''align-tracks/stretch'' isn't the default value for these properties though.)
 	Stretched items do a second layout with the new size (when it actually changed)
 	so this can be costly if there are a huge amount of stretched items
 	that each contains a lot of content.
@@ -707,11 +704,6 @@ Performance Notes</h2>
 	e.g. specifying ''justify/align-items:start''
 	and then opting in for just a few items with ''justify/align-self:stretch''
 	to let those items fill the [=masonry axis=].
-	Other 'justify-tracks' / 'align-tracks' values
-	such as ''align-self/center'', ''align-self/end'' and '<<content-distribution>>'
-	(other than ''align-self/stretch'')
-	shouldn't be a problem though
-	since they just reposition the items which is fast.
 	(This performance analysis is from a Gecko perspective,
 	but I suspect there's some truth to it for other layout engines as well.)
 
 
@@ -12,7 +12,6 @@
   padding: 10px;
   border: 3px solid;
   background: lightgrey content-box;
-  align-tracks: stretch;
   height: 150px;
   transition: height 6s linear;
 }
 
@@ -11,7 +11,6 @@
   padding: 10px;
   border: 3px solid;
   background: lightgrey content-box;
-  justify-tracks: stretch;
   width: 150px;
   transition: width 6s linear;
 }
 
@@ -11,7 +11,6 @@
 .grid {
   display: inline-grid;
   grid: masonry / repeat(10,auto);
-  align-tracks: start, start, stretch, start, start, end, end, stretch, end, end;
   gap: 3px 1px;
   border: 2px solid;
   height: 400px;
@@ -35,7 +34,6 @@
 .medium { font-size:48pt; }
 </style>
 <body>
-<pre>align-tracks: start, start, stretch, start, start, end, end, stretch, end, end</pre>
 
 <div class="grid">
   <item class="fb" style="padding-bottom: 5px"><div>F</div>x</item>
Original file line number	Diff line number	Diff line change
`@@ -12,7 +12,6 @@`
`12`	`12`	`padding: 10px;`
`13`	`13`	`border: 3px solid;`
`14`	`14`	`background: lightgrey content-box;`
`15`		`- align-tracks: stretch;`
`16`	`15`	`height: 150px;`
`17`	`16`	`transition: height 6s linear;`
`18`	`17`	`}`
Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,6 @@`
`11`	`11`	`padding: 10px;`
`12`	`12`	`border: 3px solid;`
`13`	`13`	`background: lightgrey content-box;`
`14`		`- justify-tracks: stretch;`
`15`	`14`	`width: 150px;`
`16`	`15`	`transition: width 6s linear;`
`17`	`16`	`}`