diff options
| author | Dimitris Apostolou <dimitris.apostolou@icloud.com> | 2018-03-02 23:00:25 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-03-02 23:00:25 +0200 |
| commit | a9761cae1c108c143215491af40a3578966116ad (patch) | |
| tree | 3df6916b4f6e5139b28a9d4a289d1a594a449d51 /doc/zmq.md | |
| parent | 90a0aed51194ad82da8e011b96f9561c685e40b7 (diff) | |
| download | bitcoin-a9761cae1c108c143215491af40a3578966116ad.tar.xz | |
Fix typos and cleanup
[ci-skip]
Diffstat (limited to 'doc/zmq.md')
| -rw-r--r-- | doc/zmq.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/zmq.md b/doc/zmq.md index 38c58fb7fd..5d67df9d22 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -101,6 +101,6 @@ and just the tip will be notified. It is up to the subscriber to retrieve the chain from the last known block to the new tip. There are several possibilities that ZMQ notification can get lost -during transmission depending on the communication type your are +during transmission depending on the communication type you are using. Bitcoind appends an up-counting sequence number to each notification which allows listeners to detect lost notifications. |