From 71f752bbc4eb2a280cd6f6611ba46075a7fdffd1 Mon Sep 17 00:00:00 2001
From: Steve Klabnik <steve@steveklabnik.com>
Date: Fri, 3 Oct 2014 11:58:52 -0400
Subject: [PATCH] Update signature of try_recv()

---
 src/doc/guide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/doc/guide.md b/src/doc/guide.md
index 7805b3d5681..0dc8859c328 100644
--- a/src/doc/guide.md
+++ b/src/doc/guide.md
@@ -5074,7 +5074,7 @@ The `channel()` function returns two endpoints: a `Receiver<T>` and a
 `Sender<T>`. You can use the `.send()` method on the `Sender<T>` end, and
 receive the message on the `Receiver<T>` side with the `recv()` method.  This
 method blocks until it gets a message. There's a similar method, `.try_recv()`,
-which returns an `Option<T>` and does not block.
+which returns an `Result<T, TryRecvError>` and does not block.
 
 If you want to send messages to the task as well, create two channels!