removed global_config.mdx

Author: web3jenks

docs/developers/staking_backend/services/global_config.mdx

@@ -49,7 +49,7 @@ properly set up:
 - **RabbitMQ** - [Setup Guide](https://www.rabbitmq.com/download.html)  
   _Handles message queuing between system components_
 
-- **Global Configuration** - [Setup Guide](./services/global_config)  
+- **Global Configuration** - Setup guide will be available soon.  
   _Defines system-wide parameters for all services_
 
 {/* Database Migration (Optional) - Clone Phase-1 database snapshot, apply snapshot to new MongoDB clusters.

docs/developers/staking_backend/staking_backend.mdx

@@ -49,18 +49,12 @@ Initialize your validator key with `babylond init` will create the BABY key you
 need for consensus participation and a BLS key used in checkpointing and timestamping 
 to Bitcoin blockchain.
 
-See [3. Key Management](/operators/babylon_validators/installation_guide/#3-key-management) 
-for more details.
-
 ### 3. Create a Validator
 Instead of using `staking` module of Cosmos SDK, Babylon Genesis uses `checkpointing` 
 module for validator registration and management. 
 
 To create a validator, use `babylond tx checkpointing create-validator` command.
 
-See [4. Create a Validator](/operators/babylon_validators/installation_guide/#4-create-a-validator) 
-for more details.
-
 ### 4. Verify Your Validator
 
 To verify your validator, first get your validator's operator address with 
@@ -71,38 +65,6 @@ registration request is in the queue.
 Initially, your status will be `0 - BOND_STATUS_UNBONDED`. When active, your 
 status will change to `3 - BOND_STATUS_BONDED`.
 
-See [5. Verify Your Validator](/operators/babylon_validators/installation_guide/#51-verifying-validator-setup) 
-for more details and rules.
-
 ## Communication
 
-Join the `#finality-providers` channel in the `- tech-zone -` section of our 
-[Discord server](https://discord.com/invite/babylonglobal) for all communications.
-Testnet announcements will also be made there. 
-
-## CosmWasm Governance Proposals
-
-The Babylon Genesis chain will initially use permissioned CosmWasm. After public 
-launch on 10 April 2025, dApp developers are expected to submit governance proposals 
-for either (a) deploying CosmWasm smart contracts or (b) whitelisting addresses to 
-deploy such contracts. These proposals can be expedited (24-hour voting) or standard 
-(72-hour voting). **It is important that all validators with voting power actively 
-monitor on-chain proposals, review them (**[Governance guidelines](https://docs.babylonlabs.io/guides/governance/))**
-, and participate in governance.**
-
-## Version Information
-
-- **Babylon Genesis node**: Version [v1.0.1](https://github.com/babylonlabs-io/babylon/releases/tag/v1.0.1)([Releases page](https://github.com/babylonlabs-io/babylon/releases))
-
-## Faucets 
-
-There are two ways to get tBABY for Phase 2 Testnet:
-
-1. [Babylon Labs Discord Faucet](https://discord.com/channels/1266159481218457600/1266159481218457600)
-2. [Xangle Faucet](https://babylon-explorer.xangle.io/testnet/faucet) (0.01 tBABY each request)
-
-## Documentation
-
-- [Node Setup guide](https://github.com/babylonlabs-io/networks/tree/main/bbn-1/babylon-node)
-- [Validator Setup Guide](https://github.com/babylonlabs-io/networks/blob/main/bbn-1/babylon-validators/README.md)
-- [Governance guidelines](https://docs.babylonlabs.io/guides/governance/)
+Join the `#finality-providers`

docs/operators/babylon_validators/babylon_validators.mdx

@@ -89,9 +89,7 @@ system will conduct the following actions:
 
 To monitor pending staking transactions that will be processed at epoch end:
 
-- Use [Babylon Genesis Explorers](/developers/babylon_genesis_chain/#chain-explorer) that support epochised staking, or
-
-- Use [Babylon Node](/operators/babylon_node/installation_guide/) or [RPC Endpoints](/developers/babylon_genesis_chain/#node-information) to query the `LastEpochMsgs` endpoint in the
+- Use [Babylon Node](/operators/babylon_node/installation_guide/) or RPC Endpoints to query the `LastEpochMsgs` endpoint in the
   `x/epoching` module.
 
 - Check with compatible wallet interfaces.

docs/stakers/baby_stakers/staking_mechanism.mdx

@@ -757,7 +757,6 @@ <h3>MsgSelectiveSlashingEvidence</h3>
 </code></pre>
 <p>Upon <code>MsgSelectiveSlashingEvidence</code>, a Babylon node will execute as follows:</p>
 <ol>
-<li>Find the BTC delegation with the given staking transaction hash.</li>
 <li>Ensure the BTC delegation is active or unbonding.</li>
 <li>Ensure the given secret key corresponds to the finality provider's public
 key.</li>

static/remote-docs/guides/architecture/babylon_genesis_modules/btc_staking.html

@@ -55,7 +55,7 @@ <h1>Finality Provider</h1>
 <p><img src="./docs/static/finality-provider-arch.png" alt="Finality Provider Architecture Diagram"></p>
 <h2>Finality Provider for Consumer Networks Specification</h2>
 <p>For detailed technical specifications and requirements of the finality provider
-program for Consumer networks, please see <a href="SPEC-CONSUMER.md">SPEC-CONSUMER.md</a>.
+program for Consumer networks, please see <a href="./docs/SPEC-CONSUMER.md">./docs/SPEC-CONSUMER.md</a>.
 The spec document outlines the Consumer's interfaces, message handlers and
 queries.
 It also provides guidance for integrators.</p>