Update 3.1_aggregation_mode.md

Author: cliraa

docs/3_guides/3.1_aggregation_mode.md

@@ -1,6 +1,6 @@
-## Aggregation Mode L2 integration example
+## Proof Aggregation Service L2 integration example
 
-This guide demonstrates how to build a dummy L2 application that integrates with Aligned Aggregation Mode. The L2 does not post state diffs or any data to Ethereum, only commitments. The prover has to prove that:
+This guide demonstrates how to build a dummy L2 application that integrates with Aligned's Proof Aggregation Service. The L2 does not post state diffs or any data to Ethereum, only commitments. The prover has to prove that:
 
 1. The state database used in the proof must match the commitment stored in the on-chain contract. This is validated by computing the commitment of the received data in the zkvm and then exposing it as a public input.
 2. The users performing the transfers have enough balance
@@ -15,8 +15,8 @@ The code can be viewed at `examples/l2`.
 
 This Layer 2 (L2) system operates in two main steps:
 
--   Off-chain execution and proof generation + verification with Aligned Verification Layer (a.k.a Fast Mode).
--   On-chain state update via proof verification with Aligned Aggregation Mode.
+-   Off-chain execution and proof generation + verification with Aligned's Proof Verification Layer.
+-   On-chain state update via proof verification with Aligned's Proof Aggregation Service.
 
 In Step 1, we execute user transfers and generate a zkVM-based proof of the state transition, which is submitted to Aligned’s verification layer.