From bfbfd4677ba4696a6c507f02692f73afc3485bec Mon Sep 17 00:00:00 2001 From: polinavino Date: Fri, 5 Jul 2019 00:10:29 -0400 Subject: [PATCH] More corrections --- plutus-book/doc/03-UTxO.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plutus-book/doc/03-UTxO.adoc b/plutus-book/doc/03-UTxO.adoc index c0170eb3dac..51093980bdd 100644 --- a/plutus-book/doc/03-UTxO.adoc +++ b/plutus-book/doc/03-UTxO.adoc @@ -17,7 +17,7 @@ but rather from transaction to transaction. Each transaction has inputs (where the money being spent is coming from), and outputs (where this money is going). Note that the body of a transaction may also contain other data, as we will see later when we examine the extended -UTxO model in the <<_shelley_script_extended_utxo_model>> chapter. +UTxO model in the <<09-extended#09-extended>> chapter. Consider the data flow graph below. The black lines represent unspent outputs of transactions, and the red lines represent these outputs being used as inputs @@ -72,7 +72,7 @@ the intended payees. This is, in a very general sense, the goal of smart contracts. Let us explore what is going on during the processing of a UTxO transaction event more formally. For the basic transaction -model we discuss here, refer to <>: +model we discuss here, refer to Figure <>. [#utxo-definitions] image::UTxO.png[]