Improve explanations

explanations/contract.txt

@@ -1,5 +1,3 @@
-This is a vault resource in a smart contract that can be stored in a users account.
+This smart contract defines a vault resource designed to be stored within a user's account. The vault serves as a secure container for managing a user's token balance, tracking the total amount of tokens held while providing essential functionality for withdrawing and depositing tokens.
 
-It keeps track of the total balance of tokens as well as the functions to withdraw and deposit tokens.
-
-Interfaces such as Provider, Receiver, and Balance are included that allow users to send you money when executing a transaction.
+The vault incorporates key interfaces such as Provider, Receiver, and Balance, which enable token transactions. These interfaces allow users to send and receive tokens efficiently during transactions, ensuring compatibility and interoperability within the broader ecosystem. By integrating these interfaces, the vault resource facilitates streamlined token management and enables robust interactions between accounts in the smart contract.

explanations/transaction.txt

@@ -1,5 +1,5 @@
-Here we are creating a new Vault resource into an account.
+This transaction creates a new Vault resource and stores it securely within the user's private storage. The Vault serves as a container for managing tokens within the account.
 
-When that is created and stored into their private storage, we then create public capabilities that others can use to check balance, or deposit tokens.
+After storing the Vault, the transaction establishes public capabilities linked to it. These capabilities allow others to interact with the Vault, enabling actions such as checking its balance or depositing tokens. This setup ensures the Vault is both accessible for approved interactions and protected within the account's private storage.
 
-Once we do that, we check to make sure that the capabilities were indeed created and then we are done with the transaction.
+Finally, the transaction verifies that the public capabilities were successfully created, ensuring the Vault is properly set up for use.