Fix doc typos
This commit is contained in:
parent
414ed2597e
commit
9f83ba1c6f
|
@ -299,7 +299,7 @@ important advantages of the @tech{JIT} compiler. For example, when
|
|||
@racket[+] is applied to two arguments, the generated machine code
|
||||
tests whether the two arguments are fixnums, and if so, it uses the
|
||||
machine's instruction to add the numbers (and check for overflow). If
|
||||
the two numbers are not fixnums, then it checks whether whether
|
||||
the two numbers are not fixnums, then it checks whether
|
||||
both are flonums; in that case, the machine's floating-point
|
||||
operations are used directly. For functions that take any number of
|
||||
arguments, such as @racket[+], inlining works for two or more
|
||||
|
|
|
@ -525,7 +525,7 @@ enclosed subpattern as an entity:
|
|||
|
||||
@interaction[
|
||||
#:eval rx-eval
|
||||
(regexp-match #rx"(poo )*" "poo poo platter")
|
||||
(regexp-match #rx"(pu )*" "pu pu platter")
|
||||
]
|
||||
|
||||
The number of submatches returned is always equal to the number of
|
||||
|
|
|
@ -69,7 +69,7 @@ For Unix/X, the script created by @racket[make-mred-launcher] detects
|
|||
and handles X Windows flags specially when they appear as the initial
|
||||
arguments to the script. Instead of appending these arguments to the
|
||||
end of @racket[args], they are spliced in after any X Windows flags
|
||||
already listed listed in @racket[args]. The remaining arguments (i.e.,
|
||||
already listed in @racket[args]. The remaining arguments (i.e.,
|
||||
all script flags and arguments after the last X Windows flag or
|
||||
argument) are then appended after the spliced @racket[args].}
|
||||
|
||||
|
|
|
@ -291,7 +291,7 @@ Optional @filepath{info.rkt} fields trigger additional actions by
|
|||
]
|
||||
|
||||
is provided for the optional @racket[_aux] argument (for icons,
|
||||
etc.) to @racket[make-racket-launcher], where where
|
||||
etc.) to @racket[make-racket-launcher], where
|
||||
@nonterm{suffixless-file} is @nonterm{file} without its suffix.
|
||||
|
||||
If @racket[racket-launcher-flags] is provided, it is used as a
|
||||
|
@ -539,7 +539,7 @@ form.}
|
|||
|
||||
@defparam[specific-collections colls (listof (listof path-string?))]{
|
||||
A list of collections to set up; the empty list means set-up all
|
||||
collections if the archives list and @racket[specific-planet-dirs] is
|
||||
collections if the archives list and @racket[specific-planet-dirs]
|
||||
is also @racket['()]. @defaults[@racket['()]]}
|
||||
|
||||
@defparam[specific-planet-dirs dir (listof (list/c string?
|
||||
|
|
|
@ -374,6 +374,6 @@ Latex output.
|
|||
When using @racket[local-table-of-contents], it often makes sense to
|
||||
include introductory text before the call of
|
||||
@racket[local-table-of-contents]. When the introductory text is less
|
||||
important and when when local table of contents is short, putting the
|
||||
important and when local table of contents is short, putting the
|
||||
introductory text after the call of @racket[local-table-of-contents]
|
||||
may be appropriate.
|
||||
|
|
|
@ -185,7 +185,7 @@ produces the typeset result
|
|||
([maybe-escape code:blank
|
||||
(code:line #:escape escape-id)])]{
|
||||
|
||||
Typesets the @racket[datum] sequence as a table of Racket code inset
|
||||
Typesets the @racket[datum] sequence as a table of Racket code
|
||||
inset via @racket[nested] with the style @racket['code-inset]. The
|
||||
source locations of the @racket[datum]s determine the generated
|
||||
layout. For example,
|
||||
|
@ -223,7 +223,7 @@ Like other forms defined via @racket[define-code],
|
|||
@tech{element transformers}.
|
||||
|
||||
An @racket[#:escape] clause specifies an identifier to escape back to
|
||||
an expression that produces produces an @racket[element]. But default,
|
||||
an expression that produces an @racket[element]. By default,
|
||||
the escape identifier is @racket[unsyntax]. For example,
|
||||
|
||||
@racketblock[
|
||||
|
@ -435,7 +435,7 @@ linked, even if it is not an identifier.}
|
|||
|
||||
@defproc[(litchar [str string?] ...) element?]{Typesets @racket[str]s as a
|
||||
representation of literal text. Use this when you have to talk about
|
||||
the individual characters in a stream of text, as as when documenting
|
||||
the individual characters in a stream of text, as when documenting
|
||||
a reader extension.}
|
||||
|
||||
@defproc[(racketfont [pre-content pre-content?] ...) element?]{Typesets
|
||||
|
@ -1226,7 +1226,7 @@ Typesets the given combination of a GUI's menu and item name.}
|
|||
|
||||
@defproc[(filepath [pre-content pre-content?] ...) element?]{Typesets the
|
||||
@tech{decode}d @racket[pre-content] as a file name (e.g., in
|
||||
typewriter font and in in quotes).}
|
||||
typewriter font and in quotes).}
|
||||
|
||||
@defproc[(exec [pre-content pre-content?] ...) element?]{Typesets the
|
||||
@tech{decode}d @racket[pre-content] as a command line (e.g., in
|
||||
|
|
|
@ -96,7 +96,7 @@ The normal @racket[require]s of the enclosing library are effectively
|
|||
converted into @racket[for-label] @racket[require]s when generating
|
||||
documentation, so that identifiers in the @racket[contract]s are
|
||||
linked to their corresponding documentation. Similarly, any binding
|
||||
that is available in the run-time phase of of the enclosing library
|
||||
that is available in the run-time phase of the enclosing library
|
||||
can be referenced in documentation prose using the @racket[racket]
|
||||
form.}
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user