[mesos] branch master updated: Fixed some spelling in the libprocess documentation.

[jp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jpeach pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git


The following commit(s) were added to refs/heads/master by this push:
     new 686d7b7  Fixed some spelling in the libprocess documentation.
686d7b7 is described below

commit 686d7b704132b0113ba4320d246a7e743cd0347f
Author: Tad Guo <wa...@users.noreply.github.com>
AuthorDate: Thu Oct 25 08:58:04 2018 -0700

    Fixed some spelling in the libprocess documentation.
    
    Fix "Disarding a Future" -> "Discarding a Future".
    
    This closes #315.
---
 3rdparty/libprocess/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/3rdparty/libprocess/README.md b/3rdparty/libprocess/README.md
index 3637044..3e3d5e7 100644
--- a/3rdparty/libprocess/README.md
+++ b/3rdparty/libprocess/README.md
@@ -103,7 +103,7 @@ The following table is meant to capture these transitions:
 
 We use the macros `CHECK_PENDING()`, `CHECK_READY()`, `CHECK_FAILED()`, `CHECK_DISCARDED()` throughout our examples. See [`CHECK()` Overloads](#futures-and-promises-check-overloads) for more details about these macros.
 
-### <a name="futures-and-promises-discarding-a-future"></a> Disarding a Future (aka Cancellation)
+### <a name="futures-and-promises-discarding-a-future"></a> Discarding a Future (aka Cancellation)
 
 You can "cancel" the result of some asynchronous operation by discarding a future. Unlike doing a discard on a promise, _discarding a future is a request that may or may not be be satisfiable_. You discard a future using `Future::discard()`. You can determine if a future has a discard request by using `Future::hasDiscard()` or set up a callback using `Future::onDiscard()`. Here's an example: