PR471: updated book

fixes zcash#471 (comment)
and zcash#471 (comment)

Author: PaulLaux

book/src/design/actions.md

@@ -20,9 +20,8 @@ balance the transaction without doubling its size.
 
 ## Dummy notes for Orchard
 
-For Orchard, a transaction is a bundle of actions. Each action is composed of one spend and one output.
-If we would like to create a transaction with a different number of spends and outputs,
-we need to add "dummy" spends or outputs to balance their count.
+To create a transaction with a different number of spends and outputs,
+we need to add “dummy” spends or outputs to balance their count.
 A dummy spend or output is a note with a value of zero and a random recipient address.
 In the ZK proof, when the value of the spent note is zero,
 we do not verify that the corresponding spent note commitment is part of the Merkle tree.
@@ -35,11 +34,11 @@ split notes for inputs or dummy notes for outputs.
 Split notes are essentially duplicates of actual spent notes,
 but with the following differences:
 - The nullifier is randomized to prevent it from being treated as double-spending.
-- Its value is excluded from the transaction's or bundle's value balance.
+- Their value is excluded from the transaction’s or bundle’s value balance.
 
 Within the ZK proof, we verify that the commitment of each spent note (including split notes)
 is part of the Merkle tree. This ensures that the AssetBase is constructed properly,
-a note associated with this AssetBase exists within the Merkle tree.
+and that a note associated with this AssetBase exists within the Merkle tree.
 
 For further details about split notes, refer to
 [ZIP226](https://github.com/zcash/zips/blob/main/zips/zip-0226.rst).