From e615e28cc4975c1f9631bdb7d694d5150890201a Mon Sep 17 00:00:00 2001
From: Troy McConaghy <troy@bigchaindb.com>
Date: Mon, 3 Jul 2017 14:52:40 +0200
Subject: [PATCH] output --> output_index & removed unneeded para.

---
 docs/server/source/data-models/inputs-outputs.rst | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/docs/server/source/data-models/inputs-outputs.rst b/docs/server/source/data-models/inputs-outputs.rst
index c67f0317..7c3a51c5 100644
--- a/docs/server/source/data-models/inputs-outputs.rst
+++ b/docs/server/source/data-models/inputs-outputs.rst
@@ -19,7 +19,7 @@ An input has the following structure:
        "owners_before": ["<The public_keys list in the output being spent>"],
        "fulfillment": "<Fulfillment URI fulfilling the condition of the output being spent>",
        "fulfills": {
-           "output": "<Index of the output being spent (an integer)>",
+           "output_index": "<Index of the output being spent (an integer)>",
            "transaction_id": "<ID of the transaction containing the output being spent>"
        }
    }
@@ -96,9 +96,6 @@ to set a maximum allowed fulfillment length,
 so the only real option was to
 :ref:`set a maximum allowed transaction size <Enforcing a Max Transaction Size>`.
 
-If someone tries to make a condition where the output of a threshold condition feeds into the input of another “earlier” threshold condition (i.e. in a closed logical circuit), then their computer will take forever to calculate the (infinite) “condition URI”, at least in theory. In practice, their computer will run out of memory or their client software will timeout after a while.
-
-
 
 .. note::