X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=System%2FTimeout.hs;fp=System%2FTimeout.hs;h=dbf92099c27db28fcba6ee5f047243cf5257425b;hb=9998ccb135e022aee442d32bf1f9e723a2256887;hp=c7e4ee21930158114ac58f1dfc801376471b8902;hpb=dae853e21f2a1ac47cee4b63b6cc305129320edb;p=ghc-base.git

diff --git a/System/Timeout.hs b/System/Timeout.hs
index c7e4ee2..dbf9209 100644
--- a/System/Timeout.hs
+++ b/System/Timeout.hs
@@ -57,7 +57,7 @@ data Timeout = Timeout Unique deriving (Eq, Typeable)
 -- blocks, no timeout event can be delivered until the FFI call returns, which
 -- pretty much negates the purpose of the combinator. In practice, however,
 -- this limitation is less severe than it may sound. Standard I\/O functions
--- like 'System.IO.hGetBuf', 'System.IO.hPutBuf', 'Network.Socket.accept', or
+-- like 'System.IO.hGetBuf', 'System.IO.hPutBuf', Network.Socket.accept, or
 -- 'System.IO.hWaitForInput' appear to be blocking, but they really don't
 -- because the runtime system uses scheduling mechanisms like @select(2)@ to
 -- perform asynchronous I\/O, so it is possible to interrupt standard socket