Merge branch 'main' into fix/broken-link-player-assets

Author: 0xJuanI

pages/chain/builder/apis.mdx

@@ -13,16 +13,16 @@ To learn more about the Beam API, please see the dedicated [Beam SDK docs](/sdk)
 
 ## Beam Subnet-EVM API
 
-The Subnet-EVM APIs mirror the [Coreth](https://github.com/ava-labs/coreth) APIs with one exception - Avalanche Specific APIs, identifiable by the '`avax.`' prefix. In addition, Subnet-EVM supports standard Ethereum APIs, increasing its applicability. For in-depth information about Coreth APIs, please refer [here](https://docs.avax.network/apis/avalanchego/apis/c-chain).
+The Subnet-EVM APIs mirror the [Coreth](https://github.com/ava-labs/coreth) APIs with one exception - Avalanche Specific APIs, identifiable by the '`avax.`' prefix. In addition, Subnet-EVM supports standard Ethereum APIs, increasing its applicability. For in-depth information about Coreth APIs, please refer [here](https://docs.avax.network/api-reference/c-chain/api).
 
 Moreover, Subnet-EVM introduces unique APIs not present in Coreth:
 
-- `eth_feeConfig`: Subnet-EVM comes with an API request for getting fee config at a specific block. You can use this API to check your activated fee config. ([Details](https://docs.avax.network/apis/avalanchego/apis/subnet-evm#eth_feeconfig))
+- `eth_feeConfig`: Subnet-EVM comes with an API request for getting fee config at a specific block. You can use this API to check your activated fee config. ([Details](https://docs.avax.network/api-reference/subnet-evm-api#eth_feeconfig))
 
-- `eth_getChainConfig`: eth_getChainConfig returns the Chain Config of the blockchain. This API is enabled by default with internal-blockchain namespace. ([Details](https://docs.avax.network/apis/avalanchego/apis/subnet-evm#eth_getchainconfig))
+- `eth_getChainConfig`: eth_getChainConfig returns the Chain Config of the blockchain. This API is enabled by default with internal-blockchain namespace. ([Details](https://docs.avax.network/api-reference/subnet-evm-api#eth_getchainconfig))
 
 
-- `eth_getActivePrecompilesAt`: eth_getActivePrecompilesAt returns activated precompiles at a specific timestamp. If no timestamp is provided it returns the latest block timestamp. This API is enabled by default with internal-blockchain namespace. ([Details](https://docs.avax.network/apis/avalanchego/apis/subnet-evm#eth_getactiveprecompilesat))
+- `eth_getActivePrecompilesAt`: eth_getActivePrecompilesAt returns activated precompiles at a specific timestamp. If no timestamp is provided it returns the latest block timestamp. This API is enabled by default with internal-blockchain namespace. ([Details](https://docs.avax.network/api-reference/subnet-evm-api#eth_getactiveprecompilesat))
 
 
 ### JSON-RPC Endpoint
@@ -58,7 +58,7 @@ Beam's API overview. Find a variety of APIs each designed for a different purpos
 | Title                                              | Description                                                                                                                                         |
 | :------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [**Beam API**](/sdk/full-api-reference)      |   Beam specific API       |  
-| [**AvalancheGo**](https://docs.avax.network/apis/avalanchego)      |     AvalancheGo APIs, Postman collection, public servers, and release notes      |  
-| [**AvalancheJS**](https://docs.avax.network/apis/avalanchejs)      | AvalancheJS APIs |
+| [**AvalancheGo**](https://docs.avax.network/api-reference/admin-api)      |     AvalancheGo APIs, Postman collection, public servers, and release notes      |  
+| [**AvalancheJS**](https://docs.avax.network/tooling/avalanche-js)      | AvalancheJS APIs |
 | [**Avalanche Metrics API**](https://metrics.avax.network/)       | Avalanche Metrics API              |
-| [**Glacier API**](https://glacier-api.avax.network/api#/)                 | High-performance API for easy access to indexed blockchain data              |
+| [**Glacier API**](https://glacier-api.avax.network/api#/)                 | High-performance API for easy access to indexed blockchain data              |

pages/chain/builder/omnichain-tokens.mdx

@@ -257,8 +257,7 @@ npx hardhat --network avalanche etherscan-verify
 
 ## Supported networks
 
-The LayerZero protocol is active on a wide selection of [test](https://docs.layerzero.network/v1/developers/technical-reference/testnet/testnet-addresses)- and
-[mainnets](https://docs.layerzero.network/v1/developers/technical-reference/mainnet/mainnet-addresses), though not all chains are interconnected by default.
+The LayerZero protocol is active on a wide selection of [test- and mainnets](https://docs.layerzero.network/v2/developers/evm/technical-reference/deployed-contracts), though not all chains are interconnected by default
 
 Currently, both Beam test- and mainnet connect to
 

pages/chain/nodes/beam-node.mdx

@@ -6,7 +6,7 @@ import { Callout, Steps } from "nextra/components";
 
 # Beam Node
 
-To run your own Beam Node, no matter if you plan to run a validator node or a non-validating node, you have to install AvalancheGo. The easiest method is using the installer which you can find [here](https://docs.avax.network/nodes/build/set-up-node-with-installer). Please note that this guide is compatible with AvalancheGo version 1.11.5.
+To run your own Beam Node, no matter if you plan to run a validator node or a non-validating node, you have to install AvalancheGo. The easiest method is using the installer which you can find [here](https://docs.avax.network/tooling/avalanche-go-installer). Please note that this guide is compatible with AvalancheGo version 1.11.5.
 
 Once you have a running AvalancheGo installation, you need to add the Beam Subnet-EVM to track the Beam Subnet in your node.
 
@@ -128,7 +128,7 @@ curl -X POST --data '{
 }' -H 'content-type:application/json;' 127.0.0.1:9650/ext/bc/P
 ```
 
-For an explanation of the response, check the [API docs](https://docs.avax.network/apis/avalanchego/apis/p-chain#platformgetblockchainstatus).
+For an explanation of the response, check the [API docs](https://docs.avax.network/api-reference/p-chain/api#platformgetblockchainstatus).
 
 If you want to understand your Subnet better, take a look at the blockchain log. Normally, you can find this log in `~/.avalanchego/logs/ChainID.log{:bash}`. Just replace "`ChainID`" with the real ID of your blockchain in your Subnet.