grammarly check

build/contract-integrations/native-token-transfers/configuration/rate-limiting.md

@@ -7,12 +7,12 @@ description: Learn about rate limits in Wormhole NTT by configuring send/receive
 
 The Native Token Transfer (NTT) framework provides configurable per-chain rate limits for sending and receiving token transfers. Integrators can manage these limits via their own governance processes to quickly adapt to on-chain activity.
 
-If a transfer is rate-limited on the source chain and queueing is enabled via `shouldQueue = true`, the transfer is placed into an outbound queue and can be released after the duration of the rate limit expires.
+If a transfer is rate-limited on the source chain and queueing is enabled via `shouldQueue = true`, the transfer is placed into an outbound queue and can be released after the rate limit expires.
 
 You can configure the following limits on every chain where NTT is deployed directly using the manager:
 
 - **Sending limit** - a single outbound limit for sending tokens from the chain
-- **Per-chain receiving limits** - the maximum receiving limit, which can be configured on a per-chain basis. For example, allowing `100` tokens to be received from Ethereum, but only 50 tokens to be received from Arbitrum
+- **Per-chain receiving limits** - the maximum receiving limit, which can be configured on a per-chain basis. For example, allowing `100` tokens to be received from Ethereum but only 50 tokens to be received from Arbitrum
 
 Rate limits are replenished every second over a fixed duration. While the default duration is 24 hours, the value is configurable at contract creation. Rate-limited transfers on the destination chain are added to an inbound queue with a similar release delay.
 
@@ -35,7 +35,7 @@ To configure or update the sending and receiving rate limits, follow these steps
     ```
 
      - `outbound` - sets the maximum tokens allowed to leave the chain
-     - `inbound` - configures per-chain receiving limits for tokens arriving from specific chains
+     - `inbound` - configure per-chain receiving limits for tokens arriving from specific chains
 
 3. **Push the configuration** - use the NTT CLI to synchronize the updated configuration with the blockchain
 
@@ -85,7 +85,7 @@ To configure or update the sending and receiving rate limits, follow these steps
 When a transfer exceeds the rate limit, it is held in a queue and can be released after the set rate limit duration has expired. The sending and receiving queuing behavior is as follows:
 
 - **Sending** - if an outbound transfer violates rate limits, users can either revert and try again later or queue their transfer. Users must return after the queue duration has expired to complete sending their transfer
-- **Receiving** - if an inbound transfer violates rate limits, it is held in a queue. Users or relayers must return after the queue duration has expired to complete receiving their transfer on the destination chain
+- **Receiving** - if an inbound transfer violates rate limits, it is in a queue. Users or relayers must return after the queue duration has expired to complete receiving their transfer on the destination chain
 
 Queuing is configured dynamically during each transfer by passing the `shouldQueue` parameter to the [transfer function](https://github.com/wormhole-foundation/native-token-transfers/blob/5e7ceaef9a5e7eaa13e823a67c611dc684cc0c1d/evm/src/NttManager/NttManager.sol#L171-L182){target=\_blank} in the `NttManager` contract.