chore: remove mention of DAO handled by Zama

Author: melanciani

docs/confidential-wrapper.md

@@ -10,13 +10,12 @@ This document gives an overview of the **Confidential Wrapper,** a smart contrac
 * **Unwrapping**: Converting confidential tokens back into ERC-20 tokens.
 * **Rate**: The conversion ratio between underlying token units and confidential token units (due to decimal differences).
 * **Operator**: An address authorized to transfer confidential tokens on behalf of another address.
-* **Owner**: The owner of the wrapper contract. In the FHEVM protocol, this is initially set to a DAO [governance](governance.md) contract handled by Zama. Ownership will then be transferred to the underlying token's owner.
+* **Owner**: The owner of the wrapper contract. In the FHEVM protocol, this is initially set to the Protocol DAO governance (see [governance.md](governance.md)). Ownership will then be transferred to the underlying token's owner.
 * **Registry**: The registry contract that maps ERC-20 tokens to their corresponding confidential wrappers. More information [here](registry-contract.md).
 * **ACL**: The Access Control List (ACL) contract that manages the permissions for encrypted amounts. More information in the [FHEVM library documentation](https://docs.zama.org/protocol/protocol/overview/library#access-control).
 * **Input proof**: A proof that the encrypted amount is valid. More information in the [`relayer-sdk` documentation](https://docs.zama.org/protocol/relayer-sdk-guides/fhevm-relayer/input).
 * **Public decryption**: A request to publicly decrypt an encrypted amount. More information in the [`relayer-sdk` documentation](https://docs.zama.org/protocol/relayer-sdk-guides/fhevm-relayer/decryption/public-decryption).
 
-
 ## Contract information
 
 | Resource | Link |
@@ -367,4 +366,4 @@ wrapper.supportsInterface(type(IERC165).interfaceId);
 
 ## Upgradeability
 
-The contract uses **UUPS (Universal Upgradeable Proxy Standard)** with 2-step ownership transfer. Only the owner can upgrade the contract. Initially, the owner is set to a DAO [governance](governance.md) contract handled by Zama. Ownership will then be transferred to the underlying token's owner.
+The contract uses **UUPS (Universal Upgradeable Proxy Standard)** with 2-step ownership transfer. Only the owner can upgrade the contract. Initially, the owner is set to the Protocol DAO governance (see [governance.md](governance.md)). Ownership will then be transferred to the underlying token's owner.

docs/governance.md

@@ -73,10 +73,6 @@ flowchart
 
 An example of governance architecture for the token and its OFT contracts can be found in the [zama-token.md](zama-token.md) file.
 
-## Contract addresses
-
-All deployed governance contract addresses can be found in the [addresses directory](addresses/README.md).
-
 ## Operator wallets
 
 Each operator maintains their own wallets for participating in the DAO and multisigs. Operators are free to choose how they instantiate their wallet but are strongly encouraged to use a hardware, MPC, or multisig wallet. Where possible, the same wallet may be used for multiple multisigs.

docs/registry-contract.md

@@ -10,7 +10,7 @@ This document explains the **Confidential Token Wrappers Registry,** an onchain
 * **TokenWrapperPair**: A pair of a token and its confidential wrapper.
 * **Valid**: A valid confidential wrapper has been verified by the registry owner and can be used to wrap and unwrap tokens from the underlying token.
 * **Invalid**: An invalid confidential wrapper has been revoked by the registry owner and should not be used to wrap and unwrap tokens from the underlying token.
-* **Owner**: The owner of the registry. In the FHEVM protocol, this is a DAO governance contract handled by Zama.
+* **Owner**: The owner of the registry. In the FHEVM protocol, this is the Protocol DAO governance (see [governance.md](governance.md)).
 
 ## Contract information