DOC-1308: Add CCIP Service Limits reference to the Best Practices callout (#2892)

* DOC-1308 Add CCIP Service Limits reference to the Best Practices callout

* nit

---------

Co-authored-by: aelmanaa <[email protected]>
Co-authored-by: Amine E. <[email protected]>

Author: SyedAsadKazmi

src/features/ccip/SenderContractCallout.mdx

@@ -1,6 +1,6 @@
 import { Aside } from "@components"
 
-<Aside type="caution" title="Sender Contract Best Practices">
+<Aside type="caution" title="Best Practices">
 This example is simplified for educational purposes. For production code, please adhere to the following best practices:
 
 - **Do Not Hardcode `extraArgs`**: In this example, `extraArgs` are hardcoded within the contract for simplicity. It is recommended to make `extraArgs` mutable. For instance, you can construct `extraArgs` off-chain and pass them into your function calls, or store them in a storage variable that can be updated as needed. This approach ensures that `extraArgs` remain backward compatible with future CCIP upgrades. Refer to the [Best Practices](/ccip/concepts/best-practices/evm) guide for more information.
@@ -9,6 +9,8 @@ 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**: 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.
 
 </Aside>