doc

Project: http://git-wip-us.apache.org/repos/asf/curator/repo
Commit: http://git-wip-us.apache.org/repos/asf/curator/commit/88fee0ea
Tree: http://git-wip-us.apache.org/repos/asf/curator/tree/88fee0ea
Diff: http://git-wip-us.apache.org/repos/asf/curator/diff/88fee0ea

Branch: refs/heads/CURATOR-3.0
Commit: 88fee0eac4a48e9391edf8997a5a20e14c1c18a7
Parents: 908b5c6
Author: randgalt <randg...@apache.org>
Authored: Sat Jan 7 11:33:28 2017 -0500
Committer: randgalt <randg...@apache.org>
Committed: Sat Jan 7 11:33:28 2017 -0500

----------------------------------------------------------------------
 curator-x-async/src/site/confluence/index.confluence | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/curator/blob/88fee0ea/curator-x-async/src/site/confluence/index.confluence
----------------------------------------------------------------------
diff --git a/curator-x-async/src/site/confluence/index.confluence 
b/curator-x-async/src/site/confluence/index.confluence
index 7e1449b..88f649e 100644
--- a/curator-x-async/src/site/confluence/index.confluence
+++ b/curator-x-async/src/site/confluence/index.confluence
@@ -47,7 +47,7 @@ h4. AsyncStage
 AsyncStage instances extend Java 8's CompletionStage. CompletionStage objects 
can be "completed" with a success
 value or an exception. The parameterized type of the AsyncStage will
 be whatever the builder used would naturally return as a success value. E.g. 
the async getData() builder's AsyncStage is
-parameterized with {{byte[]}}. For the exception, Curator Async always uses 
AsyncEventException (see below).
+parameterized with "byte\[\]".
 
 h4. Watchers
 
@@ -80,7 +80,7 @@ h4. AsyncEventException
 When an async watcher fails the exception set in the CompletionStage will be 
of type {{AsyncEventException}}.
 This exception allows you to see the KeeperState that caused the trigger and 
allows you to reset the
 completion stage. Reset is needed because ZooKeeper temporarily triggers 
watchers when there is a connection
-event. However, the watcher stays set for the original operation. Use 
{{AsyncEventException#reset()}}
+event. However, the watcher stays set for the original operation. Use 
{{AsyncEventException#reset}}
 to start a new completion stage that will wait on the next trigger of the 
watcher.
 
 E.g.
@@ -90,7 +90,7 @@ AsyncStage stage = ...
 stage.event().exceptionally(e -> {
     AsyncEventException asyncEx = (AsyncEventException)e;
 
-    ... noteAConnectionProblem ...
+    ... note a connection problem ...
 
     asyncEx.reset().thenRun(() -> successMethod());
 });

Reply via email to