From 46d3ea2bb8fdee5fe1380d3e3b89273c0021120f Mon Sep 17 00:00:00 2001 From: minor-change Date: Sun, 30 May 2021 10:31:50 +0000 Subject: [PATCH] Fix typos --- pkgs/racket-doc/scribblings/guide/concurrency.scrbl | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pkgs/racket-doc/scribblings/guide/concurrency.scrbl b/pkgs/racket-doc/scribblings/guide/concurrency.scrbl index 01fe4cc1c4..1bfdd52b17 100644 --- a/pkgs/racket-doc/scribblings/guide/concurrency.scrbl +++ b/pkgs/racket-doc/scribblings/guide/concurrency.scrbl @@ -456,11 +456,11 @@ exceptions during its handler's invocation. Events also allow you to encode many different communication patterns between multiple concurrent parts of a program. One common such pattern is producer-consumer. Here is a way to -implement on variation on it using the above ideas. Generally +implement a variation on it using the above ideas. Generally speaking, these communication patterns are implemented via -a server loops that uses @racket[sync] to wait for any of -a number of different possibilities to occur and then -reacts them, updating some local state. +a server loop that uses @racket[sync] to wait for any +number of different possibilities to occur and then +reacts to them, updating some local state. @examples[ #:eval concurrency-eval