From 6f0e79feff9dcb038b7b3e7132d9bba9ae7ec99d Mon Sep 17 00:00:00 2001 From: Jose Antonio Ortega Ruiz Date: Tue, 25 May 2010 04:09:02 +0200 Subject: [PATCH] Fixes for trivial typos in Reference sec. 1.2. (Eli: Ancient commit on the mailing list that wasn't merged... Most things were already fixed.) Signed-off-by: Jose Antonio Ortega Ruiz --- collects/scribblings/reference/syntax-model.scrbl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/collects/scribblings/reference/syntax-model.scrbl b/collects/scribblings/reference/syntax-model.scrbl index 390f594fd0..abafa14d80 100644 --- a/collects/scribblings/reference/syntax-model.scrbl +++ b/collects/scribblings/reference/syntax-model.scrbl @@ -71,7 +71,7 @@ identifiers are called @tech{unbound} in a module context. Throughout the documentation, @tech{identifiers} are typeset to suggest the way that they are parsed. A black, boldface -@tech{identifier} like @racket[lambda] indicates as a reference to a +@tech{identifier} like @racket[lambda] indicates a reference to a syntactic form. A plain blue @tech{identifier} like @racketidfont{x} is a @tech{variable} or a reference to an unspecified @tech{top-level variable}. A hyperlinked @tech{identifier} @racket[cons] is a @@ -855,7 +855,7 @@ For expansion purposes, a namespace maps each symbol in each An ``empty'' namespace maps all symbols to top-level variables. Certain evaluations extend a namespace for future expansions; importing a module into the top-level adjusts the namespace bindings -for all of the imported named, and evaluating a top-level +for all of the imported names, and evaluating a top-level @racket[define] form updates the namespace's mapping to refer to a variable (in addition to installing a value into the variable).