From 7333d48e455a5c9317fe789f706a971712cf1de9 Mon Sep 17 00:00:00 2001 From: z-bowen Date: Wed, 12 Sep 2018 11:15:33 +0200 Subject: [PATCH] Problem: Some typos in the docs for election management Solution: Fixed the typos --- docs/server/source/server-reference/bigchaindb-cli.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/server/source/server-reference/bigchaindb-cli.md b/docs/server/source/server-reference/bigchaindb-cli.md index bd1ea867..63bcf9f0 100644 --- a/docs/server/source/server-reference/bigchaindb-cli.md +++ b/docs/server/source/server-reference/bigchaindb-cli.md @@ -95,7 +95,7 @@ There are multiple types of election, which each take different parameters. Belo ###### election new upsert-validator -Call an election to add/update/remove a validator from the validator set. +Create an election to add/update/remove a validator from the validator set. ```bash @@ -126,7 +126,7 @@ If the command succeeds, it will create an election and return an `election_id`. #### election approve -Approve an election by voting for it. The propsal generated by executing `bigchaindb election new ...` can approved by the validators using this command. The validator who is approving the proposal will spend all their votes i.e. if the validator has a network power of `10` then they will cast `10` votes for the proposal. +Approve an election by voting for it. The proposal generated by executing `bigchaindb election new ...` can be approved by the validators using this command. The validator who is approving the proposal will spend all their votes i.e. if the validator has a network power of `10` then they will cast `10` votes for the proposal. Below is the command line syntax and the return value,