Browse Source

docs: fix some typos in ADR 075. (#7726)

* docs: fix some typos in ADR 075.

* fix typo typo
pull/7733/head
M. J. Fromberger 3 years ago
committed by GitHub
parent
commit
b3c85b795a
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 5 deletions
  1. +3
    -5
      docs/architecture/adr-075-rpc-subscription.md

+ 3
- 5
docs/architecture/adr-075-rpc-subscription.md View File

@ -181,8 +181,6 @@ well as the server. These include:
--- ---
## Decision ## Decision
(pending)
To address the described problems, we will: To address the described problems, we will:
1. Introduce a new API for event subscription to the Tendermint RPC service. 1. Introduce a new API for event subscription to the Tendermint RPC service.
@ -398,8 +396,8 @@ The `oldest_item` and `newest_item` fields of the reply report the cursors of
the oldest and newest items (of any kind) recorded in the event log at the time the oldest and newest items (of any kind) recorded in the event log at the time
of the reply, or are `""` if the log is empty. of the reply, or are `""` if the log is empty.
The `data` field contains the type-specific event datum, and `events` contain
the ABCI events, if any were defined.
The `data` field contains the type-specific event datum. The datum carries any
ABCI events that may have been defined.
> **Discussion point**: Based on [issue #7273][i7273], I did not include a > **Discussion point**: Based on [issue #7273][i7273], I did not include a
> separate field in the response for the ABCI events, since it duplicates data > separate field in the response for the ABCI events, since it duplicates data
@ -458,7 +456,7 @@ crashes and connectivity issues:
no `before_item`). no `before_item`).
2. If there are more events than the client requested, or if the client needs 2. If there are more events than the client requested, or if the client needs
to to read older events to recover from a stall or crash , clients will
to to read older events to recover from a stall or crash, clients will
**page** backward through the event log (by setting `before_item` and **page** backward through the event log (by setting `before_item` and
possibly `after_item`). possibly `after_item`).


Loading…
Cancel
Save