Update macros.md

PR feedback

Author: blast-hardcheese

docs/docs/reference/metaprogramming/macros.md

@@ -197,11 +197,14 @@ def to[T, R](f: Expr[T] => Expr[R])(using t: Type[T])(using Type[R], Quotes): Ex
 ```
 
 In this version of `to`, the type of `x` is now the result of
-splicing the `Type` value `t`. This operation _is_ splice correct -- there
-is one quote and one splice between the use of `t` and its definition.
+inserting the type `Type[T]` and selecting its `Underlying `.
+
+To avoid clutter, the compiler converts any type reference to
+a type `T` in subsequent phases to `summon[Type[T]].Underlying`.
+
+And to avoid duplication it does it once per type, and creates
+an alias for that type at the start of the quote.
 
-To avoid clutter, the Scala implementation tries to convert any type
-reference to a type `T` in subsequent phases to a type-splice, by rewriting `T` to `summon[Type[T]].Underlying`.
 For instance, the user-level definition of `to`:
 
 ```scala
@@ -213,7 +216,10 @@ would be rewritten to
 
 ```scala
 def to[T, R](f: Expr[T] => Expr[R])(using t: Type[T], r: Type[R])(using Quotes): Expr[T => R] =
-   '{ (x: t.Underlying) => ${ f('x) } }
+   '{ 
+      type T = t.Underlying
+      (x: T) => ${ f('x) } 
+   }
 ```
 
 The `summon` query succeeds because there is a given instance of