fix guide typos

closes PR 10577
This commit is contained in:
Ryan Culpepper 2011-05-12 15:15:35 -06:00
parent 042402b023
commit d22a16a3c7
3 changed files with 6 additions and 6 deletions

View File

@ -217,7 +217,7 @@ so the following are valid instances of the grammar:
(lambda (f) (code:comment @#,elem{one definition})
(define (log-it what)
(printf "~a\n"))
(printf "~a\n" what))
(log-it "running")
(f 0)
(log-it "done"))
@ -228,11 +228,11 @@ so the following are valid instances of the grammar:
(log-it "done")
(begin
(log-it "running")
(f 0)
(f n)
(call (- n 1)))))
(define (log-it what)
(printf "~a\n"))
(call f n))
(printf "~a\n" what))
(call n))
]
Internal definitions in a particular @racket[_body] sequence are

View File

@ -40,7 +40,7 @@ A literal immutable hash table can be written as an expression by using
@litchar{#hasheqv} (for an @scheme[eqv?]-based table), or
@litchar{#hasheq} (for an @scheme[eq?]-based table). A parenthesized
sequence must immediately follow @litchar{#hash}, @litchar{#hasheq},
or @litchar{#hasheqv}, where each element is a sequence is a dotted
or @litchar{#hasheqv}, where each element is a dotted
key--value pair. The @litchar{#hash}, etc. forms implicitly
@scheme[quote] their key and value sub-forms.

View File

@ -286,7 +286,7 @@ It turns out that if you write
(f i)))
]
then the @racket[for/list] form in the function both is expanded to
then the @racket[for/list] form in the function is expanded to
essentially the same code as the @racket[iter] local definition and
use. The difference is merely syntactic convenience.