revert wording

Author: kmurphypolygon

docs/cdk/agglayer/agglayer-go.md

@@ -33,7 +33,7 @@ The diagram below shows the full start-up, running, and shutdown sequence for th
 
 ## Production set up
 
-1. Ensure only one instance of AggLayer is running at a time.
+1. Ensure only one instance of the AggLayer is running at a time.
 2. Use a containerized setup, or OS level service manager/monitoring system, for automatic restarts in the case of failures.
 
 ### Prerequisites

docs/cdk/agglayer/agglayer-rs.md

@@ -10,8 +10,8 @@ It replaces the previous [Golang implementation](agglayer-go.md).
 
 ### Components
 
-- Unified bridge: A shared bridge contract for all AggLayer-connected chains, allowing for the transfer of fungible tokens. 
-- Pessimistic proof: A novel ZKP that provides safety for the tokens deposited to the unified bridge by ensuring no chain can withdraw more tokens of any type than have been deposited into it. Pessimistic proofs are validated by the verifier contract on the L1. 
+- Unified bridge: A shared bridge contract for all AggLayer-connected chains, allowing for the transfer of native assets. 
+- Pessimistic proof: A novel ZKP that provides safety for the assets on the unified bridge by ensuring no chain can withdraw more tokens of any type than have been deposited into it. Pessimistic proofs are validated by the verifier contract on the L1. 
 
 ### Data flow