github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixes a typo in the event docs, and twiddles the formatting.

Browse Source
pull/1174/head
James Phillips 9 years ago
parent 009f0fb023
commit 88c15e5bbd
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
website/source/docs/commands/event.html.markdown
Unescape View File

@ -19,7 +19,7 @@ or perform any other orchestration action. Events can be handled by
Under the hood, events are propagated using the [gossip protocol](/docs/internals/gossip.html). Under the hood, events are propagated using the [gossip protocol](/docs/internals/gossip.html).
While the details are not important for using events, an understanding of While the details are not important for using events, an understanding of
the semantics is useful. The gossip layer will make a best-effort to deliver the semantics is useful. The gossip layer will make a best-effort to deliver
the event, but there is **no guarantee** delivery. Unlike most Consul data, which is the event, but there is **no guaranteed delivery**. Unlike most Consul data, which is
replicated using [consensus](/docs/internals/consensus.html), event data replicated using [consensus](/docs/internals/consensus.html), event data
is purely peer-to-peer over gossip. This means it is not persisted and does is purely peer-to-peer over gossip. This means it is not persisted and does
not have a total ordering. In practice, this means you cannot rely on the not have a total ordering. In practice, this means you cannot rely on the

Write Preview
Loading…
Cancel
Save