From a307c531c3414ca07e33e808454d06abc51c78c6 Mon Sep 17 00:00:00 2001
From: z-bowen <zach.bowen@gmail.com>
Date: Tue, 28 Aug 2018 17:40:11 +0200
Subject: [PATCH] Problem: `status` needed an explanation in the docs

Solution: Wrote one
---
 docs/server/source/server-reference/bigchaindb-cli.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/server/source/server-reference/bigchaindb-cli.md b/docs/server/source/server-reference/bigchaindb-cli.md
index cafc12f5..80dbccdb 100644
--- a/docs/server/source/server-reference/bigchaindb-cli.md
+++ b/docs/server/source/server-reference/bigchaindb-cli.md
@@ -152,4 +152,6 @@ public_key=<e_pub_key>
 power=<e_power>
 node_id=<e_node_id>
 status=<status>
-```
\ No newline at end of file
+```
+
+The `public_key`, `power`, and `node_id` are the same values used in the `upsert-validator new` command that originally triggered the election. `status` takes three possible values, `ongoing`, if the election has not yet reached a 2/3 majority, `concluded`, if the election reached the 2/3 majority needed to pass, or `inconclusive`, if the validator set changed while the election was in process, rendering it undecidable.
\ No newline at end of file