From 5e1480abd7cb6d0516f866da7584f3ae39da0cb1 Mon Sep 17 00:00:00 2001 From: Rodolphe Marques Date: Wed, 5 Jul 2017 10:14:40 +0200 Subject: [PATCH] Fixed broken reference --- docs/server/source/data-models/inputs-outputs.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/server/source/data-models/inputs-outputs.rst b/docs/server/source/data-models/inputs-outputs.rst index 76d7062d..696dac83 100644 --- a/docs/server/source/data-models/inputs-outputs.rst +++ b/docs/server/source/data-models/inputs-outputs.rst @@ -29,7 +29,7 @@ A CREATE transaction should have exactly one input. That input can contain one o See the reference on :ref:`inputs ` for more description about the meaning of each field. To calculate a fulfillment URI, you can use one of the -:ref:`BigchainDB drivers or transaction-builders `, +:ref:`BigchainDB drivers or transaction-builders `, or use a low-level crypto-conditions library as illustrated in the page about `Handcrafting Transactions `_. @@ -52,7 +52,7 @@ See the reference on :ref:`outputs ` for more description about the mean Below is a high-level description of what goes into building a ``condition`` object. To construct an actual ``condition`` object, you can use one of the -:ref:`BigchainDB drivers or transaction-builders `, +:ref:`BigchainDB drivers or transaction-builders `, or use a low-level crypto-conditions library as illustrated in the page about `Handcrafting Transactions `_.