summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorStanislav Chlebec <stanislav.chlebec@pantheon.tech>2018-11-08 12:37:33 +0100
committerStanislav Chlebec <stanislav.chlebec@pantheon.tech>2018-11-08 12:37:34 +0100
commit93dc63d736bea9a11c870879cbd94e5958e48b6d (patch)
tree454a3c8af9e5847257a1ae2bb2f8e766553ee682
parentdee6c34b3e5d3b40bc74fc73fafc1d116126c7fc (diff)
fix typos
Change-Id: I340e8ace6c443667e5e0f1f23ac49f8bf790e781 Signed-off-by: Stanislav Chlebec <stanislav.chlebec@pantheon.tech> Issue-ID: AAF-582
-rw-r--r--ASYNC.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/ASYNC.md b/ASYNC.md
index 97167f3..0a522ad 100644
--- a/ASYNC.md
+++ b/ASYNC.md
@@ -1,11 +1,11 @@
# ASYNCHRONOUS MODE
-Gizmo has two modes, a Synchoronous (sync) mode and an Asynchronous (async) mode.
+Gizmo has two modes, a Synchronous (sync) mode and an Asynchronous (async) mode.
In the Async mode, Gizmo uses the consumer/producer model where when a
client makes a request, Gizmo will generate an event payload and
publish it on the async event stream. It will then wait for a
-response for that particular event on a different event stream. Once it recieves a
+response for that particular event on a different event stream. Once it receives a
response, gizmo will send a response back to the client which made the
original request.