diff --git a/‎selectors-4/Overview.bs‎
Lines changed: 10 additions & 14 deletions b/‎selectors-4/Overview.bs‎
Lines changed: 10 additions & 14 deletions
@@ -3258,11 +3258,10 @@ Grammar</h2>
 
 	<dfn>&lt;relative-selector></dfn> = <<combinator>>? <<complex-selector>>
 
-	<dfn>&lt;compound-selector></dfn> = <<simple-selector>>+
+	<dfn>&lt;compound-selector></dfn> = [ <<type-selector>>? <<subclass-selector>>*
+	                        [ <<pseudo-element-selector>> <<pseudo-class-selector>>* ]? ]!
 
-	<dfn>&lt;simple-selector></dfn> = <<type-selector>> | <<id-selector>> |
-	                    <<class-selector>> | <<attribute-selector>> |
-	                    <<pseudo-class-selector>> | <<pseudo-element-selector>>
+	<dfn>&lt;simple-selector></dfn> = <<type-selector>> | <<subclass-selector>> | <<pseudo-element-selector>>
 
 
 	<dfn>&lt;combinator></dfn> = '>>' | '>' | '+' | '~' | [ '||' ]
@@ -3271,7 +3270,10 @@ Grammar</h2>
 
 	<dfn noexport>&lt;ns-prefix></dfn> = [ <<ident-token>> | '*' ]? '|'
 
-	<dfn noexport>&lt;wq-name>></dfn> = <<ns-prefix>>? <<ident-token>>
+	<dfn noexport>&lt;wq-name></dfn> = <<ns-prefix>>? <<ident-token>>
+
+	<dfn noexport>&lt;subclass-selector></dfn> = <<id-selector>> | <<class-selector>> |
+	                      <<attribute-selector>> | <<pseudo-class-selector>>
 
 	<dfn>&lt;id-selector></dfn> = <<hash-token>>
 
@@ -3293,9 +3295,6 @@ Grammar</h2>
 	In addition to the above grammar,
 	the following rules apply:
 
-	* A <<compound-selector>> can contain at most one <<type-selector>>,
-		and if it does,
-		that must be the first <<simple-selector>> in it.
 	* White space is forbidden between tokens except:
 		* Around commas (denoted with the <a>#</a> multiplier)
 		* Around or in place of a <<combinator>>
@@ -3315,14 +3314,11 @@ Grammar</h2>
 	makes it difficult to indicate that a grammar term can <em>be</em> whitespace.
 	"Omitting" a combinator is actually just specifying the <a>descendant combinator</a>.
 
-	Note: While, per the grammar,
-	<a>pseudo-elements</a> can appear anywhere in a <<compound-selector>>,
-	and a <<compound-selector>> with a <<pseudo-element-selector>>
-	can appear anywhere in a <<complex-selector>>,
-	in practice the <<pseudo-element-selector>> will only match anything
+	Note: In general,
+	a <<pseudo-element-selector>> is only valid
 	if placed at the end of the last <<compound-selector>>
 	in a <<complex-selector>>.
-	In some circumstances,
+	In some circumstances, however,
 	it can be followed by more <<pseudo-element-selector>>s or <<pseudo-class-selector>>s
 	in the same <<compound-selector>>,
 	but these are specified on a case-by-case basis.