Additional changes based on review comments

* Trimmed the sample transaction list
* Modified mirror node requirements to note changes to existing
  APIs rather than new APIs.

Signed-off-by: Joseph S. <121976561+jsync-swirlds@users.noreply.github.com>

Author: jsync-swirlds

HIP/hip-1313.md

@@ -127,14 +127,15 @@ This field applies to transactions involving entity creation, such as:
 - `TokenMint`
 - `ContractCall` (for entities created inside the contract)
 - `ContractCreate`
-- `EthereumTransaction` (for entities created inside)
 - `TokenCreate`
 - `TokenAssociateToAccount`
 - `TokenAirdrop`
 - `TokenClaimAirdrop`
 
 For example, a `CryptoTransfer` that creates accounts uses high-volume pricing
 for those creations but standard throttles for the transfers themselves.
+Note that EVM transactions which create entities are not included in this HIP.
+EVM specific behavior will be defined in a subsequent HIP for greater clarity.
 
 ### High-Volume Throttles Configuration
 High-volume throttles are defined separately in the network's throttle settings.
@@ -311,8 +312,10 @@ For high-volume transactions:
    `maxTransactionFee`).
 
 ## Mirror Node Changes
-1. Mirror Node updated API for high volume rates
-2. Mirror Node updated API for high volume rate estimates
+1. Add high volume fields to relevant APIs (e.g. `/api/v1/transactions`,
+   `/api/v1/transactions/{id}` and the list of transactions
+   within `/api/v1/accounts/{id}`)
+2. Incorporate high volume as an estimation option in fee estimation.
 
 ## Backwards Compatibility
 No changes for transactions without the `high_volume` flag. Existing