From 7f9dae9e5f18fd2d5e9625b7acb5acd983e59943 Mon Sep 17 00:00:00 2001
From: Brad Gibson <b2b@humanenginuity.com>
Date: Sat, 17 Aug 2019 19:53:12 -0700
Subject: [PATCH] Clarify async fn return type

---
 docs/src/concepts/futures.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/concepts/futures.md b/docs/src/concepts/futures.md
index 31069ca..cee7ac2 100644
--- a/docs/src/concepts/futures.md
+++ b/docs/src/concepts/futures.md
@@ -102,7 +102,7 @@ While the `Future` trait has existed in Rust for a while, it was inconvenient to
 
 Amazingly little difference, right? All we did is label the function `async` and insert 2 special commands: `.await`.
 
-This function sets up a deferred computation. When this function is called, it will produce a `Future<Output=String>` instead of immediately returning a String. (Or, more precisely, generate a type for you that implements `Future<Output=String>`.)
+This function sets up a deferred computation. When this function is called, it will produce a `Future<Output=Result<String, io::Error>>` instead of immediately returning a `Result<String, io::Error>`. (Or, more precisely, generate a type for you that implements `Future<Output=Result<String, io::Error>>`.)
 
 ## What does `.await` do?