resolving links

Author: samclusker

docs/network/0-overview.mdx

@@ -353,7 +353,7 @@ Discover suitable options for your needs on the [Flare Wallets](https://flare.ne
 
 ## Consensus mechanism
 
-- **Consensus Protocol:** Snowman++ (from [Avalanche](https://build.avax.network/docs/quick-start)) provides a high-throughput, totally ordered consensus with fast finality. Learn more on the [Consensus](/network/consensus) page.
+- **Consensus Protocol:** Snowman++ (from [Avalanche](https://build.avax.network/docs/primary-network)) provides a high-throughput, totally ordered consensus with fast finality. Learn more on the [Consensus](/network/consensus) page.
 
 - **Sybil resistance mechanism:** Proof-of-Stake (PoS)
 

docs/network/4-consensus.mdx

@@ -11,7 +11,7 @@ import CodeBlock from "@theme/CodeBlock";
 import ThemedImage from "@theme/ThemedImage";
 import useBaseUrl from "@docusaurus/useBaseUrl";
 
-The consensus protocol running on all Flare networks is Snowman++, introduced by [Avalanche](https://build.avax.network/docs/quick-start).
+The consensus protocol running on all Flare networks is Snowman++, introduced by [Avalanche](https://build.avax.network/docs/primary-network).
 This runs on both the P- and C-chains.
 
 <div style={{ textAlign: "center", margin: "30px 0" }}>

docs/run-node/2-from-source.mdx

@@ -202,7 +202,7 @@ These are some of the most relevant CLI parameters you can use. Read more about
 
 #### Sample JSON configuration:
 
-Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
+Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
 Note that the default values are overridden only if specified in the given config file.
 Only provide values which differ from the defaults to avoid issues with future updates.
 

docs/run-node/3-using-docker.mdx

@@ -105,7 +105,7 @@ Mounting these allows you to manage them directly without entering the container
    ```
 
 2. **Create configuration file:** Create a `config.json` file. This example provides a standard configuration for a public RPC node.
-   Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
+   Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
    Note that the default values are overridden only if specified in the given config file.
    Only provide values which differ from the defaults to avoid issues with future updates.
 

docs/run-node/4-register-validator.mdx

@@ -67,7 +67,7 @@ Failure to implement these measures significantly increases the risk to your nod
 
 As described in [Secure the node](#secure-the-node), a validator node should have minimal APIs enabled.
 Below is a sample `config.json` demonstrating a secure configuration with limited `eth-apis` and disabled admin APIs:
-Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/c-chain).
+Most of the C-Chain configuration options can be found in the [Avalanche C-Chain Configuration docs](https://build.avax.network/docs/nodes/chain-configs/avalanche-l1s/subnet-evm).
 Note that the default values are overridden only if specified in the given config file.
 Only provide values which differ from the defaults to avoid issues with future updates.