update path-vs-textual ambiguity text

Author: yaahc

src/names/name-resolution.md

@@ -191,9 +191,7 @@ fn ambiguous_shadow() {
 }
 ```
 
-Multiple glob imports are allowed to import the same name, and that name is
-allowed to be used if the imports are of the same item (following re-exports).
-The visibility of the name is the maximum visibility of the imports.
+Multiple glob imports are allowed to import the same name, and that name is allowed to be used if the imports are of the same item (following re-exports). The visibility of the name is the maximum visibility of the imports.
 
 ```rust
 mod m1 {
@@ -281,7 +279,7 @@ const _: () = {
 > ```
 
 r[names.resolution.expansion.imports.ambiguity.path-vs-textual-macro]
-Path-based scope bindings for macros may not shadow textual scope bindings to macros.
+Names may not be resolved through ambiguous macro re-exports. Macro re-exports are ambiguous when they would shadow a textual macro candidate for the same name in an [outer scope].
 
 ```rust,compile_fail,E0659
 macro_rules! ambig {
@@ -300,6 +298,11 @@ pub fn f() {
 }
 ```
 
+// [!NOTE]
+// This restriction is needed due to implementation details in the compiler,
+// specifically the current scope visitation logic and the complexity of supporting
+// this behavior. This ambiguity error may be removed in the future.
+
 r[names.resolution.expansion.macros]
 ### Macros
 
@@ -322,6 +325,12 @@ The available scope kinds are visited in the following order. Each of these scop
 >
 > For more info see [derive helper scope].
 
+> [!NOTE]
+>
+> This visitation order may change in the future, such as interleaving the
+> visitation of textual and path-based scope candidates based on their lexical
+> scopes.
+
 > [!EDITION-2018]
 >
 > Starting in edition 2018 the `#[macro_use]` prelude is not visited when `#[no_implicit_prelude]` is present.