docs: fix .md links

docs/gtm-interchain.md

@@ -72,4 +72,4 @@ Further, we will need technical support that goes beyond the different phase rol
 
 The go-to-market team should be tracking the extent to which IBC is succeeding or failing in terms of key metrics. This will require continuous experimentation and coordination between entities. An example of a metric that best represents IBC go to market would be # of distinct IBC connections that transport x amount of value. To get to these metrics we need the developer resources and proven business models that encourage developers to use this technology.
 
-The Cosmos-SDK exposes some [existing metrics for IBC](https://docs.cosmos.network/main/core/telemetry.html#supported-metrics).
+The Cosmos-SDK exposes some [existing metrics for IBC](https://docs.cosmos.network/v0.45/core/telemetry.html#supported-metrics).

docs/guidelines/code-guidelines.md

@@ -61,7 +61,7 @@ Try to avoid extensive methods and always test your code. All PRs should have at
 - [Contributing](#contributing)
   - [Maintainability](#maintainability)
   - [Run tests](#run-tests)
-- [Guidelines](#guidelines)
+  - [Guidelines](#guidelines)
   - [Project organization](#project-organization)
   - [How to test this project locally](#how-to-test-this-project-locally)
     - [Unit Tests](#unit-tests)
@@ -110,7 +110,6 @@ Try to avoid extensive methods and always test your code. All PRs should have at
       - [Use Subtests](#use-subtests)
     - [Avoid writing directly in the stdout](#avoid-writing-directly-in-the-stdout)
     - [Avoid panic](#avoid-panic)
-  - [Security](#security)
 
 ## Project organization
 

docs/hub-overview/overview.md

@@ -62,6 +62,7 @@ These block explorers allow you to search, view and analyze Cosmos Hub data&mdas
 * [Ping.Pub](https://ping.pub/cosmos)
 * [BronBro](https://monitor.bronbro.io/d/cosmos-stats/cosmos)
 * [Numia](https://www.datalenses.zone/chain/cosmos)
+<!-- markdown-link-check-disable-next-line -->
 * [SmartStake](https://cosmos.smartstake.io/stats)
 
 ## Cosmos Hub CLI

docs/hub-tutorials/gaiad.md

@@ -41,7 +41,7 @@ gaiad config chain-id cosmoshub-2
 
 The keyring holds the private/public keypairs used to interact with a node. For instance, a validator key needs to be set up before running the blockchain node, so that blocks can be correctly signed. The private key can be stored in different locations, called "backends", such as a file or the operating system's own key storage.
 
-Headless environments are recommended to use either the `file` or `pass` backends. More information is available at the [SDK documentation page](https://docs.cosmos.network/main/run-node/keyring.html).
+Headless environments are recommended to use either the `file` or `pass` backends. More information is available at the [SDK documentation page](https://docs.cosmos.network/v0.45/run-node/keyring.html).
 
 #### Key Types
 

docs/modules/globalfee.md

@@ -297,4 +297,4 @@ bypass-min-fee-msg-types = [\
 
 ## References
 
-- [Gas and Fees in Cosmos SDK](https://docs.cosmos.network/main/basics/gas-fees.html)
+- [Gas and Fees in Cosmos SDK](https://docs.cosmos.network/v0.45/basics/gas-fees.html)

mlc_config.json

@@ -6,5 +6,5 @@
     "retryOn429": true,
     "retryCount": 5,
     "fallbackRetryDelay": "30s",
-    "aliveStatusCodes": [0, 200, 206, 403]
+    "aliveStatusCodes": [0, 200, 206, 403, 429]
   }