split expansion intro into multiple sections

Author: yaahc

src/names/name-resolution.md

@@ -17,11 +17,24 @@ r[names.resolution.expansion]
 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.
 
-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. The resolution of imports must be *stable*. After expansion, imports in the fully expanded AST must resolve to the same definition, regardless of the order in which macros are expanded. Once the crate has been fully expanded all speculative import resolutions are validated to ensure that no new ambiguities were introduced by macro expansion.
+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.
+
+```rust,compile_fail
+fn main() {
+    foo!(); // ERROR: cannot find macro `foo` in this scope
+}
+```
+
+r[names.resolution.expansion.expansion-order-stability]
+The resolution of names must be *stable*. After expansion, names in the fully expanded AST must resolve to the same definition, regardless of the order in which macros are expanded.
+
+r[names.resolution.expansion.speculation]
+All name resolution candidates selected during macro expansion are considering speculative. Once the crate has been fully expanded all speculative import resolutions are validated to ensure that no new ambiguities were introduced by macro expansion.
 
 > [!NOTE]
 >
-> Due to the iterative nature of macro expansion, this causes so called time traveling ambiguities, such as when a glob import introduces an item that is ambiguous with its own base path.
+> Due to the iterative nature of macro expansion, this causes so called time traveling ambiguities, such as when a macro or glob import introduces an item that is ambiguous with its own base path.
 >
 > ```rust,compile_fail,E0659
 > macro_rules! m {
@@ -329,6 +342,7 @@ r[names.resolution.type-dependent]
 
 [Macros]: ../macros.md
 [`let` bindings]: ../statements.md#let-statements
+[`use` glob shadowing]: ../items/use-declarations.md#r-items.use.glob.shadowing
 [item definitions]: ../items.md
 [macro invocations]: ../macros.md#macro-invocation
 [macro textual scope shadowing]: ../macros-by-example.md#r-macro.decl.scope.textual.shadow
@@ -338,5 +352,4 @@ r[names.resolution.type-dependent]
 [scope]: ../names/scopes.md
 [sub-namespace]: ../names/namespaces.md#r-names.namespaces.sub-namespaces
 [use declarations]: ../items/use-declarations.md
-[use glob shadowing]: ../items/use-declarations.md#r-items.use.glob.shadowing
 [visibility]: ../visibility-and-privacy.md