[css-navigation-1] Rename route to navigation in most places.

This is per the resolution in:
#12594 (comment)

Author: dbaron

css-navigation-1/Overview.bs

@@ -35,16 +35,16 @@ url: https://html.spec.whatwg.org/multipage/browsing-the-web.html#has-been-revea
 	type: dfn; spec: html; text: has been revealed;
 </pre>
 
-<h2 id="condional-route-queries">Conditional rules for route queries</h2>
+<h2 id="condional-navigatio-queries">Conditional rules for navigatio queries</h2>
 
-<h3 id="at-route">Route queries: the ''@route'' rule</h3>
+<h3 id="at-navigation">Navigation queries: the ''@navigation'' rule</h3>
 
-The <dfn at-rule id="at-ruledef-route">@route</dfn> rule
+The <dfn at-rule id="at-ruledef-navigation">@navigation</dfn> rule
 is a conditional group rule
 whose condition tests
 characteristics of the current URL
 or of the state of navigation between two URLs.
-These queries are called <dfn export>route queries</dfn>.
+These queries are called <dfn export>navigation queries</dfn>.
 
 Authors can use it to:
 * write style sheets that apply to multiple pages
@@ -57,37 +57,37 @@ Authors can use it to:
 	(or make other appropriate style changes)
 	in response to navigations.
 
-The syntax of the condition in the ''@route'' rule
+The syntax of the condition in the ''@navigation'' rule
 is similar to that defined for
 <<supports-condition>> in [[CSS-CONDITIONAL-3]].
 Negation, conjunction, and disjunction are all needed
 so that authors can specify the interaction of multiple styles
 in ways that are most intuitive and require the simplest code.
 
-The syntax of the ''@route'' rule is:
+The syntax of the ''@navigation'' rule is:
 
 <pre class="prod def" nohighlight>
-@route <<route-condition>> {
+@navigation <<navigation-condition>> {
 	<<rule-list>>
 }
 </pre>
 
-with <<route-condition>> defined as:
+with <<navigation-condition>> defined as:
 
 <pre class="prod def" dfn-type="type" nohighlight>
-	<dfn><<route-condition>></dfn> = not <<route-in-parens>>
-	                     | <<route-in-parens>> [ and <<route-in-parens>> ]*
-	                     | <<route-in-parens>> [ or <<route-in-parens>> ]*
-	<dfn><<route-in-parens>></dfn> = ( <<route-condition>> ) | ( <<route-test>> ) | <<general-enclosed>>
-	<dfn><<route-test>></dfn> = <<route-location>> | <<route-keyword>> : <<route-location>>
-	<dfn><<route-keyword>></dfn> = at | from | to
-	<dfn><<route-location>></dfn> = <<urlpattern()>>
+	<dfn><<navigation-condition>></dfn> = not <<navigation-in-parens>>
+	                     | <<navigation-in-parens>> [ and <<navigation-in-parens>> ]*
+	                     | <<navigation-in-parens>> [ or <<navigation-in-parens>> ]*
+	<dfn><<navigation-in-parens>></dfn> = ( <<navigation-condition>> ) | ( <<navigation-test>> ) | <<general-enclosed>>
+	<dfn><<navigation-test>></dfn> = <<navigation-location>> | <<navigation-keyword>> : <<navigation-location>>
+	<dfn><<navigation-keyword>></dfn> = at | from | to
+	<dfn><<navigation-location>></dfn> = <<urlpattern()>>
 </pre>
 
 The above grammar is purposely very loose for forwards-compatibility reasons,
 since the <<general-enclosed>> production
 allows for substantial future extensibility.
-Any ''@route'' rule that does not parse according to the grammar above
+Any ''@navigation'' rule that does not parse according to the grammar above
 (that is, a rule that does not match this loose grammar
 which includes the <<general-enclosed>> production)
 is invalid.
@@ -97,31 +97,31 @@ processors <strong>must</strong> ignore such a rule (including all of its conten
 Many of these grammar terms are associated with a boolean result,
 as follows:
 
-: <<route-condition>>
-::	: not <<route-in-parens>>
-	:: The result is the negation of the <<route-in-parens>> term.
+: <<navigation-condition>>
+::	: not <<navigation-in-parens>>
+	:: The result is the negation of the <<navigation-in-parens>> term.
 
-	: <<route-in-parens>> [ and <<route-in-parens>> ]*
+	: <<navigation-in-parens>> [ and <<navigation-in-parens>> ]*
 	::
-		The result is true if all of the <<route-in-parens>> child terms are true,
+		The result is true if all of the <<navigation-in-parens>> child terms are true,
 		and false otherwise.
 
-	: <<route-in-parens>> [ or <<route-in-parens>> ]*
+	: <<navigation-in-parens>> [ or <<navigation-in-parens>> ]*
 	::
-		The result is false if all of the <<route-in-parens>> child terms are false,
+		The result is false if all of the <<navigation-in-parens>> child terms are false,
 		and true otherwise.
 
-: <<route-in-parens>>
+: <<navigation-in-parens>>
 :: The result is the result of the child subexpression.
 
-: <<route-test>>
-::	: <<route-location>>
-	: at: <<route-location>>
+: <<navigation-test>>
+::	: <<navigation-location>>
+	: at: <<navigation-location>>
 	:: The result is true if
 		the document's [=Document/URL=] [=URL pattern/match|matches=]
-		the [=route location URL pattern=] of <<route-location>>.
+		the [=navigation location URL pattern=] of <<navigation-location>>.
 
-	: from: <<route-location>>
+	: from: <<navigation-location>>
 	:: The result is true if
 		the [=document's navigation API=] of the document
 		is non-null, and either:
@@ -130,7 +130,7 @@ as follows:
 			its [=from entry=]'s {{NavigationHistoryEntry/url}}
 			is non-null and
 			[=URL pattern/match|matches=]
-			the [=route location URL pattern=] of <<route-location>>.
+			the [=navigation location URL pattern=] of <<navigation-location>>.
 
 		* its [=activation=] is non-null,
 			the document's [=has been revealed=] is false or
@@ -139,9 +139,9 @@ as follows:
 			{{NavigationHistoryEntry/url}}'s
 			is non-null and
 			[=URL pattern/match|matches=]
-			the [=route location URL pattern=] of <<route-location>>.
+			the [=navigation location URL pattern=] of <<navigation-location>>.
 
-	: to: <<route-location>>
+	: to: <<navigation-location>>
 	:: The result is true if
 		the [=document's navigation API=] of the document
 		is non-null, and either:
@@ -150,7 +150,7 @@ as follows:
 			and its {{NavigateEvent/destination}}'s
 			{{NavigationDestination/url}}
 			[=URL pattern/match|matches=]
-			the [=route location URL pattern=] of <<route-location>>.
+			the [=navigation location URL pattern=] of <<navigation-location>>.
 
 			ISSUE: This assumes that the [=ongoing navigate event=]
 			and the [=transition=] have the same lifetime,
@@ -169,7 +169,7 @@ as follows:
 			{{NavigationHistoryEntry/url}}'s
 			is non-null and
 			[=URL pattern/match|matches=]
-			the [=route location URL pattern=] of <<route-location>>.
+			the [=navigation location URL pattern=] of <<navigation-location>>.
 
 		TODO: Update this definition to handle redirects better.
 		In particular, we'd like the ''to:'' URL to change
@@ -190,16 +190,16 @@ as follows:
 
 	Authors must not use <<general-enclosed>> in their stylesheets.
 	<span class='note'>It exists only for future-compatibility,
-	so that new syntax additions do not invalidate too much of a <<route-condition>> in older user agents.</span>
+	so that new syntax additions do not invalidate too much of a <<navigation-condition>> in older user agents.</span>
 
-The <dfn>route location URL pattern</dfn> of a <<route-location>>
-depends on the type of <<route-location>>:
+The <dfn>navigation location URL pattern</dfn> of a <<navigation-location>>
+depends on the type of <<navigation-location>>:
 
 : <<urlpattern()>>
 ::	The [=URL pattern=] represented by the function; see
 	[=create a URL pattern for urlpattern()=].
 
-ISSUE: There is currently only one type of <<route-location>>
+ISSUE: There is currently only one type of <<navigation-location>>
 but we should consider adding another,
 which would be just a name that references
 a name defined in a routemap.
@@ -216,34 +216,34 @@ the result of the following steps on <var>document</var>:
 
 1. Return <var>window</var>'s [=navigation API=].
 
-The condition of the ''@route'' rule
-is the result of the <<route-condition>> in its prelude.
+The condition of the ''@navigation'' rule
+is the result of the <<navigation-condition>> in its prelude.
 
-<h3 id="route-when-function">The ''@when/route()'' function for ''@when''</h3>
+<h3 id="navigation-when-function">The ''@when/navigation()'' function for ''@when''</h3>
 
 This specification defines an additional function for the ''@when'' rule:
 
 <pre class="prod">
-<dfn for="@when" function>route()</dfn> = route( <<route-condition>> )
+<dfn for="@when" function>navigation()</dfn> = navigation( <<navigation-condition>> )
 </pre>
 
-The ''@when/route()'' function is associated with the boolean result that
+The ''@when/navigation()'' function is associated with the boolean result that
 its contained condition is associated with.
 
-<h3 id="route-if-function">The ''if()/route()'' function for ''if()''</h3>
+<h3 id="navigation-if-function">The ''if()/navigation()'' function for ''if()''</h3>
 
 This specification defines an additional function for the ''if()'' function's
 <<if-test>> production:
 
 <pre class="prod">
-<dfn for="if()" function>route()</dfn> = route( <<route-condition>> )
+<dfn for="if()" function>navigation()</dfn> = navigation( <<navigation-condition>> )
 </pre>
 
 ISSUE: This should probably have a more formal definition of the function,
 but I can't find the formal definitions of the existing ''if()'' functions
 to model it after.
 
-<h2 id="link-route-pseudo-classes">Pseudo-classes for route-related links</h2>
+<h2 id="link-navigation-pseudo-classes">Pseudo-classes for navigation-related links</h2>
 
 TODO: To be written.
 
@@ -275,7 +275,7 @@ using the steps of the <dfn>create a URL pattern for urlpattern()</dfn> algorith
 
 	<div class="issue">
 	Do we want this to be the base URL all the time?
-	For use of ''urlpattern()'' in ''@route'',
+	For use of ''urlpattern()'' in ''@navigation'',
 	it's likely more useful for the base URL
 	to be the document URL rather than the style sheet URL.
 	However, it would be very awkward for ''urlpattern()''