From 6e5434acba1e4ca38b33c31ccdad0924052ec17c Mon Sep 17 00:00:00 2001 From: Suraj Gharat Date: Wed, 3 Jul 2019 15:00:49 +0530 Subject: [PATCH] Update futures.md Correcting a statement that incorrectly refers future instead of promise. --- _overviews/core/futures.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_overviews/core/futures.md b/_overviews/core/futures.md index a0eea92daf..9546e86c33 100644 --- a/_overviews/core/futures.md +++ b/_overviews/core/futures.md @@ -841,7 +841,7 @@ for a more precise description of the semantics. ## Promises So far we have only considered `Future` objects created by -asynchronous computations started using the `future` method. +asynchronous computations started using the `Future` method. However, futures can also be created using *promises*. While futures are defined as a type of read-only placeholder object @@ -935,7 +935,7 @@ has not been completed yet (e.g., there are several HTTP requests being executed from several different futures and the client is interested only in the first HTTP response - corresponding to the first future to complete the promise). For these reasons methods `tryComplete`, -`trySuccess` and `tryFailure` exist on future. The client should be +`trySuccess` and `tryFailure` exist on promise. The client should be aware that using these methods results in programs which are not deterministic, but depend on the execution schedule.