From 856df5e1133854bdba8d1ba1967d2f4c75eeb992 Mon Sep 17 00:00:00 2001 From: Matthew Flatt Date: Fri, 31 Dec 2010 14:41:37 -0700 Subject: [PATCH] doc correction --- collects/scribblings/reference/file-ports.scrbl | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/collects/scribblings/reference/file-ports.scrbl b/collects/scribblings/reference/file-ports.scrbl index a84ccea42a..94a6ec95ad 100644 --- a/collects/scribblings/reference/file-ports.scrbl +++ b/collects/scribblings/reference/file-ports.scrbl @@ -315,10 +315,9 @@ either it is released with @racket[port-file-unlock] or the port is closed Depending on the platform, locks may be merely advisory (i.e., locks affect only the ability of processes to acquire locks) or they may -correspond to mandatory read and write locks, where @racket['shared] -locks correspond to read locks and @racket['exclusive] locks -correspond to write locks. Specifically, locks are mandatory under -Windows and advisory on other platforms. +correspond to mandatory locks that prevent reads and writes to the +locked file. Specifically, locks are mandatory under Windows and +advisory on other platforms. Typically, locking is supported only for file ports, and attempting to acquire a lock with other kinds of file-stream ports raises an