[css-scoping-2] Remove inaccurate implied-ancestor mentions

Author: mirisuzanne

css-scoping-2/Overview.bs

@@ -215,14 +215,14 @@ The in-scope pseudo-class '':in()''</h3>
 		</pre>
 
 		Without any such lower boundaries,
-		the ''in()'' pseudo-class is similar to other descendant selectors.
+		the ''in()'' pseudo-class is similar to other existing selectors.
 		These three selectors will all select the same elements,
 		with the same specificity:
 
 		<pre class=lang-css>
 		.child:in(.ancestor) { color: darkmagenta; }
-		.child:is(.ancestor *) { color: darkmagenta; }
-		.ancestor .child { color: darkmagenta; }
+		.child:is(.ancestor, .ancestor *) { color: darkmagenta; }
+		.ancestor.child, .ancestor .child { color: darkmagenta; }
 		</pre>
 	</div>
 
@@ -256,17 +256,14 @@ Scoping Styles in CSS: the ''@scope'' rule</h3>
 
 	* [=scoped selectors|Selectors are scoped=] to the [=scope=] in question,
 		with the [=:scope element=] being the [=scoping root=].
-	* The '':scope'' pseudo-class takes on the <dfn>scope specificity</dfn> of
+	* Selectors are given the added specificity of
 		the most specific [=complex selector=] in the <<scope-start>> argument.
-	* Any selector that does not include an explicit '':scope'' pseudo-class
-		has an implicit '':scope'' ancestor prepended to the selector,
-		so that the [=scope specificity=] is applied to every selector in the <<stylesheet>>.
+		This is designed to match the behavior of the '':in()'' and '':is()'' selectors.
 	* The cascade prioritizes rules with a [=scope proximity|more proximate=] [=scoping root=],
 		regardless of source order.
 
 	<div class=example>
-		The following selectors have the same specificity (1,0,1),
-		and match the same elements:
+		The following selectors have the same specificity (1,0,1):
 
 		<pre class=lang-css>
 		@scope (#hero) {