From 8a2b06574aab93e9694aae62de20d4d194d8bd56 Mon Sep 17 00:00:00 2001 From: Jordan Schatz Date: Fri, 3 Feb 2012 10:34:09 -0700 Subject: [PATCH] Two typos in the rackunit docs --- collects/rackunit/scribblings/check.scrbl | 2 +- collects/rackunit/scribblings/quick-start.scrbl | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/collects/rackunit/scribblings/check.scrbl b/collects/rackunit/scribblings/check.scrbl index 50733fe091..cc9c912a56 100644 --- a/collects/rackunit/scribblings/check.scrbl +++ b/collects/rackunit/scribblings/check.scrbl @@ -15,7 +15,7 @@ information detailing the failure. Although checks are implemented as macros, which is necessary to grab source location, they are conceptually functions. This means, for instance, checks always evaluate -their arguments. You can use check as first class +their arguments. You can use checks as first class functions, though you will lose precision in the reported source locations if you do so. diff --git a/collects/rackunit/scribblings/quick-start.scrbl b/collects/rackunit/scribblings/quick-start.scrbl index bb79433bc8..fefa721068 100644 --- a/collects/rackunit/scribblings/quick-start.scrbl +++ b/collects/rackunit/scribblings/quick-start.scrbl @@ -104,7 +104,7 @@ check failed. A test case fails as soon as any check within it fails, and no further checks are evaluated once this takes place. -Naming our test cases if useful as it helps remind us what +Naming our test cases is useful as it helps remind us what we're testing. We can give a test case a name with the @racket[test-case] form: