From e0029e50a83d4c04841875b3f034edafbbd79f0a Mon Sep 17 00:00:00 2001 From: Vincent St-Amour Date: Wed, 2 Feb 2011 14:18:29 -0500 Subject: [PATCH] Fix more doc typoes. Closes PR 11694. Merge to 5.1. (cherry picked from commit 2935170eff16b7d86a2f24234189cc083e9f360f) --- collects/scribblings/guide/contracts-examples.scrbl | 4 ++-- collects/scribblings/guide/contracts-examples/2.rkt | 2 +- collects/scribblings/guide/contracts-examples/5.rkt | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/collects/scribblings/guide/contracts-examples.scrbl b/collects/scribblings/guide/contracts-examples.scrbl index 48a0b51613..c89b9b99e1 100644 --- a/collects/scribblings/guide/contracts-examples.scrbl +++ b/collects/scribblings/guide/contracts-examples.scrbl @@ -16,7 +16,7 @@ Mitchell and McKim's principles for design by contract DbC are derived from the 1970s style algebraic specifications. The overall goal of DbC is to specify the constructors of an algebra in terms of its observers. While we reformulate Mitchell and McKim's terminology and - we use a mostly applicative, we + we use a mostly applicative approach, we retain their terminology of ``classes'' and ``objects'': @itemize[ @@ -28,7 +28,7 @@ Mitchell and McKim's principles for design by contract DbC are derived implementation a command typically returns an new object of the same class.} -@item{@bold{Separate basic queries from derived queries} +@item{@bold{Separate basic queries from derived queries.} A @italic{derived query} returns a result that is computable in terms of basic queries.} diff --git a/collects/scribblings/guide/contracts-examples/2.rkt b/collects/scribblings/guide/contracts-examples/2.rkt index 9a53886be4..022eab13ab 100644 --- a/collects/scribblings/guide/contracts-examples/2.rkt +++ b/collects/scribblings/guide/contracts-examples/2.rkt @@ -50,7 +50,7 @@ [initialize (->d ([p contract?] [s (p p . -> . boolean?)]) () - ;; Mitchel and McKim use (= (count s) 0) here to express + ;; Mitchell and McKim use (= (count s) 0) here to express ;; the post-condition in terms of a primitive query [result (and/c stack? is-empty?)])] diff --git a/collects/scribblings/guide/contracts-examples/5.rkt b/collects/scribblings/guide/contracts-examples/5.rkt index ceeb0f96ec..e9ddf09926 100644 --- a/collects/scribblings/guide/contracts-examples/5.rkt +++ b/collects/scribblings/guide/contracts-examples/5.rkt @@ -1,7 +1,7 @@ #lang racket ;; Note: this queue doesn't implement the capacity restriction -;; of McKim and Mitchell's queue but this is easy to add. +;; of Mitchell and McKim's queue but this is easy to add. ;; a contract utility (define (all-but-last l) (reverse (cdr (reverse l)))) @@ -32,7 +32,7 @@ ;; primitive queries ;; Imagine providing this 'query' for the interface of the module - ;; only. Then in Scheme, there is no reason to have count or is-empty? + ;; only. Then in Racket there is no reason to have count or is-empty? ;; around (other than providing it to clients). After all items is ;; exactly as cheap as count. [items (->d ([q queue?]) () [result (listof (queue-p? q))])]