bkyk8rc3zvpnsf5inmcqq4n3k98cv6hj-my-site-hyper-literate-git.test.suzanne.soy-0.0.1

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit 28f34349dd3538a10c1993a1accc4a00717bd66a
parent d1a3a0a6c21fcbfe993026933b1f580bbbc7c9c2
Author: Eli Barzilay <eli@racket-lang.org>
Date:   Sun, 13 Jul 2008 17:13:20 +0000

scribble fixes -- nested @scheme and a few other similar problems

svn: r10744

original commit: 4cd2614c2122dd13e75d2dccc60e11109e26e152

Diffstat:
Mcollects/scribblings/scribble/style.scrbl | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/collects/scribblings/scribble/style.scrbl b/collects/scribblings/scribble/style.scrbl @@ -27,7 +27,7 @@ Prefer ``function'' to ``procedure.'' Avoid cut-and-paste for descriptive text. If two functions are similar, consider documenting them together with @scheme[deftogether]. To abstract a description, consider using -explicit prose abstraction, such as ``@scheme[x] is like @scheme[@y], +explicit prose abstraction, such as ``@scheme[x] is like @scheme[y], except that ...,'' instead of abstracting the source and instantiating it multiple times; often, a prose abstraction is clearer to the reader than a hidden abstraction in the document implementation.