clarify note (#2128)

Co-authored-by: Karim H. <[email protected]>

src/content/ccip/concepts/index.mdx

@@ -63,7 +63,7 @@ The Risk Management Network has two main modes of operation:
 
 - **Blessing:** Each Risk Management node monitors all Merkle roots of messages committed on each destination chain. The Committing DON commits these Merkle roots. (More information on Merkle roots can be found on the [architecture page](/ccip/architecture)). The Risk Management node independently reconstructs the Merkle tree by fetching all messages on the source chain. Then, it checks for a match between the Merkle root committed by the Committing DON and the root of the reconstructed Merkle tree. If both Merkle roots match, the Risk Management node blesses the root to the Risk Management contract on the destination chain. The Risk Management contract tracks the votes. When a quorum is met, the Risk Management contract dubs the Merkle root **blessed**.
 
-- **Cursing:** If a Risk Management node detects an anomaly, the Risk Management node will curse the CCIP system. After a quorum of votes has been met, the Risk Management contract dubs the CCIP system **cursed**. CCIP will automatically pause on that chain and wait until the contract owner assesses the situation before potentially lifting the curse. There are two cases where Risk Management nodes pause CCIP:
+- **Cursing:** If a Risk Management node detects an anomaly, the Risk Management node will curse the CCIP system. Cursing is blockchain-specific and will only affect lanes going to and from the relevant blockchain. After a quorum of votes has been met, the Risk Management contract dubs the CCIP system **cursed**. CCIP will automatically pause on that chain and wait until the contract owner assesses the situation before potentially lifting the curse. There are two cases where Risk Management nodes pause CCIP:
 
   - **Finality violation:** A deep reorganization which violates the safety parameters set by the Risk Management configuration occurs on a CCIP chain.