rmn updates

Author: gfletcher-cll

src/content/ccip/concepts/architecture/offchain/overview.mdx

@@ -38,7 +38,7 @@ With the CCIP v1.6 architecture, there is a single DON called the Role DON that
 ## Role DON: Diagram and Explanation
 
 <ClickToZoom
-  src="/images/ccip/concepts/architecture/ccip-offchain-architecture.jpg"
+  src="/images/ccip/ccip-hl-v1.7.png"
   alt="CCIP Offchain Architecture"
   style="display: block; margin: 2rem auto; max-height: 60vh; width: auto;"
 />
@@ -69,18 +69,13 @@ Below are the high-level steps for the Commit OCR process and the Executing OCR
   - Each subcommittee reading from a source chain reaches consensus on the range of messages to build a merkle root.
   - A minimum threshold of valid observations is required for consensus.
 
-- **Report Building Phase**
-  - For source chains where RMN blessing is enabled, the leader of the OCR round queries the RMN nodes for the defined message ranges.
-  - RMN nodes return independently constructed merkle roots for these ranges.
-  - After validating the returned merkle roots, the leader sends the consolidated set of merkle roots to the RMN for signatures (a single signature may cover multiple merkle roots).
-
 - **Query Phase**
-  - The leader shares the Commit Report (which may include RMN signatures) with the rest of the nodes in the Role DON for validation.
+  - The leader shares the Commit Report with the rest of the nodes in the Role DON for validation.
   - Invalid observations are dropped and the remaining valid ones must meet the threshold to achieve consensus among the nodes.
 
 - **Reporting Phase**
   - A subcommittee of nodes writing to the destination chain submits the final Commit Report onchain.
-  - The report may include merkle roots from multiple sources—some of which have RMN signatures.
+  - The report may include merkle roots from multiple sources.
   - Additionally, the Commit plugin posts price reports for fee tokens, so the Commit Report can contain a combination of merkle roots and price reports.
 
 ### Executing OCR Process

src/content/ccip/concepts/architecture/onchain/evm/overview.mdx

@@ -79,9 +79,7 @@ The following diagram illustrates the key onchain components:
 ### Destination Blockchain
 
 1. **Commit Phase**
-   - The final OCR report from the Committing DON is recorded onchain in the OffRamp contract via the `commit` function. This OCR report may include a mix of blessed and non-blessed roots and price updates from multiple source chains.
-   - If the OCR report includes **blessed** merkle roots from RMN-enabled source chains, the OffRamp verifies the RMN node signatures onchain via the `RMNRemote` contract.
-   - The OffRamp also validates that all **unblessed** merkle roots originate from the source chains where RMN is disabled.
+   - The final OCR report from the Committing DON is recorded onchain in the OffRamp contract via the `commit` function. This OCR report may include a mix of merkle roots and price updates from multiple source chains.
    - The OffRamp emits a `CommitReportAccepted` event, confirming that a valid commit has been accepted.
 
 1. **Secondary Offchain Processing**