nit

Author: aelmanaa

src/features/ccip/SenderContractCallout.mdx

@@ -9,7 +9,7 @@ This example is simplified for educational purposes. For production code, please
 
 - **Understand `allowOutOfOrderExecution` Usage**: This example sets `allowOutOfOrderExecution` to `true` (see [GenericExtraArgsV2](/ccip/api-reference/evm/v1.6.0/client#genericextraargsv2)). Read the [Best Practices: Setting `allowOutOfOrderExecution`](/ccip/concepts/best-practices/evm#setting-allowoutoforderexecution) to learn more about this parameter.
 
-- **Understand CCIP Service Limits**: Be aware of the [CCIP Service Limits](/ccip/service-limits/evm) on items such as message data size, execution gas, and the number of tokens per transaction. If your requirements exceed these limits, you may need to [contact the Chainlink Labs Team](https://chain.link/ccip-contact).
+- **Understand CCIP Service Limits**: Review the [CCIP Service Limits](/ccip/service-limits) for constraints on message data size, execution gas, and the number of tokens per transaction. If your requirements exceed these limits, you may need to [contact the Chainlink Labs Team](https://chain.link/ccip-contact).
 
 Following these best practices ensures that your contract is robust, future-proof, and compliant with CCIP standards.