Original text:
3.5.8. <del> The list selector allows combining member names, array indices, and slices in a single selector. Note: The list selector was called "union selector" in JSONPath-orig, as it was intended to solve use cases addressed by the union selector in XPath.  However, the term "union" has the connotation of a set operation that involves merging input sets while avoiding duplicates, so the concept was renamed into "list selector". </del> 3.5.8.1. <del> The list selector is syntactically related to the "index-selector" and the "slice-selector".  It contains two or more entries, separated by commas. 3.5.8.2. A list selector selects the nodes that are selected by at least one of the selector entries in the list and yields the concatenation of the lists (in the order of the selector entries) of nodes selected by the selector entries.  Note that any node selected in more than one of the selector entries is kept as many times in the node list. To be valid, integer values in the "element-index" and "slice-index" components MUST be in the I-JSON range of exact values, see synsem- overview. 3.5.9. 3.5.9.1. </del> The filter selector has the form "[?<expr>]".  It works via iterating over structured values, i.e. arrays and objects. precedence from highest (binds most tightly) to lowest (binds least tightly). <del> 3.5.9.2. </del>  The "filter-selector" works with arrays and objects exclusively.  Its result might be a list of Some examples:  3.6. A Normalized Path is a JSONPath with restricted syntax that

Reviewer comments:
To do: [x] Consider reorganising selectors in section 3.3 to match the order of the document [x] Consider reorganising table 1 to match the order of the document Fixes URL
Reorganised selectors in section 3.3 to match the order of the document. Did not reorganise table 1 as it flows better as is.
Filter selectors should come before list selectors to avoid a forward reference. The following comment should be deleted: Also, as noted by NAME at today's interim WG meeting, we should factor out a separate production to avoid repeating here: and here: Possible names for this production: or .
I think we proposed something like ... and here: thanks.
(And once we are don't with this issue, we can reorder table 1. Not quite sure if we want to do this entirely in section order; let's see how that turns out first.)

Revised text:
3.5.8.  3.5.8.1.  The filter selector has the form "[?<expr>]".  It works via iterating over structured values, i.e. arrays and objects. precedence from highest (binds most tightly) to lowest (binds least tightly).  <ins> 3.5.8.2. </ins> The "filter-selector" works with arrays and objects exclusively.  Its result might be a list of Some examples: <ins> 3.5.9. The list selector allows combining member names, array indices, and slices in a single selector. Note: The list selector was called "union selector" in JSONPath-orig, as it was intended to solve use cases addressed by the union selector in XPath.  However, the term "union" has the connotation of a set operation that involves merging input sets while avoiding duplicates, so the concept was renamed into "list selector". 3.5.9.1. The list selector is syntactically related to the "index-selector" and the "slice-selector".  It contains two or more entries, separated by commas. 3.5.9.2. A list selector selects the nodes that are selected by at least one of the selector entries in the list and yields the concatenation of the lists (in the order of the selector entries) of nodes selected by the selector entries.  Note that any node selected in more than one of the selector entries is kept as many times in the node list. To be valid, integer values in the "element-index" and "slice-index" components MUST be in the I-JSON range of exact values, see synsem- overview. </ins> 3.6. A Normalized Path is a JSONPath with restricted syntax that