From 5f58da1ced1030f1d7bc9d3e427e3a1abb65481d Mon Sep 17 00:00:00 2001 From: Daniel Nephin Date: Tue, 8 Dec 2020 12:12:15 -0500 Subject: [PATCH] Fix typos in streaming docs Co-authored-by: Paul Banks Co-authored-by: John Cowen --- docs/streaming/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/streaming/README.md b/docs/streaming/README.md index 5a4796c1a8..400b0b680b 100644 --- a/docs/streaming/README.md +++ b/docs/streaming/README.md @@ -39,7 +39,7 @@ and sent to any active subscriptions. ## Event Publisher -The [EventPublisher] in at the core of streaming. It receives published events, and +The [EventPublisher] is at the core of streaming. It receives published events, and subscription requests, and forwards events to the appropriate subscriptions. The diagram below illustrates how events are stored by the [EventPublisher]. @@ -67,7 +67,7 @@ period of time, without any hard coded limit on the number of events to cache. A subscription provides a stream of events on a single topic. Most of the events contain data for a change in state, but there are a few special "framing" events that are used to communicate something to the client. The diagram below helps illustrate the logic in -`EventPublusher.Subscribe` and the [materialized view]. +`EventPublisher.Subscribe` and the [materialized view]. ![Framing events](./framing-events.svg) @@ -97,4 +97,3 @@ and filtering happens. [source](./event-filtering.mmd) -