From 5de19e593b563f32e1d18f175b93f9481cad5704 Mon Sep 17 00:00:00 2001 From: Stephen Chang Date: Thu, 19 Apr 2018 13:33:25 -0400 Subject: [PATCH] guide: a few more typos in instantiations and visits sec --- pkgs/racket-doc/scribblings/guide/macro-module.scrbl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pkgs/racket-doc/scribblings/guide/macro-module.scrbl b/pkgs/racket-doc/scribblings/guide/macro-module.scrbl index f2c4855ab6..6bcb6613a6 100644 --- a/pkgs/racket-doc/scribblings/guide/macro-module.scrbl +++ b/pkgs/racket-doc/scribblings/guide/macro-module.scrbl @@ -325,7 +325,7 @@ not yet specified what happens with @racket[for-meta 2] for when If you think of the top-level as a kind of module that is continuously expanded, the above rules imply that @racket[require] of another module at the top level both instantiates and visits the other module -(it it is not already instantiated and visited). That's roughly true, +(if it is not already instantiated and visited). That's roughly true, but the visit is made lazy in a way that is also explained in the next section, @secref["stx-available-module"]. @@ -343,14 +343,14 @@ A top-level @racket[require] of a module does not actually @deftech{available}. An @tech{available} module will be @tech{visit}ed when a future expression needs to be expanded in the same context. The next expression may or may not involve some imported macro that needs -it's compile-time helpers evaluated by @tech{visit}ing, but the module +its compile-time helpers evaluated by @tech{visit}ing, but the module system proactively @tech{visit}s the module, just in case. In the following example, a random number is picked as a result of visiting a module's own body while that module is being expanded. A @racket[require] of the module instantiates it, printing ``running'', and also makes the module @tech{available}. Evaluating any other -expression implies expanding the expression, and that expansions +expression implies expanding the expression, and that expansion triggers a @tech{visit} of the @tech{available} module---which picks another random number: