Fix typos in streaming docs

Co-authored-by: Paul Banks <banks@banksco.de>
Co-authored-by: John Cowen <johncowen@users.noreply.github.com>
This commit is contained in:
Daniel Nephin 2020-12-08 12:12:15 -05:00 committed by GitHub
parent 53adead4e4
commit dd06040248
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions

View File

@ -39,7 +39,7 @@ and sent to any active subscriptions.
## Event Publisher ## 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 subscription requests, and forwards events to the appropriate subscriptions. The diagram
below illustrates how events are stored by the [EventPublisher]. 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 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 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 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) ![Framing events](./framing-events.svg)
@ -97,4 +97,3 @@ and filtering happens.
<sup>[source](./event-filtering.mmd)</sup> <sup>[source](./event-filtering.mmd)</sup>