From fd205b847033c6d80c1201274944ec69c2943ba4 Mon Sep 17 00:00:00 2001 From: Eli Barzilay Date: Sat, 2 Aug 2008 19:42:26 +0000 Subject: [PATCH] typos from Grant (PR9652) svn: r11036 --- collects/scribblings/guide/cond.scrbl | 4 ++-- collects/scribblings/guide/control.scrbl | 2 +- collects/scribblings/guide/lambda.scrbl | 5 ++++- collects/scribblings/guide/namespaces.scrbl | 2 +- collects/scribblings/guide/pattern-macros.scrbl | 2 +- collects/scribblings/guide/quote.scrbl | 2 +- collects/scribblings/guide/unit.scrbl | 2 +- collects/scribblings/guide/vectors.scrbl | 2 +- 8 files changed, 12 insertions(+), 9 deletions(-) diff --git a/collects/scribblings/guide/cond.scrbl b/collects/scribblings/guide/cond.scrbl index 35edb479cd..7e74d6e719 100644 --- a/collects/scribblings/guide/cond.scrbl +++ b/collects/scribblings/guide/cond.scrbl @@ -8,7 +8,7 @@ Most functions used for branching, such as @scheme[<] and @scheme[string?], produce either @scheme[#t] or @scheme[#f]. Scheme's branching forms, however, treat any value other than @scheme[#f] as -true. We we say a @defterm{true value} to mean any value other than +true. We say a @defterm{true value} to mean any value other than @scheme[#f]. This convention for ``true value'' meshes well with protocols where @@ -45,7 +45,7 @@ the @scheme[_test-expr] is always evaluated. If it produces any value other than @scheme[#f], then @scheme[_then-expr] is evaluated. Otherwise, @scheme[_else-expr] is evaluated. -An @scheme[if] form must have both an @scheme[_then-expr] and an +An @scheme[if] form must have both a @scheme[_then-expr] and an @scheme[_else-expr]; the latter is not optional. To perform (or skip) side-effects based on a @scheme[_test-expr], use @scheme[when] or @scheme[unless], which we describe later in @secref["begin"]. diff --git a/collects/scribblings/guide/control.scrbl b/collects/scribblings/guide/control.scrbl index de627779bb..e224e154f2 100644 --- a/collects/scribblings/guide/control.scrbl +++ b/collects/scribblings/guide/control.scrbl @@ -123,7 +123,7 @@ predicate: @section[#:tag "prompt"]{Prompts and Aborts} -When an exception is raised control, escapes out of an arbitrary deep +When an exception is raised, control escapes out of an arbitrary deep evaluation context to the point where the exception is caught---or all the way out if the expression is never caught: diff --git a/collects/scribblings/guide/lambda.scrbl b/collects/scribblings/guide/lambda.scrbl index dc30c7b4a9..1431cb32a5 100644 --- a/collects/scribblings/guide/lambda.scrbl +++ b/collects/scribblings/guide/lambda.scrbl @@ -144,7 +144,10 @@ calls with keywords.} @specform/subs[ (lambda gen-formals body ...+) -([arg arg-id +([gen-formals (arg ...) + rest-id + (arg ...+ . rest-id)] + [arg arg-id [arg-id default-expr] (code:line arg-keyword arg-id) (code:line arg-keyword [arg-id default-expr])]) diff --git a/collects/scribblings/guide/namespaces.scrbl b/collects/scribblings/guide/namespaces.scrbl index 614bb99fa5..a391966ecf 100644 --- a/collects/scribblings/guide/namespaces.scrbl +++ b/collects/scribblings/guide/namespaces.scrbl @@ -267,7 +267,7 @@ fails, because the namespace does not include the primitive modules on which @scheme[scheme] is built. To make a namespace useful, some modules much be @deftech{attached} -from an existing namespace. Attaching a module adjust the mapping of +from an existing namespace. Attaching a module adjusts the mapping of module names to instances by transitively copying entries (the module and all its imports) from an existing namespace's mapping. Normally, instead of just attaching the primitive modules---whose names and diff --git a/collects/scribblings/guide/pattern-macros.scrbl b/collects/scribblings/guide/pattern-macros.scrbl index 8b57a52df9..3b41fe35b7 100644 --- a/collects/scribblings/guide/pattern-macros.scrbl +++ b/collects/scribblings/guide/pattern-macros.scrbl @@ -318,7 +318,7 @@ usual role in the generated macro, instead of the generating macro. @section[#:tag "pattern-macro-example"]{Extended Example: Call-by-Reference Functions} -We can use pattern-matching macros to implement add a form to Scheme +We can use pattern-matching macros to add a form to Scheme for defining first-order @deftech{call-by-reference} functions. When a call-by-reference function body mutates its formal argument, the mutation applies to variables that are supplied as actual arguments in diff --git a/collects/scribblings/guide/quote.scrbl b/collects/scribblings/guide/quote.scrbl index 2de41a8c5f..183fdc8755 100644 --- a/collects/scribblings/guide/quote.scrbl +++ b/collects/scribblings/guide/quote.scrbl @@ -47,7 +47,7 @@ more typically used for symbols and lists, which have other meanings An expression -@specform[(quote #,(scheme _datum))] +@specform[(quote #, @schemevarfont{datum})] is a shorthand for diff --git a/collects/scribblings/guide/unit.scrbl b/collects/scribblings/guide/unit.scrbl index b00a1896b5..517b8a48fa 100644 --- a/collects/scribblings/guide/unit.scrbl +++ b/collects/scribblings/guide/unit.scrbl @@ -491,7 +491,7 @@ conveniences---such as allowing overriding of methods or especially simple application to values---that make them suitable for different purposes. -The @scheme[module] form is more fundamental that the others, in a +The @scheme[module] form is more fundamental than the others, in a sense. After all, a program fragment cannot reliably refer to @scheme[lambda], @scheme[class], or @scheme[unit] form without the namespace management provided by @scheme[module]. At the same time, diff --git a/collects/scribblings/guide/vectors.scrbl b/collects/scribblings/guide/vectors.scrbl index 4bf0391060..b7aa1cfc12 100644 --- a/collects/scribblings/guide/vectors.scrbl +++ b/collects/scribblings/guide/vectors.scrbl @@ -31,7 +31,7 @@ written directly as expressions are immutable. Vector can be converted to lists and vice-versa via @scheme[list->vector] and @scheme[vector->list]; such conversions are particularly useful in combination with predefined procedures on -lists. When allocating extra lists seems too expensive, use consider +lists. When allocating extra lists seems too expensive, consider using looping forms like @scheme[fold-for], which recognize vectors as well as lists.