From 63a6399f0900aec95d8cb734d5f9f692b3d17556 Mon Sep 17 00:00:00 2001 From: thephez Date: Wed, 1 May 2019 16:57:54 -0400 Subject: [PATCH] Formatting --- _includes/devdoc/guide_dash_features.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/_includes/devdoc/guide_dash_features.md b/_includes/devdoc/guide_dash_features.md index 7d33e14e..b9fd13dc 100644 --- a/_includes/devdoc/guide_dash_features.md +++ b/_includes/devdoc/guide_dash_features.md @@ -733,11 +733,12 @@ network propagation. Beginning ~3 days (1662 blocks) prior to a superblock, Sentinel selects one masternode per block to rank proposals. This ranking is used to determine what a candidate superblock (or "superblock trigger") should contain. Based on -the results, it creates and broadcasts a new superblock trigger if a matching one was not found. +the results, it creates and broadcasts a new superblock trigger if a matching +one was not found. -All masternodes vote for existing superblock triggers. -Each masternode casts only 1 superblock trigger "Yes" vote per superblock cycle. -It will vote "No" for any other triggers it receives. +All masternodes vote for existing superblock triggers. Each masternode casts +only 1 superblock trigger "Yes" vote per superblock cycle. It will vote "No" +for any other triggers it receives. Note: This means that proposal votes submitted _after_ superblock trigger creation begins will _not_ be counted by some masternodes (those that have