diff --git a/src/content/any-api/api-reference.mdx b/src/content/any-api/api-reference.mdx
index c4832f9e5c5..733d554e2c6 100644
--- a/src/content/any-api/api-reference.mdx
+++ b/src/content/any-api/api-reference.mdx
@@ -11,8 +11,8 @@ import AnyApiCallout from "@features/any-api/common/AnyApiCallout.astro"
 <Aside type="note" title="API reference for ChainlinkClient">
 
 `ChainlinkClient` [contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/ChainlinkClient.sol)
-can communicate with legacy `Oracle` [contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol)
-or `Operator` [contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+can communicate with legacy `Oracle` [contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol)
+or `Operator` [contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 </Aside>
 
@@ -20,23 +20,23 @@ or `Operator` [contracts](https://github.com/smartcontractkit/chainlink/blob/dev
 
 ### Methods
 
-| Name                                                          | Description                                                                                                                                                                                                                        |
-| :------------------------------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [setChainlinkOracle](#setchainlinkoracle)                     | Sets the stored address for the oracle contract                                                                                                                                                                                    |
-| [setChainlinkToken](#setchainlinktoken)                       | Sets the stored address for the LINK token                                                                                                                                                                                         |
-| [buildChainlinkRequest](#buildchainlinkrequest)               | Instantiates a Request object with the required parameters                                                                                                                                                                         |
-| [buildOperatorRequest](#buildoperatorrequest)                 | Instantiates a Request object with the required parameters. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol)                       |
-| [sendChainlinkRequest](#sendchainlinkrequest)                 | Sends the request payload to the stored address stored as chainlinkOracleAddress                                                                                                                                                   |
-| [sendChainlinkRequestTo](#sendchainlinkrequestto)             | Sends a request to the oracle address specified                                                                                                                                                                                    |
-| [sendOperatorRequest](#sendoperatorrequest)                   | Sends the request payload to the stored address stored as chainlinkOracleAddress. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) |
-| [sendOperatorRequestTo](#sendoperatorrequestto)               | Sends a request to the oracle address specified. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol)                                  |
-| [validateChainlinkCallback](#validatechainlinkcallback)       | Secures the fulfillment callback to make sure it is only called by permissioned senders                                                                                                                                            |
-| [addChainlinkExternalRequest](#addchainlinkexternalrequest)   | Allows a Chainlinked contract to track unfulfilled requests that it hasn't created itself                                                                                                                                          |
-| [cancelChainlinkRequest](#cancelchainlinkrequest)             | Cancels Chainlink requests attempting to contact an unresponsive node                                                                                                                                                              |
-| [useChainlinkWithENS](#usechainlinkwithens)                   | Looks up the addresses of the LINK token and Oracle contract through ENS                                                                                                                                                           |
-| [updateChainlinkOracleWithENS](#updatechainlinkoraclewithens) | Updates the stored oracle address with the latest address resolved through ENS                                                                                                                                                     |
-| [chainlinkTokenAddress](#chainlinktokenaddress)               | Returns the stored address of the LINK token                                                                                                                                                                                       |
-| [chainlinkOracleAddress](#chainlinkoracleaddress)             | Returns the stored address of the oracle contract                                                                                                                                                                                  |
+| Name                                                          | Description                                                                                                                                                                                                                       |
+| :------------------------------------------------------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| [setChainlinkOracle](#setchainlinkoracle)                     | Sets the stored address for the oracle contract                                                                                                                                                                                   |
+| [setChainlinkToken](#setchainlinktoken)                       | Sets the stored address for the LINK token                                                                                                                                                                                        |
+| [buildChainlinkRequest](#buildchainlinkrequest)               | Instantiates a Request object with the required parameters                                                                                                                                                                        |
+| [buildOperatorRequest](#buildoperatorrequest)                 | Instantiates a Request object with the required parameters. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol)                       |
+| [sendChainlinkRequest](#sendchainlinkrequest)                 | Sends the request payload to the stored address stored as chainlinkOracleAddress                                                                                                                                                  |
+| [sendChainlinkRequestTo](#sendchainlinkrequestto)             | Sends a request to the oracle address specified                                                                                                                                                                                   |
+| [sendOperatorRequest](#sendoperatorrequest)                   | Sends the request payload to the stored address stored as chainlinkOracleAddress. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) |
+| [sendOperatorRequestTo](#sendoperatorrequestto)               | Sends a request to the oracle address specified. **Note** the oracle must be an `Operator` [contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol)                                  |
+| [validateChainlinkCallback](#validatechainlinkcallback)       | Secures the fulfillment callback to make sure it is only called by permissioned senders                                                                                                                                           |
+| [addChainlinkExternalRequest](#addchainlinkexternalrequest)   | Allows a Chainlinked contract to track unfulfilled requests that it hasn't created itself                                                                                                                                         |
+| [cancelChainlinkRequest](#cancelchainlinkrequest)             | Cancels Chainlink requests attempting to contact an unresponsive node                                                                                                                                                             |
+| [useChainlinkWithENS](#usechainlinkwithens)                   | Looks up the addresses of the LINK token and Oracle contract through ENS                                                                                                                                                          |
+| [updateChainlinkOracleWithENS](#updatechainlinkoraclewithens) | Updates the stored oracle address with the latest address resolved through ENS                                                                                                                                                    |
+| [chainlinkTokenAddress](#chainlinktokenaddress)               | Returns the stored address of the LINK token                                                                                                                                                                                      |
+| [chainlinkOracleAddress](#chainlinkoracleaddress)             | Returns the stored address of the oracle contract                                                                                                                                                                                 |
 
 ### Events
 
@@ -114,7 +114,7 @@ constructor(address _link)
 ### buildChainlinkRequest
 
 Use `buildOperatorRequest` [function](#buildoperatorrequest) if the oracle is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -151,7 +151,7 @@ is that `buildOperatorRequest` does not allow setting up the address of the call
 is set to the address of the calling contract.
 
 It is recommended to use `buildOperatorRequest` but make sure the oracle you are contacting is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -181,7 +181,7 @@ function requestPrice()
 ### sendChainlinkRequest
 
 Use `sendOperatorRequest` [function](#sendoperatorrequest) if the oracle is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -213,7 +213,7 @@ function requestPrice()
 ### sendChainlinkRequestTo
 
 Use `sendOperatorRequestTo` [function](#sendoperatorrequestto) if the oracle is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -245,7 +245,7 @@ function requestPriceFrom(address _oracle)
 
 This function is similar to `sendChainlinkRequest`[function](#sendchainlinkrequest).
 It is recommended to use `sendOperatorRequest` but make sure the oracle you are contacting is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -278,7 +278,7 @@ function requestPrice()
 
 This function is similar to `sendChainlinkRequestTo`[function](#sendchainlinkrequestto).
 It is recommended to use `sendOperatorRequestTo`, but make sure the oracle you are contacting is an `Operator`
-[contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+[contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 {/* prettier-ignore */}
 ```solidity
@@ -421,7 +421,7 @@ constructor(){
 
 <Aside type="caution" title="Updating oracle addresses">
 
-If an oracle provider supports listing their oracle on ENS, that provides the added security of being able to update any issues that may arise. The tradeoff here is that by using their ENS record, you are allowing whoever controls that record and the corresponding code it points to. If your contract does this, you must either audit the updated code and make sure it matches [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.6/Oracle.sol) or trust whoever can update the records.
+If an oracle provider supports listing their oracle on ENS, that provides the added security of being able to update any issues that may arise. The tradeoff here is that by using their ENS record, you are allowing whoever controls that record and the corresponding code it points to. If your contract does this, you must either audit the updated code and make sure it matches [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.6/Oracle.sol) or trust whoever can update the records.
 
 </Aside>
 
@@ -445,7 +445,7 @@ function updateOracleAddressToLatest() public {
 
 <Aside type="caution" title="Updating oracle addresses">
 
-If an oracle provider supports listing their oracle on ENS, that provides the added security of being able to update any issues that may arise. The tradeoff here is that by using their ENS record, you are allowing whoever controls that record and the corresponding code it points to. If your contract does this, you must either audit the updated code and make sure it matches [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol) or trust whoever can update the records.
+If an oracle provider supports listing their oracle on ENS, that provides the added security of being able to update any issues that may arise. The tradeoff here is that by using their ENS record, you are allowing whoever controls that record and the corresponding code it points to. If your contract does this, you must either audit the updated code and make sure it matches [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol) or trust whoever can update the records.
 
 </Aside>
 
diff --git a/src/content/any-api/testnet-oracles.mdx b/src/content/any-api/testnet-oracles.mdx
index f3461ac0157..f4753c23391 100644
--- a/src/content/any-api/testnet-oracles.mdx
+++ b/src/content/any-api/testnet-oracles.mdx
@@ -21,7 +21,7 @@ To retrieve the LINK token address or get faucet details for your testnet of cho
 
 ## Operator Contracts
 
-Testnet [Operator contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) are deployed and maintained on the following networks:
+Testnet [Operator contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) are deployed and maintained on the following networks:
 
 | Testnet          | Oracle Address                                                                                                                    |
 | ---------------- | --------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/src/content/architecture-overview/architecture-decentralized-model.mdx b/src/content/architecture-overview/architecture-decentralized-model.mdx
index 2a4c9d6735d..943323e9195 100644
--- a/src/content/architecture-overview/architecture-decentralized-model.mdx
+++ b/src/content/architecture-overview/architecture-decentralized-model.mdx
@@ -62,13 +62,13 @@ Offchain applications can also consume data feeds. See the Javascript and Python
 
 Proxy contracts are onchain proxies that point to the aggregator for a particular data feed. Using proxies enables the underlying aggregator to be upgraded without any service interruption to consuming contracts.
 
-Proxy contracts can vary from one data feed to another, but the [`AggregatorProxy.sol` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/dev/AggregatorProxy.sol) on Github is a common example.
+Proxy contracts can vary from one data feed to another, but the [`AggregatorProxy.sol` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/dev/AggregatorProxy.sol) on Github is a common example.
 
 ### Aggregator
 
 An aggregator is the contract that receives periodic data updates from the oracle network. Aggregators store aggregated data onchain so that consumers can retrieve it and act upon it within the same transaction.
 
-You can access this data using the Data Feed address and the [`AggregatorV3Interface` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.6/interfaces/AggregatorV3Interface.sol).
+You can access this data using the Data Feed address and the [`AggregatorV3Interface` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.6/interfaces/AggregatorV3Interface.sol).
 
 Aggregators receive updates from the oracle network only when the **Deviation Threshold** or **Heartbeat Threshold** triggers an update during an aggregation round. The first condition that is met triggers an update to the data.
 
diff --git a/src/content/ccip/supported-networks/index.mdx b/src/content/ccip/supported-networks/index.mdx
index 3f2c918ff63..f71e9fd1dc1 100644
--- a/src/content/ccip/supported-networks/index.mdx
+++ b/src/content/ccip/supported-networks/index.mdx
@@ -2,6 +2,7 @@
 section: ccip
 date: Last Modified
 title: "CCIP Supported Networks"
+isIndex: true
 ---
 
 Click on the following links to find the latest configuration for Chainlink CCIP:
diff --git a/src/content/chainlink-automation/guides/log-trigger.mdx b/src/content/chainlink-automation/guides/log-trigger.mdx
index 02bb7aa8878..7d42c9aa1dc 100644
--- a/src/content/chainlink-automation/guides/log-trigger.mdx
+++ b/src/content/chainlink-automation/guides/log-trigger.mdx
@@ -78,7 +78,7 @@ Select **Log Trigger**.
   Your upkeeps will be protected against logs that are emitted during a reorg.
 </Aside>
 
-1. **Provide the address of your [Automation-compatible contract](/chainlink-automation/guides/compatible-contracts)** that you want to automate. In this case, we will paste the address of `CountWithLog.sol`. This contract must follow the format of the [ILogAutomation interface](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/interfaces/ILogAutomation.sol) to ensure Automation nodes can interact with your contract as expected.
+1. **Provide the address of your [Automation-compatible contract](/chainlink-automation/guides/compatible-contracts)** that you want to automate. In this case, we will paste the address of `CountWithLog.sol`. This contract must follow the format of the [ILogAutomation interface](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/interfaces/ILogAutomation.sol) to ensure Automation nodes can interact with your contract as expected.
 
    <ClickToZoom src="/images/automation/log_trig_1_upkeep_address.png" />
 
diff --git a/src/content/chainlink-automation/reference/automation-contracts.mdx b/src/content/chainlink-automation/reference/automation-contracts.mdx
index 48a81e0b50a..b2fd12ef411 100644
--- a/src/content/chainlink-automation/reference/automation-contracts.mdx
+++ b/src/content/chainlink-automation/reference/automation-contracts.mdx
@@ -9,25 +9,25 @@ whatsnext: { "Automation Architecture": "/chainlink-automation/concepts/automati
 
 Automation Nodes use the following contracts. You can find them in the [Chainlink repository](https://github.com/smartcontractkit/chainlink/tree/develop/contracts/src/v0.8/automation). For details about how to use them, visit the [Creating Compatible Contracts](/chainlink-automation/guides/compatible-contracts) guide. To understand the logic behind these contracts, visit the [Architecture](/chainlink-automation/concepts/automation-architecture) page.
 
-- [`AutomationCompatible.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/AutomationCompatible.sol): Imports the following contracts:
-  - [`AutomationBase.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/AutomationBase.sol): Enables the use of the `cannotExecute` modifier. Import this contract if you need for this modifier. See the [`checkUpkeep` function](/chainlink-automation/reference/automation-interfaces#checkupkeep-function) for details.
+- [`AutomationCompatible.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/AutomationCompatible.sol): Imports the following contracts:
+  - [`AutomationBase.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/AutomationBase.sol): Enables the use of the `cannotExecute` modifier. Import this contract if you need for this modifier. See the [`checkUpkeep` function](/chainlink-automation/reference/automation-interfaces#checkupkeep-function) for details.
   - [`AutomationCompatibleInterface.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/interfaces/AutomationCompatibleInterface.sol): The interface to be implemented in order to make your contract compatible. Import this contract for type safety.
 
 ## AutomationRegistry.sol
 
-[`AutomationRegistry2_1.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/v2_1/KeeperRegistry2_1.sol): The registry contract that tracks all registered Upkeeps and the Automation Nodes that can perform them. _Note_: As Chainlink Automation continues adding new functionalities, a new **Automation Registry** is deployed and the contract address may change.
+[`AutomationRegistry2_1.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/v2_1/KeeperRegistry2_1.sol): The registry contract that tracks all registered Upkeeps and the Automation Nodes that can perform them. _Note_: As Chainlink Automation continues adding new functionalities, a new **Automation Registry** is deployed and the contract address may change.
 
 ## AutomationRegistrar.sol
 
-[`AutomationRegistrar2_1.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/v2_1/AutomationRegistrar2_1.sol): The Registrar contract governs the registration of new Upkeeps on the associated `AutomationRegistry` contract. Users who want to register Upkeeps by directly calling the deployed contract have to call the Transfer-and-Call function on the respective ERC-677 LINK contract configured on the Registrar and ensure they pass the correct encoded function call and inputs.
+[`AutomationRegistrar2_1.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/v2_1/AutomationRegistrar2_1.sol): The Registrar contract governs the registration of new Upkeeps on the associated `AutomationRegistry` contract. Users who want to register Upkeeps by directly calling the deployed contract have to call the Transfer-and-Call function on the respective ERC-677 LINK contract configured on the Registrar and ensure they pass the correct encoded function call and inputs.
 
 ## UpkeepTranscoder.sol
 
-[`UpkeepTranscode4_0.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/dev/automation/2_1/UpkeepTranscoder4_0.sol) allows the conversion of upkeep data from previous Automation registry versions 1.2, 1.3, and 2.0 to registry 2.1.
+[`UpkeepTranscode4_0.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/v2_1/UpkeepTranscoder4_0.sol) allows the conversion of upkeep data from previous Automation registry versions 1.2, 1.3, and 2.0 to registry 2.1.
 
 ## AutomationForwarder.sol
 
-[`AutomationForwarder.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/v2_1/AutomationForwarder.sol) is a relayer that sits between the registry and the customer's target contract. The purpose of the forwarder is to give customers a consistent address to authorize against that stays consistent between migrations. The Forwarder also exposes the registry address, so that users who want to programatically interact with the registry can do so. The `forward` function in this contract is called by the registry and forwards the call to the target.
+[`AutomationForwarder.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/AutomationForwarder.sol) is a relayer that sits between the registry and the customer's target contract. The purpose of the forwarder is to give customers a consistent address to authorize against that stays consistent between migrations. The Forwarder also exposes the registry address, so that users who want to programatically interact with the registry can do so. The `forward` function in this contract is called by the registry and forwards the call to the target.
 
 ## CronUpkeepFactory.sol
 
diff --git a/src/content/chainlink-automation/reference/automation-interfaces.mdx b/src/content/chainlink-automation/reference/automation-interfaces.mdx
index 88905085804..79c0ed65a65 100644
--- a/src/content/chainlink-automation/reference/automation-interfaces.mdx
+++ b/src/content/chainlink-automation/reference/automation-interfaces.mdx
@@ -26,7 +26,7 @@ Your Automation-compatible contracts may use the following interfaces. You can f
 
 ## AutomationCompatibleInterface
 
-Custom logic upkeeps need to use the [`AutomationCompatibleInterface.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/interfaces/AutomationCompatibleInterface.sol) interface. Click on one of the functions below to understand its parameters and limits.
+Custom logic upkeeps need to use the [`AutomationCompatibleInterface.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/interfaces/AutomationCompatibleInterface.sol) interface. Click on one of the functions below to understand its parameters and limits.
 
 | Function Name   | Description                                                                          |
 | --------------- | ------------------------------------------------------------------------------------ |
diff --git a/src/content/chainlink-functions/getting-started.mdx b/src/content/chainlink-functions/getting-started.mdx
index 7c4c19fc1e8..f016dd41b13 100644
--- a/src/content/chainlink-functions/getting-started.mdx
+++ b/src/content/chainlink-functions/getting-started.mdx
@@ -230,7 +230,7 @@ Chainlink Functions is capable of much more than just retrieving data. Try one o
 
 <CodeSample src="samples/ChainlinkFunctions/GettingStartedFunctionsConsumer.sol" />
 
-- To write a Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/FunctionsClient.sol) and [FunctionsRequest.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/libraries/FunctionsRequest.sol). You can read the API references: [FunctionsClient](/chainlink-functions/api-reference/functions-client) and [FunctionsRequest](/chainlink-functions/api-reference/functions-request).
+- To write a Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/FunctionsClient.sol) and [FunctionsRequest.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/libraries/FunctionsRequest.sol). You can read the API references: [FunctionsClient](/chainlink-functions/api-reference/functions-client) and [FunctionsRequest](/chainlink-functions/api-reference/functions-request).
 
   These contracts are available in an NPM package so that you can import them from within your project.
 
diff --git a/src/content/chainlink-nodes/contracts/forwarder.mdx b/src/content/chainlink-nodes/contracts/forwarder.mdx
index 769ec4bcf8b..0935f4cb096 100644
--- a/src/content/chainlink-nodes/contracts/forwarder.mdx
+++ b/src/content/chainlink-nodes/contracts/forwarder.mdx
@@ -14,7 +14,7 @@ In the EVM world, [externally-owned account](https://ethereum.org/en/developers/
 To solve these challenges, we introduced two major features that will allow node operators to set up different transaction-sending strategies more securely while lowering their infrastructure costs:
 
 - Chainlink nodes support multiple EOAs.
-- [Forwarder](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/AuthorizedForwarder.sol) contracts allow a node operator to manage multiple EOAs and make them look like a single address. If you use a web2 analogy, forwarder contracts act like a reverse proxy server where the user is served by the same address and does not see which server the traffic is coming from. To do so, nodes call the [forward](#forward) function on the forwarder contract.
+- [Forwarder](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/AuthorizedForwarder.sol) contracts allow a node operator to manage multiple EOAs and make them look like a single address. If you use a web2 analogy, forwarder contracts act like a reverse proxy server where the user is served by the same address and does not see which server the traffic is coming from. To do so, nodes call the [forward](#forward) function on the forwarder contract.
 
 Combining multiple EOAs and forwarder contracts allows greater flexibility and security in terms of design:
 
@@ -25,7 +25,7 @@ Combining multiple EOAs and forwarder contracts allows greater flexibility and s
 
 ## API Reference
 
-The forwarder contract inherits [AuthorizedReceiver.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/AuthorizedReceiver.sol) and [ConfirmedOwnerWithProposal.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol). Read the [Receiver](/chainlink-nodes/contracts/receiver) and [Ownership](/chainlink-nodes/contracts/ownership) API references to learn more.
+The forwarder contract inherits [AuthorizedReceiver.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/AuthorizedReceiver.sol) and [ConfirmedOwnerWithProposal.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol). Read the [Receiver](/chainlink-nodes/contracts/receiver) and [Ownership](/chainlink-nodes/contracts/ownership) API references to learn more.
 
 ### Methods
 
diff --git a/src/content/chainlink-nodes/contracts/operator.mdx b/src/content/chainlink-nodes/contracts/operator.mdx
index 9d92605a2c3..5e769ef5088 100644
--- a/src/content/chainlink-nodes/contracts/operator.mdx
+++ b/src/content/chainlink-nodes/contracts/operator.mdx
@@ -8,7 +8,7 @@ import { Aside } from "@components"
 
 Oracles must deploy an onchain contract to handle requests made through the LINK token (Read [Basic Request Model](/architecture-overview/architecture-request-model) to learn more).
 
-When the _Basic Request_ model was introduced, node operators had to deploy [Oracle contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol). However, these come with some limitations, and soon, we introduced [operator contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol).
+When the _Basic Request_ model was introduced, node operators had to deploy [Oracle contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol). However, these come with some limitations, and soon, we introduced [operator contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol).
 
 <Aside type="note">
   <p>Node operators are recommended to use _Operator.sol_ instead of _Oracle.sol_.</p>
@@ -20,13 +20,13 @@ In addition to replacing oracle contracts, operator contracts come with addition
 
 ### Multi-word Response
 
-In the EVM architecture, a word is made up of 32 bytes. One limitation of the [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol) contract is that it limits responses to requests to 32 bytes.
+In the EVM architecture, a word is made up of 32 bytes. One limitation of the [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol) contract is that it limits responses to requests to 32 bytes.
 
-[Operator.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) doesn't have the same limitation as it supports a response made of multiple EVM words.
+[Operator.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) doesn't have the same limitation as it supports a response made of multiple EVM words.
 
 ### Factory deployment
 
-To deploy an _Oracle_ contract, each node operator has to manually compile and deploy [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol).
+To deploy an _Oracle_ contract, each node operator has to manually compile and deploy [Oracle.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol).
 The vast number of Solidity versions and steps involved in verifying the contract made it difficult for a client to verify that the deployed contract had not been tampered with.
 To fix this, node operators can use a [factory](/chainlink-nodes/contracts/operatorfactory) to deploy an instance of the _operator_ contract. Moreover, the factory exposes a getter for clients to check if it deployed a specific _operator_ contract address.
 
@@ -50,7 +50,7 @@ As discussed in the [forwarder](/chainlink-nodes/contracts/forwarder) contracts
 
 ## API Reference
 
-The operator contract inherits [AuthorizedReceiver](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/AuthorizedReceiver.sol) and [ConfirmedOwnerWithProposal](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol). Read [AuthorizedReceiver](/chainlink-nodes/contracts/receiver) and [ConfirmedOwnerWithProposal](/chainlink-nodes/contracts/ownership) API references.
+The operator contract inherits [AuthorizedReceiver](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/AuthorizedReceiver.sol) and [ConfirmedOwnerWithProposal](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol). Read [AuthorizedReceiver](/chainlink-nodes/contracts/receiver) and [ConfirmedOwnerWithProposal](/chainlink-nodes/contracts/ownership) API references.
 
 ### Methods
 
@@ -64,7 +64,7 @@ The operator contract inherits [AuthorizedReceiver](https://github.com/smartcont
 function oracleRequest(address sender, uint256 payment, bytes32 specId, address callbackAddress, bytes4 callbackFunctionId, uint256 nonce, uint256 dataVersion, bytes data) external
 ```
 
-Creates the Chainlink request. This is backwards compatible API with [Oracle.sol contracts](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/Oracle.sol), but the behavior changes because `callbackAddress` is assumed to be the same as the request sender.
+Creates the Chainlink request. This is backwards compatible API with [Oracle.sol contracts](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/Oracle.sol), but the behavior changes because `callbackAddress` is assumed to be the same as the request sender.
 
 ##### Parameters
 
diff --git a/src/content/chainlink-nodes/contracts/ownership.mdx b/src/content/chainlink-nodes/contracts/ownership.mdx
index 99ce03ff546..c94b4409b9b 100644
--- a/src/content/chainlink-nodes/contracts/ownership.mdx
+++ b/src/content/chainlink-nodes/contracts/ownership.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "Ownership"
 ---
 
-[ConfirmedOwnerWithProposal](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol) is inherited by [operator](/chainlink-nodes/contracts/operator) and [forwarder](/chainlink-nodes/contracts/forwarder) contracts. It contains helpers for basic contract ownership.
+[ConfirmedOwnerWithProposal](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/ConfirmedOwnerWithProposal.sol) is inherited by [operator](/chainlink-nodes/contracts/operator) and [forwarder](/chainlink-nodes/contracts/forwarder) contracts. It contains helpers for basic contract ownership.
 
 ## API Reference
 
diff --git a/src/content/chainlink-nodes/contracts/receiver.mdx b/src/content/chainlink-nodes/contracts/receiver.mdx
index 336e58d3e80..048e1de2f5d 100644
--- a/src/content/chainlink-nodes/contracts/receiver.mdx
+++ b/src/content/chainlink-nodes/contracts/receiver.mdx
@@ -6,7 +6,7 @@ title: "Receiver"
 
 import { Aside } from "@components"
 
-[AuthorizedReceiver](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/AuthorizedReceiver.sol) is an abstract contract inherited by [operator](/chainlink-nodes/contracts/operator) and [forwarder](/chainlink-nodes/contracts/forwarder) contracts.
+[AuthorizedReceiver](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/AuthorizedReceiver.sol) is an abstract contract inherited by [operator](/chainlink-nodes/contracts/operator) and [forwarder](/chainlink-nodes/contracts/forwarder) contracts.
 
 <Aside type="note">
 Calling [setAuthorizedSenders](#setauthorizedsenders) has a different effect depending if it is called from an [operator](/chainlink-nodes/contracts/operator) or a [forwarder](/chainlink-nodes/contracts/forwarder) contract:
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-existing-job.mdx b/src/content/chainlink-nodes/job-specs/direct-request-existing-job.mdx
index dc7899708c9..48a658ed9f0 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-existing-job.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-existing-job.mdx
@@ -7,7 +7,7 @@ title: "Existing Job Example specs"
 This is an example v2 (TOML) job spec for returning gas price using [etherscan](https://docs.etherscan.io/api-endpoints/gas-tracker#get-gas-oracle) in one Chainlink API Call. Note that the job :
 
 - Uses an [external adapter](/chainlink-nodes/external-adapters/external-adapters) to consume the etherscan API: [EtherScan External Adapter](https://github.com/smartcontractkit/external-adapters-js/tree/develop/packages/sources/etherscan). Note that this is done using the [bridge](/chainlink-nodes/oracle-jobs/all-tasks/#bridge-task) task: `type="bridge" name="etherscan"`.
-- Calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+- Calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 
 To test this job spec from a smart contract, see this [Example](/any-api/get-request/examples/existing-job-request).
 
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-get-bool.mdx b/src/content/chainlink-nodes/job-specs/direct-request-get-bool.mdx
index 863bf108b81..6d744500184 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-get-bool.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-get-bool.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "GET > Bool Example Job Spec"
 ---
 
-This is an example v2 (TOML) job spec for calling any public API, parsing the result then returning a _bool_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for calling any public API, parsing the result then returning a _bool_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 
 ```toml
 type = "directrequest"
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-get-bytes.mdx b/src/content/chainlink-nodes/job-specs/direct-request-get-bytes.mdx
index 765308d4286..c3c9b2bb1cd 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-get-bytes.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-get-bytes.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "GET > Bytes Example Job Spec"
 ---
 
-This is an example v2 (TOML) job spec for returning _bytes_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for returning _bytes_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 To test it from a smart contract, see this [Example](/any-api/get-request/examples/large-responses).
 
 ```toml
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-get-int256.mdx b/src/content/chainlink-nodes/job-specs/direct-request-get-int256.mdx
index 260f878450e..b13438a66f4 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-get-int256.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-get-int256.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "GET > Int256 Example Job Spec"
 ---
 
-This is an example v2 (TOML) job spec for calling any public API, retrieving a number , removing its decimals then returning _int256_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for calling any public API, retrieving a number , removing its decimals then returning _int256_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 
 ```toml
 type = "directrequest"
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-get-string.mdx b/src/content/chainlink-nodes/job-specs/direct-request-get-string.mdx
index c83197bb7e9..7645ddd4796 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-get-string.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-get-string.mdx
@@ -6,7 +6,7 @@ title: "GET > String Example Job Spec"
 
 import { CodeSample } from "@components"
 
-This is an example v2 (TOML) job spec for returning a _string_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for returning a _string_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 To test it from a smart contract, see this [Example](/any-api/get-request/examples/array-response).
 
 {/* prettier-ignore */}
diff --git a/src/content/chainlink-nodes/job-specs/direct-request-get-uint256.mdx b/src/content/chainlink-nodes/job-specs/direct-request-get-uint256.mdx
index e4ba33d06d8..819f6e2c218 100644
--- a/src/content/chainlink-nodes/job-specs/direct-request-get-uint256.mdx
+++ b/src/content/chainlink-nodes/job-specs/direct-request-get-uint256.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "GET > Uint256 Example Job Spec"
 ---
 
-This is an example v2 (TOML) job spec for calling any public API, retrieving a number , removing its decimals then returning _uint256_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for calling any public API, retrieving a number , removing its decimals then returning _uint256_ in one Chainlink API Call. Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 To test it from a smart contract, see this [Example](/any-api/get-request/examples/single-word-response).
 
 ```toml
diff --git a/src/content/chainlink-nodes/job-specs/multi-word-job.mdx b/src/content/chainlink-nodes/job-specs/multi-word-job.mdx
index b1afa9437e8..a565be32d90 100644
--- a/src/content/chainlink-nodes/job-specs/multi-word-job.mdx
+++ b/src/content/chainlink-nodes/job-specs/multi-word-job.mdx
@@ -4,7 +4,7 @@ date: Last Modified
 title: "MultiWord Example Job Spec"
 ---
 
-This is an example v2 (TOML) job spec for returning multiple responses in 1 Chainlink API Call.Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/Operator.sol) with this job.
+This is an example v2 (TOML) job spec for returning multiple responses in 1 Chainlink API Call.Note that the job calls the `fulfillOracleRequest2` function. If you are a node operator, use an [Operator contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/Operator.sol) with this job.
 To test it from a smart contract, see this [Example](/any-api/get-request/examples/multi-variable-responses).
 
 ```toml
diff --git a/src/content/chainlink-nodes/resources/run-an-ethereum-client.mdx b/src/content/chainlink-nodes/resources/run-an-ethereum-client.mdx
index cb85f030b93..e914f6e2473 100644
--- a/src/content/chainlink-nodes/resources/run-an-ethereum-client.mdx
+++ b/src/content/chainlink-nodes/resources/run-an-ethereum-client.mdx
@@ -97,7 +97,7 @@ Return to [Running a Chainlink Node](/chainlink-nodes/v1/running-a-chainlink-nod
 
 ## Nethermind
 
-You can use the [Nethermind client](https://docs.nethermind.io/nethermind/) for the Goerli testnet and the Ethereum Mainnet. See the [Nethermind supported network configurations](https://docs.nethermind.io/nethermind/ethereum-client/docker#available-configurations) page for a list of supported networks.
+You can use the [Nethermind client](https://docs.nethermind.io) for the Goerli testnet and the Ethereum Mainnet. See the [Nethermind supported network configurations](https://docs.nethermind.io/get-started/installing-nethermind#supported-networks) page for a list of supported networks.
 
 Download the latest version:
 
diff --git a/src/content/chainlink-nodes/v1/node-config.mdx b/src/content/chainlink-nodes/v1/node-config.mdx
index 9f36a147096..93da1f8935c 100644
--- a/src/content/chainlink-nodes/v1/node-config.mdx
+++ b/src/content/chainlink-nodes/v1/node-config.mdx
@@ -7033,7 +7033,7 @@ SkipPreflight enables or disables preflight checks when sending txs.
 Commitment = 'confirmed' # Default
 ```
 
-Commitment is the confirmation level for solana state and transactions. ([documentation](https://docs.solana.com/developing/clients/jsonrpc-api#configuring-state-commitment))
+Commitment is the confirmation level for solana state and transactions. ([documentation](https://solana.com/docs/rpc#configuring-state-commitment))
 
 ### MaxRetries
 
diff --git a/src/content/data-feeds/feed-registry/index.mdx b/src/content/data-feeds/feed-registry/index.mdx
index 5880f7772d2..15087ed962e 100644
--- a/src/content/data-feeds/feed-registry/index.mdx
+++ b/src/content/data-feeds/feed-registry/index.mdx
@@ -9,7 +9,7 @@ metadata:
 whatsnext:
   {
     "Read the Feed Registry API Reference": "/data-feeds/feed-registry/feed-registry-functions",
-    "See the FeedRegistryInterface contract on GitHub": "https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/FeedRegistryInterface.sol",
+    "See the FeedRegistryInterface contract on GitHub": "https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/interfaces/FeedRegistryInterface.sol",
   }
 ---
 
@@ -60,7 +60,7 @@ latestRoundData(0x514910771AF9Ca656af840dff83E8264EcF986CA, 0xEeeeeEeeeEeEeeEeEe
 
 ### Denominations library
 
-A [`Denominations`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/Denominations.sol) Solidity library is available for you to fetch currency identifiers which lack a canonical Ethereum address:
+A [`Denominations`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/Denominations.sol) Solidity library is available for you to fetch currency identifiers which lack a canonical Ethereum address:
 
 <CodeSample src="samples/FeedRegistry/Denominations.sol" />
 
@@ -68,7 +68,7 @@ A [`Denominations`](https://github.com/smartcontractkit/chainlink/blob/develop/c
 
 ### Solidity
 
-To consume price data from the Feed Registry, your smart contract should reference [`FeedRegistryInterface`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/FeedRegistryInterface.sol), which defines the external functions implemented by the Feed Registry.
+To consume price data from the Feed Registry, your smart contract should reference [`FeedRegistryInterface`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/interfaces/FeedRegistryInterface.sol), which defines the external functions implemented by the Feed Registry.
 
 <CodeSample src="samples/FeedRegistry/PriceConsumer.sol" />
 
diff --git a/src/content/data-feeds/getting-started.mdx b/src/content/data-feeds/getting-started.mdx
index 90575dff1a0..8515bd46baf 100644
--- a/src/content/data-feeds/getting-started.mdx
+++ b/src/content/data-feeds/getting-started.mdx
@@ -17,7 +17,7 @@ metadata:
 
 import { Aside, CodeSample } from "@components"
 
-You can use Chainlink Data Feeds to connect your smart contracts to asset pricing data like the [ETH / USD feed](https://data.chain.link/eth-usd). These data feeds use data aggregated from many independent Chainlink node operators. Each price feed has an onchain address and functions that enable contracts to read pricing data from that address.
+You can use Chainlink Data Feeds to connect your smart contracts to asset pricing data like the [ETH / USD feed](https://data.chain.link/feeds/ethereum/mainnet/eth-usd). These data feeds use data aggregated from many independent Chainlink node operators. Each price feed has an onchain address and functions that enable contracts to read pricing data from that address.
 
 This guide shows you how to read Data Feeds and store the value onchain using Solidity. To learn how to read feeds offchain or use different languages, see the [Using Data Feeds on EVM Chains](/data-feeds/using-data-feeds) guide. Alternatively, you can also learn how to use Data Feeds on [Solana](/data-feeds/solana) or [StarkNet](/data-feeds/starknet).
 
diff --git a/src/content/data-feeds/historical-data.mdx b/src/content/data-feeds/historical-data.mdx
index df32b7be4c9..c2c7b221908 100644
--- a/src/content/data-feeds/historical-data.mdx
+++ b/src/content/data-feeds/historical-data.mdx
@@ -44,7 +44,7 @@ The examples in this document name the aggregator `roundId` as `aggregatorRoundI
 
 ### `roundId` in Proxy
 
-Because a proxy has references to current and all previous underlying aggregators, it needs a way to fetch data from the correct aggregator. The `roundId` is computed in the [proxy contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/dev/AggregatorProxy.sol) as shown in the following example:
+Because a proxy has references to current and all previous underlying aggregators, it needs a way to fetch data from the correct aggregator. The `roundId` is computed in the [proxy contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/dev/AggregatorProxy.sol) as shown in the following example:
 
 {/* prettier-ignore */}
 ```solidity
diff --git a/src/content/data-feeds/index.mdx b/src/content/data-feeds/index.mdx
index 11a01efe1c7..20c0fcfee1f 100644
--- a/src/content/data-feeds/index.mdx
+++ b/src/content/data-feeds/index.mdx
@@ -87,7 +87,7 @@ To learn how to use L2 sequencer uptime feeds feeds, see the [L2 Sequencer Uptim
 Data Feeds are an example of a decentralized oracle network and include the following components:
 
 - **Consumer**: A consumer is an onchain or offchain application that uses Data Feeds. Consumer contracts use the [`AggregatorV3Interface`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/shared/interfaces/AggregatorV3Interface.sol) to call functions on the proxy contract and retrieve information from the aggregator contract. For a complete list of functions available in the `AggregatorV3Interface`, see the [Data Feeds API Reference](/data-feeds/api-reference/#aggregatorv3interface).
-- **Proxy contract**: Proxy contracts are onchain proxies that point to the aggregator for a particular data feed. Using proxies enables the underlying aggregator to be upgraded without any service interruption to consuming contracts. Proxy contracts can vary from one data feed to another, but the [`AggregatorProxy.sol` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/dev/AggregatorProxy.sol) on Github is a common example.
+- **Proxy contract**: Proxy contracts are onchain proxies that point to the aggregator for a particular data feed. Using proxies enables the underlying aggregator to be upgraded without any service interruption to consuming contracts. Proxy contracts can vary from one data feed to another, but the [`AggregatorProxy.sol` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.7/dev/AggregatorProxy.sol) on Github is a common example.
 - **Aggregator contract**: An aggregator is a contract that receives periodic data updates from the oracle network. Aggregators store aggregated data onchain so that consumers can retrieve it and act upon it within the same transaction. For a complete list of functions and variables available on most aggregator contracts, see the [Data Feeds API Reference](/data-feeds/api-reference/#accesscontrolledoffchainaggregator).
 
 To learn how to create a consumer contract that uses an existing data feed, read the [Using Data Feeds](/data-feeds/price-feeds) documentation.
diff --git a/src/content/data-feeds/l2-sequencer-feeds.mdx b/src/content/data-feeds/l2-sequencer-feeds.mdx
index f0f9dad6c32..765d9f6f88c 100644
--- a/src/content/data-feeds/l2-sequencer-feeds.mdx
+++ b/src/content/data-feeds/l2-sequencer-feeds.mdx
@@ -34,10 +34,10 @@ The diagram below shows how these feeds update and how a consumer retrieves the
 
 <ClickToZoom src="/images/data-feed/l2-diagram-arbitrum.webp" />
 
-1. Chainlink nodes trigger an OCR round every 30s and update the sequencer status by calling the `validate` function in the [`ArbitrumValidator` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/dev/ArbitrumValidator.sol) by calling it through the [`ValidatorProxy` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/ValidatorProxy.sol).
+1. Chainlink nodes trigger an OCR round every 30s and update the sequencer status by calling the `validate` function in the [`ArbitrumValidator` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumValidator.sol) by calling it through the [`ValidatorProxy` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/ValidatorProxy.sol).
 1. The `ArbitrumValidator` checks to see if the latest update is different from the previous update. If it detects a difference, it places a message in the [Arbitrum inbox contract](https://developer.offchainlabs.com/docs/inside_arbitrum#the-big-picture).
-1. The inbox contract sends the message to the [`ArbitrumSequencerUptimeFeed` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/dev/ArbitrumSequencerUptimeFeed.sol). The message calls the `updateStatus` function in the `ArbitrumSequencerUptimeFeed` contract and updates the latest sequencer status to 0 if the sequencer is up and 1 if it is down. It also records the block timestamp to indicate when the message was sent from the L1 network.
-1. A consumer contract on the L2 network can read these values from the [`ArbitrumUptimeFeedProxy` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.6/EACAggregatorProxy.sol), which reads values from the `ArbitrumSequencerUptimeFeed` contract.
+1. The inbox contract sends the message to the [`ArbitrumSequencerUptimeFeed` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumSequencerUptimeFeed.sol). The message calls the `updateStatus` function in the `ArbitrumSequencerUptimeFeed` contract and updates the latest sequencer status to 0 if the sequencer is up and 1 if it is down. It also records the block timestamp to indicate when the message was sent from the L1 network.
+1. A consumer contract on the L2 network can read these values from the [`ArbitrumUptimeFeedProxy` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.6/EACAggregatorProxy.sol), which reads values from the `ArbitrumSequencerUptimeFeed` contract.
 
 ### Handling Arbitrum outages
 
diff --git a/src/content/data-feeds/proof-of-reserve/index.mdx b/src/content/data-feeds/proof-of-reserve/index.mdx
index cbecbe165fb..d45e1a439bf 100644
--- a/src/content/data-feeds/proof-of-reserve/index.mdx
+++ b/src/content/data-feeds/proof-of-reserve/index.mdx
@@ -44,7 +44,7 @@ Cross-chain reserves are sourced from the network where the reserves are held. C
 
 Cross-chain reserves provide their data using the following methods:
 
-- Wallet address manager: The project uses the [IPoRAddressList](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/PoRAddressList.sol) wallet address manager contract and self-attests to which addresses they own.
+- Wallet address manager: The project uses the [IPoRAddressList](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/interfaces/PoRAddressList.sol) wallet address manager contract and self-attests to which addresses they own.
 - Wallet address: The project attests which addresses they own through a self-hosted API.
 
 ## Using Proof of Reserve Feeds
diff --git a/src/content/data-feeds/solana/using-data-feeds-off-chain.mdx b/src/content/data-feeds/solana/using-data-feeds-off-chain.mdx
index 4bbf8a0de4f..d25ea9f4561 100644
--- a/src/content/data-feeds/solana/using-data-feeds-off-chain.mdx
+++ b/src/content/data-feeds/solana/using-data-feeds-off-chain.mdx
@@ -112,7 +112,7 @@ Install the necessary components and include the example code in your project. O
     solana-keygen new --outfile ./id.json
     ```
 
-1.  Set the [Anchor environment variables](https://www.twilio.com/blog/2017/01/how-to-set-environment-variables.html). Anchor uses these to determine which wallet to use and how to get a connection to a Solana cluster. Because this example does not generate or sign any transactions, no lamports are required. The wallet is required only by the Anchor library. For a list of available networks and endpoints, see the [Solana Cluster RPC Endpoints](https://docs.solana.com/cluster/rpc-endpoints) documentation.
+1.  Set the [Anchor environment variables](https://www.twilio.com/en-us/blog/how-to-set-environment-variables-html). Anchor uses these to determine which wallet to use and how to get a connection to a Solana cluster. Because this example does not generate or sign any transactions, no lamports are required. The wallet is required only by the Anchor library. For a list of available networks and endpoints, see the [Solana Cluster RPC Endpoints](https://docs.solana.com/cluster/rpc-endpoints) documentation.
 
     ```shell
     export ANCHOR_PROVIDER_URL=https://api.devnet.solana.com &&
@@ -207,7 +207,7 @@ After you install the required tools, clone the example code from the [solana-st
    solana-keygen new --outfile ./id.json
    ```
 
-1. Set the [Anchor environment variables](https://www.twilio.com/blog/2017/01/how-to-set-environment-variables.html). Anchor uses these to determine which wallet to use and Solana cluster to use. Take note that because we are not generating or signing any transactions, the wallet isn't used, it's just required by the Anchor library. For a list of available networks and endpoints, see the [Solana Cluster RPC Endpoints](https://docs.solana.com/cluster/rpc-endpoints) documentation.
+1. Set the [Anchor environment variables](https://www.twilio.com/en-us/blog/how-to-set-environment-variables-html). Anchor uses these to determine which wallet to use and Solana cluster to use. Take note that because we are not generating or signing any transactions, the wallet isn't used, it's just required by the Anchor library. For a list of available networks and endpoints, see the [Solana Cluster RPC Endpoints](https://docs.solana.com/cluster/rpc-endpoints) documentation.
 
    ```shell Solana Devnet
    export ANCHOR_PROVIDER_URL=https://api.devnet.solana.com &&
diff --git a/src/content/data-feeds/solana/using-data-feeds-solana.mdx b/src/content/data-feeds/solana/using-data-feeds-solana.mdx
index 70200c39e17..8cf80e4192d 100644
--- a/src/content/data-feeds/solana/using-data-feeds-solana.mdx
+++ b/src/content/data-feeds/solana/using-data-feeds-solana.mdx
@@ -237,7 +237,7 @@ Now that the program is onchain, you can call it.
 
 Use your deployed program to retrieve price data from a Chainlink data feed on Solana Devnet. For this example, call your deployed program using the [`client.js` example](https://github.com/smartcontractkit/solana-starter-kit/blob/main/client.js) code.
 
-1. Set the [Anchor environment variables](https://www.twilio.com/blog/2017/01/how-to-set-environment-variables.html). Anchor uses these to determine which wallet to use and Solana cluster to use.
+1. Set the [Anchor environment variables](https://www.twilio.com/en-us/blog/how-to-set-environment-variables-html). Anchor uses these to determine which wallet to use and Solana cluster to use.
 
    ```shell
    export ANCHOR_PROVIDER_URL=https://api.devnet.solana.com &&
diff --git a/src/content/getting-started/conceptual-overview.mdx b/src/content/getting-started/conceptual-overview.mdx
index 6da67f5bb6e..afc3cb5a4ed 100644
--- a/src/content/getting-started/conceptual-overview.mdx
+++ b/src/content/getting-started/conceptual-overview.mdx
@@ -152,7 +152,7 @@ Oracles play a critical role in facilitating the full potential of smart contrac
 
 Oracles are most popularly used with [_Data Feeds_](/data-feeds). DeFi platforms like [AAVE](https://aave.com/) and [Synthetix](https://www.synthetix.io/) use Chainlink data feed oracles to obtain accurate real-time asset prices in their smart contracts.
 
-Chainlink data feeds are sources of data [aggregated from many independent Chainlink node operators](/architecture-overview/architecture-decentralized-model). Each data feed has an onchain address and functions that enable contracts to read from that address. For example, the [ETH / USD feed](https://data.chain.link/eth-usd/).
+Chainlink data feeds are sources of data [aggregated from many independent Chainlink node operators](/architecture-overview/architecture-decentralized-model). Each data feed has an onchain address and functions that enable contracts to read from that address. For example, the [ETH / USD feed](https://data.chain.link/feeds/ethereum/mainnet/eth-usd).
 
 ![Chainlink Feeds List](/images/contract-devs/price-aggr.png)
 
diff --git a/src/content/getting-started/other-tutorials.mdx b/src/content/getting-started/other-tutorials.mdx
index 77bfffe19d0..0665579f7f4 100644
--- a/src/content/getting-started/other-tutorials.mdx
+++ b/src/content/getting-started/other-tutorials.mdx
@@ -81,7 +81,7 @@ Below is a list of applications of Chainlink's products and services sorted by d
 | [Smart Contract Automation Master Class Module #3](https://youtu.be/FirUe1YCcqs)                                                                                                                       | Automation | Beginner   |
 | [Smart Contract Automation Master Class Module #4](https://youtu.be/1a0wguM5Ig0)                                                                                                                       | Automation | Beginner   |
 | [Entropyfi Saves Engineering Hours with Chainlink Automation](https://medium.com/entropyfi/entropyfi-saves-engineering-hours-with-chainlink-keepers-6ec172a76249)                                      | Gaming     | Medium     |
-| [Enabling Limit Orders on CivTrade With Chainlink Automation](https://news.civfund.org/civtrade-with-chainlink-keepers-8b6c3965a92e)                                                                   | Trading    | Medium     |
+| [Enabling Limit Orders on CivTrade With Chainlink Automation](https://docs.civfund.org/civilization/civtrade/integrations/chainlink)                                                                   | Trading    | Medium     |
 | [Pickle Finance UniV3 Jars Powered by Chainlink Automation](https://picklefinance.medium.com/pickle-finance-univ3-jars-powered-by-chainlink-keepers-8ce1756a2497)                                      | Finance    | Medium     |
 | [JamonSwap Introduces New Limit Order Functionality Using Chainlink Automation](https://medium.com/@JamonSwap/jamonswap-introduces-new-limit-order-functionality-using-chainlink-keepers-51bd94d75feb) | DeFi       | Medium     |
 | [How Cratos used Chainlink Automation to automate the token vesting process](https://cratostoken.medium.com/how-cratos-used-chainlink-keepers-to-automate-the-token-vesting-process-69bcb3611161)      | DeFi       | Medium     |
diff --git a/src/content/quickstarts/eth-balance-monitor.mdx b/src/content/quickstarts/eth-balance-monitor.mdx
index 99ba2a6cb11..94d9525a8ca 100644
--- a/src/content/quickstarts/eth-balance-monitor.mdx
+++ b/src/content/quickstarts/eth-balance-monitor.mdx
@@ -109,7 +109,7 @@ After you are done with this example, you can run the `withdraw` function on you
 
 ## Examine the example code
 
-The [`EthBalanceMonitor` contract](https://github.com/smartcontractkit/documentation/blob/main/public/samples/Automation/tutorials/EthBalanceMonitor.sol) is ownable, pauseable, and compatible with the [`AutomationCompatibleInterface` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/interfaces/AutomationCompatibleInterface.sol):
+The [`EthBalanceMonitor` contract](https://github.com/smartcontractkit/documentation/blob/main/public/samples/Automation/tutorials/EthBalanceMonitor.sol) is ownable, pauseable, and compatible with the [`AutomationCompatibleInterface` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/interfaces/AutomationCompatibleInterface.sol):
 
 - **Ownable**: The contract has an owner address, and provides basic authorization control functions. This simplifies the implementation of _user permissions_ and allows for transfer of ownership.
 - **Pauseable**: This feature allows the contract to implement a pause and unpause mechanism that the contract owner can trigger.
diff --git a/src/content/quickstarts/foundry-chainlink-toolkit.mdx b/src/content/quickstarts/foundry-chainlink-toolkit.mdx
index 0615758c330..19c80316181 100644
--- a/src/content/quickstarts/foundry-chainlink-toolkit.mdx
+++ b/src/content/quickstarts/foundry-chainlink-toolkit.mdx
@@ -165,7 +165,7 @@ Once Chainlink cluster is launched, a Chainlink nodes' Operator GUI will be avai
 - http://127.0.0.1:6744 - Chainlink node 4
 - http://127.0.0.1:6755 - Chainlink node 5
 
-For authorization, you must use the credentials specified in the [chainlink_api_credentials](https://github.com/smartcontractkit/foundry-chainlink-toolkit/blob/main/https://github.com/smartcontractkit/foundry-chainlink-toolkit/tree/main/chainlink/settings/chainlink_api_credentials).
+For authorization, you must use the credentials specified in the [chainlink_api_credentials](https://github.com/smartcontractkit/foundry-chainlink-toolkit/tree/main/src/sandbox/clroot/settings/chainlink_api_credentials).
 
 </Accordion>
 
diff --git a/src/content/quickstarts/price-feeds-showcase.mdx b/src/content/quickstarts/price-feeds-showcase.mdx
index a3f30cfdaa0..d30179267ed 100644
--- a/src/content/quickstarts/price-feeds-showcase.mdx
+++ b/src/content/quickstarts/price-feeds-showcase.mdx
@@ -84,7 +84,7 @@ This tutorial shows you how to install and configure the [Solana Prediction Game
 1. Set up a Solana wallet. For this example, [install the Phantom wallet](https://phantom.app/):
 
    1. Visit https://phantom.app/download and select your browser type. Follow the steps in your respective extension store to add Phantom to your browser. After installing, you should see Phantom start-up in a new tab.
-   1. If you are a brand new Solana user, select "Create New Wallet" and create a password. If you are an existing Solana user, you can follow the steps [here](https://phantom.app/help/migrating-from-sollet-to-phantom) to migrate your existing wallets to Phantom.
+   1. If you are a brand new Solana user, select "Create New Wallet" and create a password. If you are an existing Solana user, you can follow the steps [here](https://help.phantom.app/hc/en-us/articles/4406527601811-How-to-migrate-from-Sollet) to migrate your existing wallets to Phantom.
    1. Store your "Secret Recovery Phrase" in a safe and secure location, it is the only way to recover your wallet. Whoever has access to this phrase has access to your funds.
 
 1. Set up Phantom mobile app.
@@ -103,7 +103,7 @@ This tutorial shows you how to install and configure the [Solana Prediction Game
 1. Copy your Phantom Wallet address
 1. Paste your wallet address into the text field and then click 'DEVNET' to send the Solana token
 
-1. [Switch your network to `devnet` on your wallet](https://docs.realms.today/phantom-wallet).
+1. [Switch your network to `devnet` on your wallet](https://www.blog.goosefx.io/switch-from-mainnet-to-devnet-network-on-solana).
 
 ## Steps to implement
 
diff --git a/src/content/quickstarts/vrf-mystery-box.mdx b/src/content/quickstarts/vrf-mystery-box.mdx
index 64b41c4a64a..22e9172c3cb 100644
--- a/src/content/quickstarts/vrf-mystery-box.mdx
+++ b/src/content/quickstarts/vrf-mystery-box.mdx
@@ -137,7 +137,7 @@ npm run coverage
 
 <Accordion title="Deploy the example contract" number={3}>
 
-Run the `npx hardhat run` command and replace `<network>` with the network that you want to deploy to. The network must be configured in [`hardhat.config.ts`](https://github.com/smartcontractkit/chainlink-solutions-mysterybox/blob/main/hardhat.config.ts).
+Run the `npx hardhat run` command and replace `<network>` with the network that you want to deploy to. The network must be configured in [`hardhat.config.ts`](https://github.com/smartcontractkit/quickstarts-mysterybox/blob/main/hardhat.config.ts).
 
 ```bash
 npx hardhat run scripts/deploy.ts --network <network>
@@ -145,7 +145,7 @@ npx hardhat run scripts/deploy.ts --network <network>
 
 In addition to deploying the contract, the deploy script also completes the following steps automatically:
 
-1.  Create and fund a VRF subscription if one is not provided. Make sure the deployer account has enough LINK to fund the subscription. The initial funding amount is configured in [`network-config.ts`](https://github.com/smartcontractkit/chainlink-solutions-mysterybox/blob/main/network-config.ts). For testnets, you can use the [LINK faucet](https://faucets.chain.link/) to get LINK. If your subscription is underfunded, your VRF request will be [pending](/vrf/v2/subscription/ui#pending) for 24 hours. If this happens, check the [Subscription Manager](https://vrf.chain.link]) to see the additional balance needed.
+1.  Create and fund a VRF subscription if one is not provided. Make sure the deployer account has enough LINK to fund the subscription. The initial funding amount is configured in [`network-config.ts`](https://github.com/smartcontractkit/quickstarts-mysterybox/blob/main/network-config.ts). For testnets, you can use the [LINK faucet](https://faucets.chain.link/) to get LINK. If your subscription is underfunded, your VRF request will be [pending](/vrf/v2/subscription/ui#pending) for 24 hours. If this happens, check the [Subscription Manager](https://vrf.chain.link]) to see the additional balance needed.
 
 1.  Add the deployed contract address as a consumer to the VRF subscription. If you provided a subscription ID, make sure the deployer account is the owner of the subscription. Otherwise, comment out the `addVrfConsumer` function in the deploy script and add the contract address manually.
 
diff --git a/src/content/quickstarts/web3js.mdx b/src/content/quickstarts/web3js.mdx
index 7fd547e0d75..c01d4f3fdef 100644
--- a/src/content/quickstarts/web3js.mdx
+++ b/src/content/quickstarts/web3js.mdx
@@ -82,7 +82,7 @@ Run the following tests:
     - `yarn test:black-box`: Calls `yarn pre-black-box` and `runTests` from the from the `black_box_test_helpers.sh` script
     - `yarn post-black-box`: Calls `stop` from the `black_box_test_helpers.sh` script
 
-More information about registering web3.js plugins can be found [here](https://docs.web3js.org/docs/guides/web3_plugin_guide/plugin_users#registering-the-plugin).
+More information about registering web3.js plugins can be found [here](https://docs.web3js.org/guides/web3_plugin_guide/plugin_users#registering-the-plugin).
 
 </Accordion>
 
diff --git a/src/content/resources/hackathon-resources.mdx b/src/content/resources/hackathon-resources.mdx
index c1b4ff96817..13c50207c4f 100644
--- a/src/content/resources/hackathon-resources.mdx
+++ b/src/content/resources/hackathon-resources.mdx
@@ -34,7 +34,6 @@ If you are new to Smart Contracts, read the [Getting Started Guide](/getting-sta
 
 - [Learning Resources](/getting-started/other-tutorials)
 - [Video Tutorials](https://www.youtube.com/playlist?list=PLVP9aGDn-X0QwJVbQvuKr-zrh2_DV5M6J)
-- [@Chain_Dev Video Tutorials](https://www.youtube.com/@Chain_Dev/videos)
 - [What is Ethereum?](https://www.youtube.com/playlist?list=PLVP9aGDn-X0QwJVbQvuKr-zrh2_DV5M6J)
 - [Developer Blog featuring several tutorials](https://blog.chain.link/tag/developers/)
 - [Testing Chainlink Smart Contracts](https://blog.chain.link/testing-chainlink-smart-contracts/)
diff --git a/src/content/vrf/index.mdx b/src/content/vrf/index.mdx
index 46c5cfb6b1d..e3367d01e9f 100644
--- a/src/content/vrf/index.mdx
+++ b/src/content/vrf/index.mdx
@@ -3,6 +3,7 @@ section: vrf
 date: Last Modified
 title: "Chainlink VRF"
 isMdx: true
+isIndex: true
 whatsnext: { "Subscription Method": "/vrf/v2/subscription", "Direct Funding Method": "/vrf/v2/direct-funding" }
 metadata:
   title: "Generate Random Numbers for Smart Contracts using Chainlink VRF"
diff --git a/src/content/vrf/v2/direct-funding/examples/get-a-random-number.mdx b/src/content/vrf/v2/direct-funding/examples/get-a-random-number.mdx
index 80bfca60d06..d31adf7f15b 100644
--- a/src/content/vrf/v2/direct-funding/examples/get-a-random-number.mdx
+++ b/src/content/vrf/v2/direct-funding/examples/get-a-random-number.mdx
@@ -34,7 +34,7 @@ If you are new to developing smart contracts on Ethereum, see the [Getting Start
 
 For this example, use the [VRFv2DirectFundingConsumer.sol](https://remix.ethereum.org/#url=https://docs.chain.link/samples/VRF/VRFv2DirectFundingConsumer.sol) sample contract. This contract imports the following dependencies:
 
-- `VRFV2WrapperConsumerBase.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol)
+- `VRFV2WrapperConsumerBase.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol)
 - `ConfirmedOwner.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/shared/access/ConfirmedOwner.sol)
 
 The contract also includes pre-configured values for the necessary request parameters such as `callbackGasLimit`, `requestConfirmations`, the number of random words `numWords`, the VRF v2 Wrapper address `wrapperAddress`, and the LINK token address `linkAddress`. You can change these parameters if you want to experiment on different testnets.
diff --git a/src/content/vrf/v2/direct-funding/examples/test-locally.mdx b/src/content/vrf/v2/direct-funding/examples/test-locally.mdx
index a34742f2421..1f5a0123674 100644
--- a/src/content/vrf/v2/direct-funding/examples/test-locally.mdx
+++ b/src/content/vrf/v2/direct-funding/examples/test-locally.mdx
@@ -26,17 +26,17 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix-
 
 Complete the following tasks to test your VRF v2 consumer locally:
 
-1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract.
-1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract.
-1. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/LinkToken.sol) contract.
-1. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract.
-1. Call the VRFV2Wrapper [setConfig function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2Wrapper.sol#L119) to set wrapper specific parameters.
+1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract.
+1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract.
+1. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/LinkToken.sol) contract.
+1. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract.
+1. Call the VRFV2Wrapper [setConfig function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2Wrapper.sol#L119) to set wrapper specific parameters.
 1. Fund the VRFv2Wrapper subscription.
-1. Call the the VRFCoordinatorV2Mock [addConsumer function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L230) to add the wrapper contract to your subscription.
+1. Call the the VRFCoordinatorV2Mock [addConsumer function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L230) to add the wrapper contract to your subscription.
 1. Deploy your VRF consumer contract.
 1. Fund your consumer contract with LINK tokens.
 1. Request random words from your consumer contract.
-1. Call the VRFCoordinatorV2Mock [fulfillRandomWords function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L108) to fulfill your consumer contract request.
+1. Call the VRFCoordinatorV2Mock [fulfillRandomWords function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L108) to fulfill your consumer contract request.
 
 ## Prerequisites
 
diff --git a/src/content/vrf/v2/direct-funding/index.mdx b/src/content/vrf/v2/direct-funding/index.mdx
index 1cab39e5abb..b58c888fd97 100644
--- a/src/content/vrf/v2/direct-funding/index.mdx
+++ b/src/content/vrf/v2/direct-funding/index.mdx
@@ -37,19 +37,19 @@ Two types of accounts exist in the Ethereum ecosystem, and both are used in VRF:
 
 The Chainlink VRF v2 solution uses both offchain and onchain components:
 
-- [VRF v2 Wrapper (onchain component)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2Wrapper.sol): A wrapper for the VRF Coordinator that provides an interface for consuming contracts.
-- [VRF v2 Coordinator (onchain component)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol): A contract designed to interact with the VRF service. It emits an event when a request for randomness is made, and then verifies the random number and proof of how it was generated by the VRF service.
+- [VRF v2 Wrapper (onchain component)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2Wrapper.sol): A wrapper for the VRF Coordinator that provides an interface for consuming contracts.
+- [VRF v2 Coordinator (onchain component)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol): A contract designed to interact with the VRF service. It emits an event when a request for randomness is made, and then verifies the random number and proof of how it was generated by the VRF service.
 - VRF service (offchain component): Listens for requests by subscribing to the VRF Coordinator event logs and calculates a random number based on the block hash and nonce. The VRF service then sends a transaction to the `VRFCoordinator` including the random number and a proof of how it was generated.
 
 ### Set up your contract and request
 
 Set up your consuming contract:
 
-1. Your contract must inherit [VRFV2WrapperConsumerBase](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol).
+1. Your contract must inherit [VRFV2WrapperConsumerBase](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol).
 
 1. Your contract must implement the `fulfillRandomWords` function, which is the _callback VRF function_. Here, you add logic to handle the random values after they are returned to your contract.
 
-1. Submit your VRF request by calling the `requestRandomness` function in the [VRFV2WrapperConsumerBase](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol) contract. Include the following parameters in your request:
+1. Submit your VRF request by calling the `requestRandomness` function in the [VRFV2WrapperConsumerBase](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol) contract. Include the following parameters in your request:
 
    - `requestConfirmations`: The number of block confirmations the VRF service will wait to respond. The minimum and maximum confirmations for your network can be found [here](/vrf/v2/direct-funding/supported-networks/#configurations).
    - `callbackGasLimit`: The maximum amount of gas to pay for completing the callback VRF function.
@@ -59,11 +59,11 @@ Set up your consuming contract:
 
 After you submit your request, it is processed using the [Request & Receive Data](#request-and-receive-data) cycle:
 
-1. The consuming contract calls the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) `calculateRequestPrice` function to estimate the total transaction cost to fulfill randomness. Learn [how to estimate transaction costs](/vrf/v2/estimating-costs).
+1. The consuming contract calls the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) `calculateRequestPrice` function to estimate the total transaction cost to fulfill randomness. Learn [how to estimate transaction costs](/vrf/v2/estimating-costs).
 
-1. The consuming contract calls the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.4/LinkToken.sol) `transferAndCall` function to pay the wrapper with the calculated request price. This method sends LINK tokens and executes the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) `onTokenTransfer` logic.
+1. The consuming contract calls the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.4/LinkToken.sol) `transferAndCall` function to pay the wrapper with the calculated request price. This method sends LINK tokens and executes the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) `onTokenTransfer` logic.
 
-1. The VRFV2Wrapper's `onTokenTransfer` logic triggers the [VRF Coordinator](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) `requestRandomWords` function to request randomness.
+1. The VRFV2Wrapper's `onTokenTransfer` logic triggers the [VRF Coordinator](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) `requestRandomWords` function to request randomness.
 
 1. The VRF coordinator emits an event.
 
diff --git a/src/content/vrf/v2/direct-funding/migration-from-v1.mdx b/src/content/vrf/v2/direct-funding/migration-from-v1.mdx
index 3122f592b5a..0bd2c654bec 100644
--- a/src/content/vrf/v2/direct-funding/migration-from-v1.mdx
+++ b/src/content/vrf/v2/direct-funding/migration-from-v1.mdx
@@ -22,7 +22,7 @@ The main similarity between VRF v1 and VRF v2 Direct funding method is that cons
 
 To modify your existing smart contract code to work with VRF v2, complete the following changes. See the [Get a Random Number](/vrf/v2/direct-funding/examples/get-a-random-number) guide for an example.
 
-1. Import and inherit the new [`VRFV2WrapperConsumerBase.sol` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol) and remove the v1 `VRFConsumerBase.sol` import. This contract includes the `fulfillRandomWords` function.
+1. Import and inherit the new [`VRFV2WrapperConsumerBase.sol` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFV2WrapperConsumerBase.sol) and remove the v1 `VRFConsumerBase.sol` import. This contract includes the `fulfillRandomWords` function.
 
 1. Add a `VRFV2WrapperConsumerBase` constructor as shown in the [Get a Random Number](/vrf/v2/direct-funding/examples/get-a-random-number) example and use the correct VRF v2 Direct funding configuration.
 
diff --git a/src/content/vrf/v2/getting-started.mdx b/src/content/vrf/v2/getting-started.mdx
index 2962c489574..11118ce6b47 100644
--- a/src/content/vrf/v2/getting-started.mdx
+++ b/src/content/vrf/v2/getting-started.mdx
@@ -73,7 +73,7 @@ For this example, create a new subscription on the Sepolia testnet as explained
 Chainlink maintains a [library of contracts](https://github.com/smartcontractkit/chainlink/tree/master/contracts) that make consuming data from oracles easier. For Chainlink VRF, you will use:
 
 - [`VRFConsumerBaseV2`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol) that must be imported and extended from the contract that you create.
-- [`VRFCoordinatorV2Interface`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol) that must be imported to communicate with the VRF coordinator.
+- [`VRFCoordinatorV2Interface`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/interfaces/VRFCoordinatorV2Interface.sol) that must be imported to communicate with the VRF coordinator.
 
 {/* prettier-ignore */}
 ```solidity
diff --git a/src/content/vrf/v2/subscription/examples/get-a-random-number.mdx b/src/content/vrf/v2/subscription/examples/get-a-random-number.mdx
index 0816e9c68b3..889ce2f2faf 100644
--- a/src/content/vrf/v2/subscription/examples/get-a-random-number.mdx
+++ b/src/content/vrf/v2/subscription/examples/get-a-random-number.mdx
@@ -68,8 +68,8 @@ Now that you have a funded subscription account and your subscription ID, [creat
 
 For this example, use the [VRFv2Consumer.sol](https://remix.ethereum.org/#url=https://docs.chain.link/samples/VRF/VRFv2Consumer.sol) sample contract. This contract imports the following dependencies:
 
-- `VRFConsumerBaseV2.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol)
-- `VRFCoordinatorV2Interface.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol)
+- `VRFConsumerBaseV2.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol)
+- `VRFCoordinatorV2Interface.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/interfaces/VRFCoordinatorV2Interface.sol)
 - `ConfirmedOwner.sol`[(link)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/shared/access/ConfirmedOwner.sol)
 
 The contract also includes pre-configured values for the necessary request parameters such as `vrfCoordinator` address, gas lane `keyHash`, `callbackGasLimit`, `requestConfirmations` and number of random words `numWords`. You can change these parameters if you want to experiment on different testnets, but for this example you only need to specify `subscriptionId` when you deploy the contract.
diff --git a/src/content/vrf/v2/subscription/examples/programmatic-subscription.mdx b/src/content/vrf/v2/subscription/examples/programmatic-subscription.mdx
index 35b78ca125b..7d502e91727 100644
--- a/src/content/vrf/v2/subscription/examples/programmatic-subscription.mdx
+++ b/src/content/vrf/v2/subscription/examples/programmatic-subscription.mdx
@@ -25,7 +25,7 @@ You can view and monitor your subscriptions in the [Subscription Manager](/vrf/v
 
 ## Modifying subscriptions and configurations
 
-Subscription configurations do not have to be static. You can change your subscription configuration dynamically by calling the following functions using the [VRFCoordinatorV2Interface](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol):
+Subscription configurations do not have to be static. You can change your subscription configuration dynamically by calling the following functions using the [VRFCoordinatorV2Interface](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/interfaces/VRFCoordinatorV2Interface.sol):
 
 - Change the list of approved subscription consumers with:
   - `addConsumer(uint64 subId, address consumer)`.
diff --git a/src/content/vrf/v2/subscription/examples/test-locally.mdx b/src/content/vrf/v2/subscription/examples/test-locally.mdx
index 318589a4732..4e92cdbf5cf 100644
--- a/src/content/vrf/v2/subscription/examples/test-locally.mdx
+++ b/src/content/vrf/v2/subscription/examples/test-locally.mdx
@@ -26,13 +26,13 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix-
 
 Complete the following tasks to test your VRF v2 consumer locally:
 
-1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract.
-1. Call the VRFCoordinatorV2Mock [createSubscription function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L194) to create a new subscription.
-1. Call the VRFCoordinatorV2Mock [fundSubscription function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L156) to fund your newly created subscription. **Note**: You can fund with an arbitrary amount.
+1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract.
+1. Call the VRFCoordinatorV2Mock [createSubscription function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L194) to create a new subscription.
+1. Call the VRFCoordinatorV2Mock [fundSubscription function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L156) to fund your newly created subscription. **Note**: You can fund with an arbitrary amount.
 1. Deploy your VRF consumer contract.
-1. Call the the VRFCoordinatorV2Mock [addConsumer function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L230) to add your consumer contract to your subscription.
+1. Call the the VRFCoordinatorV2Mock [addConsumer function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L230) to add your consumer contract to your subscription.
 1. Request random words from your consumer contract.
-1. Call the VRFCoordinatorV2Mock [fulfillRandomWords function](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L108) to fulfill your consumer contract request.
+1. Call the VRFCoordinatorV2Mock [fulfillRandomWords function](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol#L108) to fulfill your consumer contract request.
 
 ## Testing
 
diff --git a/src/content/vrf/v2/subscription/index.mdx b/src/content/vrf/v2/subscription/index.mdx
index 4f117df053d..6aa1358befb 100644
--- a/src/content/vrf/v2/subscription/index.mdx
+++ b/src/content/vrf/v2/subscription/index.mdx
@@ -64,18 +64,18 @@ Two types of accounts exist in the Ethereum ecosystem, and both are used in VRF:
 
 The Chainlink VRF v2 solution uses both offchain and onchain components:
 
-- [VRF v2 Coordinator (onchain component)](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol): A contract designed to interact with the VRF service. It emits an event when a request for randomness is made, and then verifies the random number and proof of how it was generated by the VRF service.
+- [VRF v2 Coordinator (onchain component)](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol): A contract designed to interact with the VRF service. It emits an event when a request for randomness is made, and then verifies the random number and proof of how it was generated by the VRF service.
 - VRF service (offchain component): Listens for requests by subscribing to the VRF Coordinator event logs and calculates a random number based on the block hash and nonce. The VRF service then sends a transaction to the `VRFCoordinator` including the random number and a proof of how it was generated.
 
 ### Set up your contract and request
 
 Set up your consuming contract:
 
-1. Your contract must inherit [VRFConsumerBaseV2](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol).
+1. Your contract must inherit [VRFConsumerBaseV2](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol).
 
 1. Your contract must implement the `fulfillRandomWords` function, which is the _callback VRF function_. Here, you add logic to handle the random values after they are returned to your contract.
 
-1. Submit your VRF request by calling `requestRandomWords` of the [VRF Coordinator](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol). Include the following parameters in your request:
+1. Submit your VRF request by calling `requestRandomWords` of the [VRF Coordinator](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol). Include the following parameters in your request:
 
    - `keyHash`: Identifier that maps to a job and a private key on the VRF service and that represents a specified gas lane. If your request is urgent, specify a gas lane with a higher gas price limit. The configuration for your network can be found [here](/vrf/v2/subscription/supported-networks/#configurations).
    - `s_subscriptionId`: The subscription ID that the consuming contract is registered to. LINK funds are deducted from this subscription.
diff --git a/src/content/vrf/v2/subscription/migration-from-v1.mdx b/src/content/vrf/v2/subscription/migration-from-v1.mdx
index 02a580b8208..eadb1cbd8ec 100644
--- a/src/content/vrf/v2/subscription/migration-from-v1.mdx
+++ b/src/content/vrf/v2/subscription/migration-from-v1.mdx
@@ -38,9 +38,9 @@ To modify your existing smart contract code to work with VRF v2, complete the fo
      <a href="https://vrf.chain.link">Open the Subscription Manager</a>
    </div>
 
-1. Import the new [`VRFConsumerBaseV2.sol` contract](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol) and remove the v1 `VRFConsumerBase.sol` import. This contract includes the `fulfillRandomWords` function.
+1. Import the new [`VRFConsumerBaseV2.sol` contract](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/VRFConsumerBaseV2.sol) and remove the v1 `VRFConsumerBase.sol` import. This contract includes the `fulfillRandomWords` function.
 
-1. Import the [`VRFCoordinatorV2Interface.sol` interface](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/interfaces/VRFCoordinatorV2Interface.sol). This interface includes the new `requestRandomWords` function.
+1. Import the [`VRFCoordinatorV2Interface.sol` interface](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/vrf/interfaces/VRFCoordinatorV2Interface.sol). This interface includes the new `requestRandomWords` function.
 
 1. Add a `VRFConsumerBaseV2` constructor as shown in the [Get a Random Number](/vrf/v2/subscription/examples/get-a-random-number) example.
 
diff --git a/src/features/chainlink-automation/common/iLogAutomation.mdx b/src/features/chainlink-automation/common/iLogAutomation.mdx
index 93ea9fa611c..74b075b5756 100644
--- a/src/features/chainlink-automation/common/iLogAutomation.mdx
+++ b/src/features/chainlink-automation/common/iLogAutomation.mdx
@@ -1,6 +1,6 @@
 import { CodeSample } from "@components"
 
-To use log triggers, you will need to implement the [`ILogAutomation.sol`](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.8/automation/interfaces/ILogAutomation.sol) interface in your smart contract. Click on the functions below to understand the parameters:
+To use log triggers, you will need to implement the [`ILogAutomation.sol`](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/automation/interfaces/ILogAutomation.sol) interface in your smart contract. Click on the functions below to understand the parameters:
 
 | Function Name   | Description                                                                           |
 | --------------- | ------------------------------------------------------------------------------------- |
diff --git a/src/features/chainlink-functions/common/AutomatedFunctionsConsumer.mdx b/src/features/chainlink-functions/common/AutomatedFunctionsConsumer.mdx
index 25ec09ee483..f0aa30463ca 100644
--- a/src/features/chainlink-functions/common/AutomatedFunctionsConsumer.mdx
+++ b/src/features/chainlink-functions/common/AutomatedFunctionsConsumer.mdx
@@ -2,7 +2,7 @@ import { CodeSample } from "@components"
 
 <CodeSample src="samples/ChainlinkFunctions/AutomatedFunctionsConsumerExample.sol" />
 
-- To write an automated Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/FunctionsClient.sol). You can read the API reference of [FunctionsClient](/chainlink-functions/api-reference/functions-client).
+- To write an automated Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/FunctionsClient.sol). You can read the API reference of [FunctionsClient](/chainlink-functions/api-reference/functions-client).
 
   The contract is available in an NPM package, so you can import it from within your project.
 
diff --git a/src/features/chainlink-functions/common/CustomAutomatedFunctionsConsumer.mdx b/src/features/chainlink-functions/common/CustomAutomatedFunctionsConsumer.mdx
index 2d247d9b3e1..d047e66ddd8 100644
--- a/src/features/chainlink-functions/common/CustomAutomatedFunctionsConsumer.mdx
+++ b/src/features/chainlink-functions/common/CustomAutomatedFunctionsConsumer.mdx
@@ -2,7 +2,7 @@ import { CodeSample } from "@components"
 
 <CodeSample src="samples/ChainlinkFunctions/CustomAutomatedFunctionsConsumerExample.sol" />
 
-- To write an automated Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/FunctionsClient.sol). You can read the API reference of [FunctionsClient](/chainlink-functions/api-reference/functions-client).
+- To write an automated Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/FunctionsClient.sol). You can read the API reference of [FunctionsClient](/chainlink-functions/api-reference/functions-client).
 
   The contract is available in an NPM package, so you can import it from within your project.
 
diff --git a/src/features/chainlink-functions/common/FunctionsConsumer.mdx b/src/features/chainlink-functions/common/FunctionsConsumer.mdx
index 22b38a2d95f..916d345b827 100644
--- a/src/features/chainlink-functions/common/FunctionsConsumer.mdx
+++ b/src/features/chainlink-functions/common/FunctionsConsumer.mdx
@@ -2,7 +2,7 @@ import { CodeSample } from "@components"
 
 <CodeSample src="samples/ChainlinkFunctions/FunctionsConsumerExample.sol" />
 
-- To write a Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/FunctionsClient.sol) and [FunctionsRequest.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/dev/1_0_0/libraries/FunctionsRequest.sol). You can read the API references: [FunctionsClient](/chainlink-functions/api-reference/functions-client) and [FunctionsRequest](/chainlink-functions/api-reference/functions-request).
+- To write a Chainlink Functions consumer contract, your contract must import [FunctionsClient.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/FunctionsClient.sol) and [FunctionsRequest.sol](https://github.com/smartcontractkit/chainlink/blob/master/contracts/src/v0.8/functions/v1_0_0/libraries/FunctionsRequest.sol). You can read the API references: [FunctionsClient](/chainlink-functions/api-reference/functions-client) and [FunctionsRequest](/chainlink-functions/api-reference/functions-request).
 
   These contracts are available in an NPM package, so you can import them from within your project.
 
diff --git a/src/scripts/link-check/ignoredfiles-external.txt b/src/scripts/link-check/ignoredfiles-external.txt
index 80da3c6a78b..9cd28da24bf 100644
--- a/src/scripts/link-check/ignoredfiles-external.txt
+++ b/src/scripts/link-check/ignoredfiles-external.txt
@@ -4,7 +4,19 @@ _astro\/.*.css$
 
 # skip 403
 https://faucet.polygon.technology/
-https://faucet.polygon.technology/
+https://faucet.polygon.technology
 https://infura.io/
+https://infura.io
 https://www.infura.io/ 
 https://goerlifaucet.com/
+https://www.coingecko.com/en/api/documentation
+https://metamask.zendesk.com/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key
+https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key
+https://support.metamask.io/hc/en-us/articles/360015289452-How-to-create-an-additional-account-in-your-wallet
+https://support.metamask.io/hc/en-us/articles/360015289452-How-to-add-accounts-in-your-wallet
+https://support.metamask.io/hc/en-us/articles/360015489031-How-to-display-tokens-in-MetaMask
+https://support.metamask.io/hc/en-us/articles/360015489031#h_01FWH492CHY60HWPC28RW0872H
+https://support.metamask.io/hc/en-us/articles/360015489331-How-to-import-an-account
+https://support.metamask.io/hc/en-us/articles/360022895972
+https://support.metamask.io/hc/en-us/articles/360043227612-How-to-add-a-custom-network-RPC#h_01G63GGJ83DGDRCS2ZWXM37CV5
+https://help.phantom.app/hc/en-us/articles/4406527601811-How-to-migrate-from-Sollet
\ No newline at end of file