From 5cd910f9f23c7f7b78343e0c57e93dc6a9508824 Mon Sep 17 00:00:00 2001 From: Eric Dobson Date: Tue, 23 Jun 2015 20:57:08 -0700 Subject: [PATCH] Fix docs on channel synchronization --- pkgs/racket-doc/scribblings/reference/channels.scrbl | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/pkgs/racket-doc/scribblings/reference/channels.scrbl b/pkgs/racket-doc/scribblings/reference/channels.scrbl index fbb1b3943d..b462d81089 100644 --- a/pkgs/racket-doc/scribblings/reference/channels.scrbl +++ b/pkgs/racket-doc/scribblings/reference/channels.scrbl @@ -15,10 +15,9 @@ often, then the thread eventually participates in a transaction. In addition to its use with channel-specific procedures, a channel can be used as a @tech{synchronizable event} (see @secref["sync"]). A -channel is @tech{ready for synchronization} when @racket[make-channel] -is ready when @racket[channel-get] would not block; the channel's -@tech{synchronization result} is the same as the @racket[channel-get] -result. +channel is @tech{ready for synchronization} when @racket[channel-get] +would not block; the channel's @tech{synchronization result} is the +same as the @racket[channel-get] result. For buffered asynchronous channels, see @secref["async-channel"].