Site health improvements - january report

builders/ethereum/dev-env/scaffold-eth.md

@@ -267,7 +267,7 @@ yarn start
 
 --8<-- 'code/builders/ethereum/dev-env/scaffold-eth/terminal/start.md'
 
-This will launch the React-based DApp frontend at [http://localhost:3000/](http://localhost:3000){target=\_blank} by default. You can then point your browser to [http://localhost:3000/](http://localhost:3000){target=\_blank} and interact with the React frontend by connecting your wallet or checking out the contract debugger page.
+This will launch the React-based DApp frontend at `http://localhost:3000/` by default. You can then point your browser to `http://localhost:3000/` and interact with the React frontend by connecting your wallet or checking out the contract debugger page.
 
 ![The frontend of the DApp on the browser.](/images/builders/ethereum/dev-env/scaffold-eth/new/scaffold-eth-1.webp)
 

builders/integrations/.pages

@@ -2,7 +2,6 @@ title: Integrate
 nav:
   - index.md
   - analytics
-  - gaming
   - indexers
   - oracles
   - wallets

builders/integrations/indexers/subquery.md

@@ -31,7 +31,7 @@ Later on in this guide, you have the option of deploying your project to a local
 
 To get started, you'll need to [create a SubQuery project](https://academy.subquery.network/quickstart/quickstart.html){target=\_blank}:
 
-1. Globally install the [SubQuery CLI](https://academy.subquery.network/run_publish/cli.html){target=\_blank}:
+1. Globally install the [SubQuery CLI](https://academy.subquery.network/indexer/quickstart/quickstart.html#_1-install-the-subquery-cli){target=\_blank}:
 
     === "npm"
 
@@ -45,6 +45,9 @@ To get started, you'll need to [create a SubQuery project](https://academy.subqu
         yarn global add @subql/cli
         ```    
 
+!!! note
+    Using yarn to install `@subql/cli` is discouraged due to its poor dependency management, which can result in various errors.
+
 2. Initialize your SubQuery project using the following command:
 
     ```bash
@@ -368,13 +371,13 @@ To run your indexer locally using Docker, you can take the following steps:
 
     ![The terminal output after starting up the Docker container for your project.](/images/builders/integrations/indexers/subquery/new/subquery-7.webp)
 
-3. Head to [localhost:3000](http://localhost:3000){target=\_blank} to open the GraphQL playground and submit queries. You can open up the **DOCS** or **SCHEMA** tab on the playground as a reference when creating your queries
+3. Head to `http://localhost:3000` to open the GraphQL playground and submit queries. You can open up the **DOCS** or **SCHEMA** tab on the playground as a reference when creating your queries
 
     !!! note
         It may take a few minutes before the GraphQL server is ready. You'll be able to access the playground after you see the following log:
 
         ```bash
-        substrate-demo-graphql-engine-1  | <subql-query> INFO Started playground at http://localhost:3000 
+        substrate-demo-graphql-engine-1  | <subql-query> INFO Started playground at `http://localhost:3000`
         ```
 
     ![The GraphQL playground in the browser.](/images/builders/integrations/indexers/subquery/new/subquery-8.webp)

builders/integrations/oracles/chainlink.md

@@ -405,7 +405,7 @@ To get started with your own setup, including your own client contract, oracle c
 
 If you [created a job to be used with any API](/node-operators/oracle-nodes/node-chainlink/#using-any-api){target=\_blank}, you can then create a client contract that sets the API endpoint URL to perform the GET request on.
 
-Note that the client contract must have a LINK tokens balance to be able to pay for requests. Therefore, you will need to set the LINK value to zero in your `ChainlinkClient.sol` contract. You'll also need to make sure that your oracle node has a `MINIMUM_CONTRACT_PAYMENT` of `0`. You can verify that it has been set to zero by checking out the [**Configuration** section of your node](http://localhost:6688/config){target=\_blank}.
+Note that the client contract must have a LINK tokens balance to be able to pay for requests. Therefore, you will need to set the LINK value to zero in your `ChainlinkClient.sol` contract. You'll also need to make sure that your oracle node has a `MINIMUM_CONTRACT_PAYMENT` of `0`. You can verify that it has been set to zero by checking out the **Configuration** section of your node at `http://localhost:6688/config`.
 
 The following client contract is an example of how to use any API from within your client contract:
 
@@ -476,6 +476,6 @@ contract Client is ChainlinkClient {
 !!! note
     The above example uses the pre-deployed LINK token contract address. You also have the option of deploying your own LINK token contract and using that instead.
 
-Once you've deployed the contract on Remix, you can begin to request the volume data. After you make a request, you can check the status of the job by going to the [**Jobs** section of your node](http://localhost:6688/jobs){target=\_blank}.
+Once you've deployed the contract on Remix, you can begin to request the volume data. After you make a request, After you make a request, you can check the job status under the **Jobs** section on your node at `http://localhost:6688/jobs`.
 
 --8<-- 'text/_disclaimers/third-party-content.md'

builders/integrations/wallets/rainbowkit.md

@@ -43,7 +43,7 @@ The script will prompt you for a project name, generate a new directory with the
 
 --8<-- 'code/builders/integrations/wallets/rainbowkit/terminal/cli-quickstart.md'
 
-You can now navigate to the project directory, start the development server, and navigate to [http://localhost:3000](http://localhost:3000){target=\_blank} to view your project locally:
+You can now navigate to the project directory, start the development server, and navigate to `http://localhost:3000` to view your project locally:
 
 === "npm"
 
@@ -168,7 +168,7 @@ Next, start the development server to create a local dApp instance:
     yarn dev
     ```
 
-If you navigate to [http://localhost:3000](http://localhost:3000){target=\_blank},  you should see the starter Next.js application in your browser.
+If you navigate to `http://localhost:3000`,  you should see the starter Next.js application in your browser.
 
 To test the RainbowKit connection, you will use the MetaMask mobile app. To follow this guide, you must have established a connection to the Moonbase Alpha TestNet on the MetaMask mobile app.
 

node-operators/oracle-nodes/node-chainlink.md

@@ -147,7 +147,7 @@ docker logs --tail 50 {INSERT_CONTAINER_ID} #Logs progressing
 
 With the oracle node running, you can start to configure the smart contract side of things. First, you'll need to fund the oracle node by taking the following steps:
 
-1. Retrieve the address that the oracle node will use to send transactions and write data on-chain by logging into the [ChainLink node's UI](http://localhost:6688){target=\_blank} (located at `http://localhost:6688/`). You'll need to use the credentials from the `.api` file
+1. Retrieve the address that the oracle node will use to send transactions and write data on-chain by logging into the Chainlink node's UI (located at `http://localhost:6688/`). You'll need to use the credentials from the `.api` file
 
     ![Chainlink login](/images/node-operators/oracle-nodes/chainlink/chainlink-node-2.webp)
 
@@ -194,7 +194,7 @@ The last step to have a fully configured Chainlink oracle is to create a job. Re
 
 Seeing an oracle as an API service, a job here would be one of the functions that you can call and that will return a result. To get started creating your first job, take the following steps:
 
-1. Go to the [Jobs sections of your node](http://localhost:6688/jobs){target=\_blank}
+1. Go to the **Jobs** sections of your node at `http://localhost:6688/jobs`
 2. Click on **New Job**
 
 ![Chainlink oracle New Job](/images/node-operators/oracle-nodes/chainlink/chainlink-node-6.webp)

tutorials/eth-api/how-to-build-a-dapp.md

@@ -327,7 +327,7 @@ npm run start
 !!! note
     At this point, you may see a couple compilation warnings, but as we continue to build the DApp, we'll make changes that will resolve the warnings.
 
-Your frontend will be available at [localhost:3000](http://localhost:3000){target=\_blank}.
+Your frontend will be available at `http://localhost:3000`.
 
 At this point, our frontend project is set up well enough to start working on the functional code!  
 

tutorials/integrations/local-subsquid.md

@@ -442,7 +442,7 @@ To query your squid, open up a new terminal window within your project and run t
 sqd serve
 ```
 
-And that's it! You can now run queries against your Squid on the GraphQL playground at [http://localhost:4350/graphql](http://localhost:4350/graphql){target=\_blank}. Try crafting your own GraphQL query, or use the below one:
+And that's it! You can now run queries against your Squid on the GraphQL playground at `http://localhost:4350/graphql`. Try crafting your own GraphQL query, or use the below one:
 
 ???+ code "Sample query"
 

tutorials/integrations/nft-subsquid.md

@@ -187,7 +187,7 @@ Finally, in a separate terminal window, launch the GraphQL server:
 sqd serve
 ```
 
-Visit [`localhost:4350/graphql`](http://localhost:4350/graphql){target=\_blank} to access the [GraphiQL](https://github.com/graphql/graphiql){target=\_blank} console. From this window, you can perform queries such as this one to fetch a batch of owners:
+Visit `http://localhost:4350/graphql` to access the [GraphiQL](https://github.com/graphql/graphiql){target=\_blank} console. From this window, you can perform queries such as this one to fetch a batch of owners:
 
 ```graphql
 query MyQuery {