CH07: correction: the utxo set is not stored in ram

chapters/authorization-authentication.adoc

@@ -477,9 +477,9 @@ ability to create custom transaction scripts, and each customer would
 have to understand how to create a transaction using custom scripts.
 Furthermore, the resulting transaction would be about five times larger
 than a simple payment transaction, because this script contains very
-long public keys. The burden of that extra-large transaction would be
-borne by the customer in the form of fees. Finally, a large transaction
-script like this would be carried in the UTXO set in RAM in every full
+long public keys. The burden of that extra data would be
+borne by the customer in the form of extra transaction fees. Finally, a large transaction
+script like this would be carried in the UTXO set in every full
 node, until it was spent. All of these issues make using complex scriptPubKeys
 difficult in practice.
 
@@ -734,7 +734,7 @@ UTXO set. +RETURN+ outputs are recorded on the blockchain, so they
 consume disk space and contribute to the increase in the blockchain's
 size, but they are not stored in the UTXO set and therefore do not bloat
 the UTXO memory pool and burden full nodes with the cost of more
-expensive RAM.
+expensive database operations.
 
 +RETURN+ scripts look like this: