more removal

packages/docs/pages/integrating-with-namada/light-sdk/usage/transactions.mdx

@@ -3,7 +3,6 @@ The transaction module exposes various modules (objects) to construct transactio
 
 ```rust
 pub mod account; // contains functions to create transactions for account module
-pub mod bridge; // contains functions to create transactions for bridge module
 pub mod governance; // contains functions to create transactions for governance module
 pub mod ibc; // contains functions to create transactions for ibc module
 pub mod pgf; // contains functions to create transactions for pgf module
@@ -57,20 +56,6 @@ impl InitAccount {
 
 A public key can be constructed from a string using the `::from_str()` method. The `vp_code_hash` is a hash that is found under the `wasm` folder.
 
-### Bridge
-
-```rust
-pub use namada_sdk::eth_bridge_pool::{GasFee, TransferToEthereum};
-pub struct BridgeTransfer(Tx);
-impl BridgeTransfer {
-    pub fn new(
-        transfer: TransferToEthereum,
-        gas_fee: GasFee,
-        args: GlobalArgs,
-    ) -> Self {...}
-}
-```
-
 ### Governance
 
 ```rust

packages/docs/pages/introduction/privacy.mdx

@@ -6,7 +6,7 @@ Namada provides the largest possible unified shielded set in the multichain, com
 * Namada can also seed data protection to users who want to use an asset originating from one base chain on another chain, without losing data protection
 * Namada retrofits data protection to assets that were created and already used in transparent chains
 
-Users should be aware that they can still expose personal information when transferring funds into and out of Namada via the Ethereum bridge or IBC. For example, a user bridging WETH from Ethereum may be able to obfuscate their on-chain identities to *some* on-chain observers by interacting with Smart contract based shielding protocols or centralized exchanges. However, a user transferring a non-fungible token or a low liquidity token that relies on price discovery on-chain, will leak more information by the nature of their asset holdings. This is also true of tokens transferred into and out of Namada via IBC. Once inside the shielded set, a user can perform *shielded actions* such as triggering a cross chain swap. 
+Users should be aware that they can still expose personal information when transferring funds into and out of Namada via IBC. For example, a user bridging WETH from Ethereum may be able to obfuscate their on-chain identities to *some* on-chain observers by interacting with Smart contract based shielding protocols or centralized exchanges. However, a user transferring a non-fungible token or a low liquidity token that relies on price discovery on-chain, will leak more information by the nature of their asset holdings. This is also true of tokens transferred into and out of Namada via IBC. Once inside the shielded set, a user can perform *shielded actions* such as triggering a cross chain swap. 
 
 Shielded actions are not limited to application chains that are IBC compatible, it works with any chain that is connected to Namada, e.g. Ethereum, and the actions can be generalized to interact with any dApp, such as trading NFTs or staking ETH. For the time being, the only shielded action available is cross chain transfers, but more will be added in the future.
 

packages/docs/pages/networks/testnets/faq.mdx

@@ -17,10 +17,6 @@
 There are a few more, but we leave it to you as a challenge to find out which these are 🤔 
 HINT: `namadac balance`
 
-### **Q: How do I use the Ethereum Bridge?**
-
-**A:** The Ethereum Bridge is not yet implemented. Keep an eye on the [Changelog](https://github.com/anoma/namada/tree/main/.changelog) 👀 to see when it will be officially released.
-
 ### **Q: How can I make an IBC transfer?**
 
 **A:** As of `v0.23.1` you can now follow the docs [here!](../../users/ibc.mdx)

packages/docs/pages/users/governance/on-chain-governance.mdx

@@ -173,17 +173,6 @@ For a pgf proposal that is to be executed on an IBC chain, the "Internal" data s
     }
 ```
 
-### ETH Bridge Proposal
-
-```json
-"data" : "<hex-encoded-bytes-of-what-will-be-signed-by-validators>"
-```
-
-<Callout type="warning">
-**Note**:
-The encoding will be submitted as a string
-</Callout>
-
 
 ## Submitting the proposal
 As soon as your `proposal.json` file is ready, you can submit the proposal with (make sure to be in the same directory as the `proposal.json` file):