From 8e666f47e0da4a6d64e280a45771105e4a7919f0 Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Mon, 18 Oct 2021 17:49:45 +0000 Subject: [PATCH] optimistic-confirmation-and-slashing - fix typos (#20741) (#20765) (cherry picked from commit 84660bbf3d4a9b51a2fa9464fc492954eb55ed2d) Co-authored-by: Elliot Lee --- docs/src/proposals/optimistic-confirmation-and-slashing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/src/proposals/optimistic-confirmation-and-slashing.md b/docs/src/proposals/optimistic-confirmation-and-slashing.md index 13442d137d..0c6de6eb57 100644 --- a/docs/src/proposals/optimistic-confirmation-and-slashing.md +++ b/docs/src/proposals/optimistic-confirmation-and-slashing.md @@ -39,9 +39,9 @@ on our mainnet, cosmos, or tezos. For our network, which is primarily composed of high availability systems, this seems unlikely. Currently, we have set the threshold percentage to 4.66%, which means that if 23.68% have failed the network may stop finalizing blocks. For our network, -which is primarily composed of high availability systems a 23.68% drop -in availabilty seems unlinkely. 1:10^12 odds assuming five 4.7% staked -nodes with 0.995 of uptime. +which is primarily composed of high availability systems, a 23.68% drop +in availability seems unlikely. 1:10^12 odds, assuming five 4.7% staked +nodes with 0.995 uptime. ## Security