Edited ch10.asciidoc with Atlas code editor

ch10.asciidoc

@@ -135,7 +135,7 @@ Jing's node is listening for new blocks, propagated on the bitcoin network, as d
 
 === Aggregating Transactions into Blocks
 
-After validating transactions, a bitcoin node will add them to the _memory pool_, or _transaction pool_, where transactions await until they can be included (mined) into a block. Jing's node collects, validates, and relays new transactions just like any other node. Unlike other nodes, however, Jing's node will then aggregate these transactions into a _candidate block_.
+((("mining and consensus", "aggregating transactions into blocks", id="MACaggreg10")))((("transactions", "aggregating into blocks", id="Taggreg10")))((("blocks", "aggregating transactions into", id="Baggreg10")))After validating transactions, a bitcoin node will add them to the _memory pool_, or _transaction pool_, where transactions await until they can be included (mined) into a block. Jing's node collects, validates, and relays new transactions just like any other node. Unlike other nodes, however, Jing's node will then aggregate these transactions into a _candidate block_.
 
 Let's follow the blocks that were created during the time Alice bought a cup of coffee from Bob's Cafe (see <<cup_of_coffee>>). Alice's transaction was included in block 277,316. For the purpose of demonstrating the concepts in this chapter, let's assume that block was mined by Jing's mining system and follow Alice's transaction as it becomes part of this new block.
 
@@ -349,7 +349,7 @@ include::code/satoshi-words.cpp[]
 ----
 ====
 
-We compile the code with the GNU C++ compiler and run the resulting executable, as shown in <<satoshi_words_run>>.
+We compile the code with the GNU C++ compiler and run the resulting executable, as shown in <<satoshi_words_run>>.((("", startref="MACaggreg10")))((("", startref="Baggreg10")))((("", startref="Taggreg10")))
 
 [[satoshi_words_run]]
 .Compiling and running the satoshi-words example code