[plt-dev] [PATCH] Fixes for trivial typos in Reference sec. 1.2.

From: Jose Antonio Ortega Ruiz (jao at gnu.org)
Date: Mon May 24 22:09:02 EDT 2010

Signed-off-by: Jose Antonio Ortega Ruiz <jao at gnu.org>
 collects/scribblings/reference/syntax-model.scrbl |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/collects/scribblings/reference/syntax-model.scrbl b/collects/scribblings/reference/syntax-model.scrbl
index 2fd384d..ef2decb 100644
--- a/collects/scribblings/reference/syntax-model.scrbl
+++ b/collects/scribblings/reference/syntax-model.scrbl
@@ -37,7 +37,7 @@ new binding information.
-An @deftech{identifier} is source-program entity. Parsing (i.e.,
+An @deftech{identifier} is a source-program entity. Parsing (i.e.,
 expanding) a Racket program reveals that some @tech{identifiers}
 correspond to @tech{variables}, some refer to syntactic forms, and
 some are quoted to produce a symbol or a syntax object.
@@ -73,7 +73,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
- at tech{identifier} like @racket[lambda] indicates as a reference to a
+ at 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
@@ -125,14 +125,14 @@ indicate that it references a @tech{top-level variable}.
 When a @tech{syntax object} represents a more complex expression than
 an @tech{identifier} or simple constant, its internal components can
-be extracted. Even for extracted identifier, detailed information
+be extracted. Even for extracted identifiers, detailed information
 about binding is available mostly indirectly; two identifiers can be
 compared to see if they refer to the same binding (i.e.,
 @racket[free-identifier=?]), or whether each identifier would bind the
 other if one was in a binding position and the other in an expression
 position (i.e., @racket[bound-identifier=?]).
-For example, the when the program written as
+For example, when the program written as
 @racketblock[(let ([x 5]) (+ x 6))]
@@ -467,7 +467,7 @@ For example, in
 the binding introduced for @racket[x] applies to the @racket[x] in the
-body, but not the @racket[y] n the body, because (at the point in
+body, but not the @racket[y] in the body, because (at the point in
 expansion where the @racket[let-values] form is encountered) the
 binding @racket[x] and the body @racket[y] are not
@@ -575,7 +575,7 @@ certificates}.
 The expander's handling of @racket[letrec-values+syntaxes] is similar
 to its handling of @racket[define-syntaxes]. A
- at racket[letrec-values+syntaxes] mist be expanded in an arbitrary phase
+ at racket[letrec-values+syntaxes] must be expanded in an arbitrary phase
 level @math{n} (not just 0), in which case the expression for the
 @tech{transformer binding} is expanded at @tech{phase level} @math{n+1}.
@@ -849,7 +849,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).

Posted on the dev mailing list.