fixed borken links

Author: web3jenks

docs/operators/babylon_node/babylon_cli/create_bls_key.mdx

@@ -20,7 +20,7 @@ babylond create-bls-key [flags]
 
 Before using this command, ensure you have:
 
-- Initialized your Babylon node with [`babylond init`](./init.md) or [`babylond testnet`](./testnet.md)
+- Initialized your Babylon node with [`babylond init`](./init.mdx) or [`babylond testnet`](./testnet.mdx)
 - Confirmed that `priv_validator_key.json` exists in your node's configuration directory
 - Planned your BLS key password security strategy
 
@@ -287,16 +287,16 @@ systemctl start babylond
 ## Related Commands
 
 ### Validator Setup
-- [`babylond init`](./init.md) - Initialize node (required prerequisite)
-- [`babylond testnet`](./testnet.md) - Initialize testnet configuration
-- [`babylond gentx`](./gentx.md) - Generate validator genesis transaction
-- [`babylond add-genesis-account`](./add-genesis-account.md) - Add validator account to genesis
+- [`babylond init`](./init.mdx) - Initialize node (required prerequisite)
+- [`babylond testnet`](./testnet.mdx) - Initialize testnet configuration
+- [`babylond gentx`](./gen_tx.mdx) - Generate validator genesis transaction
+- [`babylond add-genesis-account`](./add_genesis_account.mdx) - Add validator account to genesis
 
 ### Key Management
-- [`babylond keys`](./keys.md) - Manage keyring keys
-- [`babylond comet show-validator`](./comet.md#show-validator) - Show validator public key
+- [`babylond keys`](./keys.mdx) - Manage keyring keys
+- [`babylond comet show-validator`](./comet.mdx#show-validator) - Show validator public key
 
 ### Node Operations
-- [`babylond start`](./start.md) - Start the validator node
-- [`babylond status`](./status.md) - Check validator status
+- [`babylond start`](./start.mdx) - Start the validator node
+- [`babylond status`](./status.mdx) - Check validator status
 

docs/operators/babylon_node/babylon_cli/gen_tx.mdx

@@ -20,10 +20,10 @@ babylond gentx [key_name] [amount] [flags]
 
 Before using this command, ensure you have:
 
-- Initialized your Babylon node with [`babylond init`](./init.md)
-- Created validator keys with [`babylond keys add`](./keys.md)
-- Created BLS keys with [`babylond create-bls-key`](./create-bls-key.md)
-- Added your validator account to genesis with [`babylond add-genesis-account`](./add-genesis-account.md)
+- Initialized your Babylon node with [`babylond init`](./init.mdx)
+- Created validator keys with [`babylond keys add`](./keys.mdx)
+- Created BLS keys with [`babylond create-bls-key`](./create_bls_key.mdx)
+- Added your validator account to genesis with [`babylond add-genesis-account`](./add_genesis_account.mdx)
 
 ## Arguments
 

docs/operators/babylon_node/babylon_cli/generate_bls_pop.mdx

@@ -20,8 +20,8 @@ babylond generate-bls-pop [flags]
 
 Before using this command, ensure you have:
 
-- Initialized your Babylon node with [`babylond init`](./init.md)
-- Created BLS keys with [`babylond create-bls-key`](./create-bls-key.md)
+- Initialized your Babylon node with [`babylond init`](./init.mdx)
+- Created BLS keys with [`babylond create-bls-key`](./create_bls_key.mdx)
 - Confirmed that both key files exist:
   - `priv_validator_key.json` (contains Ed25519 keys)
   - `bls_key.json` or BLS keys embedded in `priv_validator_key.json`

docs/operators/babylon_node/babylon_cli/keys.mdx

@@ -675,15 +675,15 @@ echo "✅ Validator keys created and added to genesis"
 ## Related Commands
 
 ### Validator Operations
-- [`babylond gentx`](./gentx.md) - Generate genesis transaction using keys
-- [`babylond tx checkpointing create-validator`](./tx-checkpointing.md) - Create validator using keys
-- [`babylond generate-bls-pop`](./generate-bls-pop.md) - Generate proof-of-possession with keys
+- [`babylond gentx`](./gen_tx.mdx) - Generate genesis transaction using keys
+- [`babylond tx checkpointing create-validator`](./tx.mdx) - Create validator using keys
+- [`babylond generate-bls-pop`](./generate_bls_pop.mdx) - Generate proof-of-possession with keys
 
 ### Node Setup
-- [`babylond init`](./init.md) - Initialize node (creates validator consensus keys)
-- [`babylond add-genesis-account`](./add-genesis-account.md) - Add key addresses to genesis
+- [`babylond init`](./init.mdx) - Initialize node (creates validator consensus keys)
+- [`babylond add-genesis-account`](./add_genesis_account.mdx) - Add key addresses to genesis
 
 ### Address Operations
-- [`babylond debug addr`](./debug.md#addr) - Convert address formats
-- [`babylond debug pubkey`](./debug.md#pubkey) - Debug public key formats
+- [`babylond debug addr`](./debug.mdx#addr) - Convert address formats
+- [`babylond debug pubkey`](./debug.mdx#pubkey) - Debug public key formats
 

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

@@ -314,8 +314,8 @@ <h3>BTC delegations</h3>
     ProofOfPossessionBTC pop = 3;
     // fp_btc_pk_list is the list of BIP-340 PKs of the finality providers that
     // this BTC delegation delegates to
-    // If there is more than 1 PKs, then this means the delegation is restaked
-    // to multiple finality providers
+    // If there is more than 1 PKs, then this means the delegation is
+    // multi-staked to multiple finality providers
     repeated bytes fp_btc_pk_list = 4 [ (gogoproto.customtype) = "github.com/babylonlabs-io/babylon/types.BIP340PubKey" ];
     // staking_time is the number of blocks for which the delegation is locked on BTC chain
     uint32 staking_time = 5;

static/remote-docs/guides/architecture/consumer_zone_programs/babylon_contracts.html

@@ -23,9 +23,24 @@
 <body>
   <article>
 
-    <h1>Babylon-contract</h1>
-<p>This repo contains the Wasm smart contract for Babylon integrations.
-It will be deployed on a Cosmos zone that integrates Babylon, and will maintain BTC timestamps of headers in this Cosmos zone.</p>
+    <h1>Cosmos BSN Contracts</h1>
+<p>This repository contains the CosmWasm smart contracts that enable
+the integration of Cosmos BSNs with the Babylon BTC Staking protocol.</p>
+<h2>Architecture</h2>
+<p>The contracts are written in Rust, and use the CosmWasm framework to interact
+with the BSN's Cosmos application layer.
+There's a thin layer which adds a <a href="https://github.com/babylonlabs-io/babylon-sdk/tree/main/x/babylon"><code>babylon</code> module</a>
+, which provides the necessary functionality to interact with the contracts
+through privileged calls (<code>sudo</code> messages) and custom messages.
+This thin layer is naturally written in Go, and uses the Cosmos SDK.</p>
+<p>An integrator can import the <code>babylon</code> module into their Cosmos SDK-based chain,
+and use the provided functionality to interact with the Cosmos BSN contracts,
+following the demo app's guidelines and layout, which is provided in
+<a href="https://github.com/babylonlabs-io/babylon-sdk"><code>babylon-sdk</code></a> as well.</p>
+<p>The entire solution is designed to be modular and extensible, for ease of
+integration and future upgrades.</p>
+<p>A broad architecture diagram, along with the contracts' main interfaces, can be
+found in the <a href="docs/ARCHITECTURE.md"><code>docs/ARCHITECTURE.md</code></a> documentation.</p>
 <h2>Development</h2>
 <h3>Prerequisites</h3>
 <p>Make sure you have <code>cargo-run-script</code> installed and docker running.</p>