Update docs/cdk/architecture/cdk-pp-highlevel-arch.md

Co-authored-by: Arnau Bennassar <arnaubennassar5@gmail.com>

Author: mitchpolygon

docs/cdk/architecture/cdk-pp-highlevel-arch.md

@@ -11,7 +11,7 @@ Here is a step by step flow of transactions starting from when users submit tran
 3. The transaction-pool manager proxies all transaction data to the CDK Erigon sequencer.
 4. CDK Erigon sequencer executes transactions, puts the transactions in blocks
 5. CDK Erigon sequencer syncs all transaction data with any CDK Erigon RPC node.
-6. AggSender gets batch data from the CDK Erigon sequencer, uses the data to generate certificates, and submits the certificates to the JSON-RPC API.
+6. AggSender gets batch data from the CDK Erigon sequencer, uses the data to generate certificates, and submits the certificates to the AggLayer RPC.
 7. The AggLayer RPC checks validity of the certificate by asserting that the balances of the bridge interactions are consistent with the liquidity of the chain
 8. After validating the certificates, the JSON-RPC API sends a request to generate a proof, together with the necessary data (including the certificates), to the SP1 prover. 
 9. Once the proof is received from the SP1 prover, the JSON-RPC API sends it to L1.