add backticks around use for use declarations

Author: yaahc

src/names/name-resolution.md

@@ -4,7 +4,7 @@ r[names.resolution]
 r[names.resolution.intro]
 _Name resolution_ is the process of tying paths and other identifiers to the declarations of those entities. Names are segregated into different [namespaces], allowing entities in different namespaces to share the same name without conflict. Each name is valid within a [scope], or a region of source text where that name may be referenced. Access to certain names may be restricted based on their [visibility].
 
-Name resolution is split into three stages throughout the compilation process. The first stage, *expansion-time resolution*, resolves all [use declarations] and [macro invocations]. The second stage, *primary resolution*, resolves all names that have not yet been resolved that do not depend on type information to resolve. The last stage, *type-relative resolution*, resolves the remaining names once type information is available.
+Name resolution is split into three stages throughout the compilation process. The first stage, *expansion-time resolution*, resolves all [`use` declarations] and [macro invocations]. The second stage, *primary resolution*, resolves all names that have not yet been resolved that do not depend on type information to resolve. The last stage, *type-relative resolution*, resolves the remaining names once type information is available.
 
 > [!NOTE]
 >
@@ -15,7 +15,7 @@ r[names.resolution.expansion]
 ## Expansion-time name resolution
 
 r[names.resolution.expansion.intro]
-Expansion-time name resolution is the stage of name resolution necessary to complete macro expansion and fully generate a crate's AST. This stage requires the resolution of macro invocations and use declarations. Resolving use declarations is required to resolve [path-based scope] macro invocations. Resolving macro invocations is required in order to expand them.
+Expansion-time name resolution is the stage of name resolution necessary to complete macro expansion and fully generate a crate's AST. This stage requires the resolution of macro invocations and `use` declarations. Resolving `use` declarations is required to resolve [path-based scope] macro invocations. Resolving macro invocations is required in order to expand them.
 
 r[names.resolution.expansion.unresolved-invocations]
 After expansion-time name resolution, the AST must not contain any unexpanded macro invocations. Every macro invocation resolves to a valid definition that exists in the final AST or an external crate.
@@ -58,7 +58,7 @@ All name resolution candidates selected during macro expansion are considering s
 r[names.resolution.expansion.imports]
 ### Imports
 r[names.resolution.expansion.imports.intro]
-All use declarations are fully resolved during this stage of resolution. Type-relative paths cannot be resolved at this stage of compilation and will produce an error.
+All `use` declarations are fully resolved during this stage of resolution. Type-relative paths cannot be resolved at this stage of compilation and will produce an error.
 
 ```rust,compile_fail,E0432
 mod my_mod {
@@ -91,7 +91,7 @@ fn foo() {
 ```
 
 r[names.resolution.expansion.imports.shadowing]
-The following is a list of situations where shadowing of use declarations is permitted:
+The following is a list of situations where shadowing of `use` declarations is permitted:
 
 * [`use` glob shadowing]
 * [Macro textual scope shadowing]
@@ -100,7 +100,7 @@ r[names.resolution.expansion.imports.ambiguity]
 #### Ambiguities
 
 r[names.resolution.expansion.imports.ambiguity.intro]
-Some situations are an error when there is an ambiguity as to which macro definition, use declaration, or module an import or macro invocation's name refers to. This happens when there are two name candidates that do not resolve to the same entity where neither candidate is [permitted] to shadow the other.
+Some situations are an error when there is an ambiguity as to which macro definition, `use` declaration, or module an import or macro invocation's name refers to. This happens when there are two name candidates that do not resolve to the same entity where neither candidate is [permitted] to shadow the other.
 
 r[names.resolution.expansion.imports.ambiguity.globvsglob]
 Names may not be resolved through ambiguous glob imports. Glob imports are allowed to import conflicting names in the same namespace as long as the name is not used. Names with conflicting candidates from ambiguous glob imports may still be shadowed by non glob imports and used without producing an error. The errors occur at time of use, not time of import.
@@ -237,7 +237,7 @@ fn foo() {
 ```
 
 r[names.resolution.expansion.imports.ambiguity.pathvstextualmacro]
-Path-based scope bindings for macros may not shadow textual scope bindings to macros. For bindings from [use declarations], this applies regardless of their [sub-namespace].
+Path-based scope bindings for macros may not shadow textual scope bindings to macros. For bindings from [`use` declarations], this applies regardless of their [sub-namespace].
 
 ```rust,compile_fail,E0659
 #[macro_export]
@@ -351,5 +351,5 @@ r[names.resolution.type-dependent]
 [permitted]: name-resolution.md#r-names.resolution.expansion.imports.shadowing
 [scope]: ../names/scopes.md
 [sub-namespace]: ../names/namespaces.md#r-names.namespaces.sub-namespaces
-[use declarations]: ../items/use-declarations.md
+[`use` declarations]: ../items/use-declarations.md
 [visibility]: ../visibility-and-privacy.md