Use component amendment disclaimers for MPTs

docs/references/protocol/transactions/types/mptokenauthorize.md

@@ -15,7 +15,7 @@ An MPTokenAuthorize transaction controls whether an account can hold a given [Mu
 - An account revokes their willingness to hold an MPT, deleting the [MPToken entry][]. This can only be done if their balance of the given MPT is zero.
 - For an MPT that uses allow-listing, an issuer grants or revokes permission for another account to hold the given MPT.
 
-_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
+{% amendment-disclaimer name="MPTokensV1" /%}
 
 {% raw-partial file="/docs/_snippets/tx-fields-intro.md" /%}
 

docs/references/protocol/transactions/types/mptokenissuancecreate.md

@@ -15,7 +15,7 @@ If the transaction is successful, the newly created token is owned by the accoun
 
 Whenever your query returns an `MPTokenIssuance` transaction response, there will always be an `mpt_issuance_id` field on the Transaction Metadata page.
 
-_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
+{% amendment-disclaimer name="MPTokensV1" /%}
 
 ## Example MPTokenIssuanceCreate JSON
 

docs/references/protocol/transactions/types/mptokenissuancedestroy.md

@@ -12,7 +12,7 @@ The `MPTokenIssuanceDestroy` transaction is used to remove an `MPTokenIssuance`
 
 If this operation succeeds, the corresponding `MPTokenIssuance` is removed and the owner’s reserve requirement is reduced by one. This operation must fail if there are any holders of the MPT in question.
 
-_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
+{% amendment-disclaimer name="MPTokensV1" /%}
 
 ## Example MPTokenIssuanceDestroy JSON
 

docs/references/protocol/transactions/types/mptokenissuanceset.md

@@ -10,7 +10,7 @@ status: not_enabled
 
 Use this transaction to update a mutable property for a Multi-purpose Token. The transaction flags determine which change(s) to apply.
 
-_(Requires the [MPTokensV1 amendment][] {% not-enabled /%}.)_
+{% amendment-disclaimer name="MPTokensV1" /%}
 
 ## Example