fix: burning -> destroying.

Author: l-monninger

aptos-move/framework/evaluations/aptos-coin-mint-capability/README.md

@@ -2,4 +2,4 @@
 This directory evaluates various usages of the Aptos Coin mint capability.
 
 ## Contents
-- **[Burning](./burning):** evaluates the burning the Aptos Coin mint capability.
+- **[Destroying](./destroying):** evaluates the destroying the Aptos Coin mint capability.

aptos-move/framework/evaluations/aptos-coin-mint-capability/burning/README.md renamed to aptos-move/framework/evaluations/aptos-coin-mint-capability/destroying/README.md

@@ -1,21 +1,21 @@
-# Burning the Aptos Coin Mint Capability
-We begin with a brief section on the [procedure and intended outcomes](#procedure-and-intended-outcomes) of burning the Aptos Coin mint capability.
+# Destroying the Aptos Coin Mint Capability
+We begin with a brief section on the [procedure and intended outcomes](#procedure-and-intended-outcomes) of destroying the Aptos Coin mint capability.
 
 We then evaluate the means of [reversing this procedure](#reversing-the-procedure) and the potential [side effects](#side-effects) of doing so.
 
 We then list all identified [call sites](#call-sites) using the Aptos Coin mint capability.
 
 Finally, we the evaluate the following potential usages of the Aptos Coin mint capability as would affect critical system properties. These are:
 
-1. **[Transaction `prologue` and `epilogue`](#transaction-epilogue-and-prologue):** we assert whether the removal of the mint capability would cause failures of the transaction `prologue` and `epilogue` and thus general transaction processing.
-2. **[Token transfers](#token-transfers):** we assert whether the removal of the mint capability would cause failures of token transfers.
-3. **[FA migration](#fa-migration):** we assert whether the removal of the mint capability would cause failures of FA migration.
+1. **[Transaction `prologue` and `epilogue`](#transaction-epilogue-and-prologue):** we assert that destroying the mint capability would cause failures of the transaction `prologue` and `epilogue` and thus general transaction processing under the Governed Gas Pool feature flags. 
+2. **[Token transfers](#token-transfers):** we assert destroying the mint capability would not cause failures of token transfers.
+3. **[FA migration](#fa-migration):** we assert that destroying the mint capability would not cause failures of FA migration.
 
 ## Procedure and intended outcomes
 > [!WARNING]
 > In general, a user who has access to the `core_resource_account` signer has the ability to make and publish changes to the framework which can remove restrictions on minting, recreate capabilities, etc. However, we maintain that under the Biarritz Model, these are a tolerable risk--particularly as structures and their storage are preserved by the Aptos Move VM inherently and thus can be restored. 
 > 
-> Our evaluation thus concerns effectively burning the mint capability in such a manner that a user who holds the `core_resource_account` signer would need to introduce a new framework to restore it--as opposed to simply running a series of transactions against existing code. This renders exploits costly, but not impossible.
+> Our evaluation thus concerns effectively destroying the mint capability in such a manner that a user who holds the `core_resource_account` signer would need to introduce a new framework to restore it--as opposed to simply running a series of transactions against existing code. This renders exploits costly, but not impossible.
 
 ### Framework changes
 Because Aptos Move scripts cannot borrow structs but instead need to call `public` functions, we must update the framework to expose an `aptos_coin::destory_mint_capability_v2` which wraps the existing `public(friend) aptos_coin::destory_mint_capability`. The body of this function would be as follows: