diff --git a/docs/bridges/Legacy Bridges UI/using-omnibridge/README.md b/docs/bridges/Legacy Bridges UI/using-omnibridge/README.md
index 9fa31440..f09d176d 100644
--- a/docs/bridges/Legacy Bridges UI/using-omnibridge/README.md	
+++ b/docs/bridges/Legacy Bridges UI/using-omnibridge/README.md	
@@ -108,7 +108,7 @@ The steps below assume:
    You can monitor the confirmation and AMB request execution with the [AMB Live Monitoring tool](https://alm-bridge-monitor.gnosischain.com/). Specify the hash (tx id) of the transaction used to call `relayTokens` in the ALM entry page to check the status of the AMB request initiated by this transaction in real time. If the AMB request is executed successfully:
 
 - **If token has not been transferred with AMB before:** If this is the first transaction for this particular token using the AMB, a new ERC677 token contract will be deployed to Gnosis. The token contract will be initialized with the same symbol and decimals as for the original token on Ethereum. The name of the new token will be extended with the letters "on xDai" (e.g. "Dai Stablecoin v1.0 on xDai"). At the end, the requested amount of tokens will be minted and sent to the account that called `relayTokens`.
-- **If token has been previously transferred with AMB:** If If the ERC677 token has already been registered by the mediator for the original ERC20 token, deployment of the contract will be skipped but the requested amount of tokens will be minted and sent to the account that called `relayTokens`.
+- **If token has been previously transferred with AMB:** If the ERC677 token has already been registered by the mediator for the original ERC20 token, deployment of the contract will be skipped but the requested amount of tokens will be minted and sent to the account that called `relayTokens`.
   Once the process is complete and indexed by BlockScout, it is possible to find the token contract on Gnosis Chain. Check out the [Bridged token registry](https://blockscout.com/xdai/mainnet/bridged-tokens) to view it.
 
 #### Gnosis -> Ethereum
diff --git a/docs/node/manual/validator/Run Client/lighthouse.md b/docs/node/manual/validator/Run Client/lighthouse.md
index e30e298e..b9997619 100644
--- a/docs/node/manual/validator/Run Client/lighthouse.md	
+++ b/docs/node/manual/validator/Run Client/lighthouse.md	
@@ -5,7 +5,7 @@ title: Lighthouse
 # Run Validator: Lighthouse
 
 :::caution
-The Validator requires a Consensus Client (also known as Beacon Node) in order to operate. See See [Step 3: Run Beacon Node - Lighthouse](../../beacon/lighthouse.md) for more information.
+The Validator requires a Consensus Client (also known as Beacon Node) in order to operate. See [Step 3: Run Beacon Node - Lighthouse](../../beacon/lighthouse.md) for more information.
 :::
 
 ## Option 1: Run as System Process {#system-process}
diff --git a/docs/technicalguides/custom-signers/privy.md b/docs/technicalguides/custom-signers/privy.md
index 9881e2b7..197f2d60 100644
--- a/docs/technicalguides/custom-signers/privy.md
+++ b/docs/technicalguides/custom-signers/privy.md
@@ -33,7 +33,7 @@ Also, note the **App ID** from the settings, we will need to configure while ini
 
 ### 3. Setup Privy Provider and Gnosis Config
 
-We can now initialize **PrivyProvider**. Replace the App ID field with your own Privy App ID and import the chains you want to support in your dapp. In our case, we have imported **gnosisChiado** and **gnosis** from viem. We can also also customize with theme, logo and , colours and other [configs](https://docs.privy.io/guide/react/configuration/appearance#app-name).
+We can now initialize **PrivyProvider**. Replace the App ID field with your own Privy App ID and import the chains you want to support in your dapp. In our case, we have imported **gnosisChiado** and **gnosis** from viem. We can also customize with theme, logo and , colours and other [configs](https://docs.privy.io/guide/react/configuration/appearance#app-name).
 
 ```shell
 'use client';