From 5a9ff6a044c0611ec1b144db6e4bc9d48538b2df Mon Sep 17 00:00:00 2001 From: Eli Barzilay Date: Sun, 13 Jul 2008 17:13:20 +0000 Subject: [PATCH] scribble fixes -- nested @scheme and a few other similar problems svn: r10744 original commit: 4cd2614c2122dd13e75d2dccc60e11109e26e152 --- pkgs/racket-doc/scribblings/style/scribble.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkgs/racket-doc/scribblings/style/scribble.scrbl b/pkgs/racket-doc/scribblings/style/scribble.scrbl index d4d8d566d2..1590a2c469 100644 --- a/pkgs/racket-doc/scribblings/style/scribble.scrbl +++ b/pkgs/racket-doc/scribblings/style/scribble.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.