update example for path vs textual macro ambiguity

Author: yaahc

src/names/name-resolution.md

@@ -283,15 +283,19 @@ r[names.resolution.expansion.imports.ambiguity.path-vs-textual-macro]
 Path-based scope bindings for macros may not shadow textual scope bindings to macros.
 
 ```rust,compile_fail,E0659
-macro_rules! m2 {
+macro_rules! ambig {
+//           ^---- textual macro candidate
     () => {}
 }
-macro_rules! m {
+
+macro_rules! path_based {
+//           ^--- path-based macro candidate
     () => {}
 }
+
 pub fn foo() {
-    m!(); // ERROR: `m` is ambiguous
-    use m2 as m; // In scope for entire function body.
+    ambig!(); // ERROR: `ambig` is ambiguous
+    use path_based as ambig; // In scope for entire function body.
 }
 ```