fix: fixed broken links from site migration

ar-io · Mar 6, 2024 · 2e691d2 · 2e691d2
1 parent 87ac17d
commit 2e691d2
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 12 deletions.
diff --git a/docs/src/gateways/ar-io-node/advanced-config.md b/docs/src/gateways/ar-io-node/advanced-config.md
@@ -32,7 +32,7 @@ View examples of the admin endpoints [here](./admin/admin-api.md)
 
 ## Wallet Association
 
-In order to participate in the greater [ar.io network](/../), Gateway nodes need to associate themselves with an Arweave wallet. This can be configured by setting the `AR_IO_WALLET` key value in your `.env` file.
+In order to participate in the greater [ar.io network](https://ar.io), Gateway nodes need to associate themselves with an Arweave wallet. This can be configured by setting the `AR_IO_WALLET` key value in your `.env` file.
 
 ```
 AR_IO_WALLET=1seRanklLU_1VTGowDZdD7s_-7k1qowT6oeFZHUZiZo

diff --git a/docs/src/gateways/ar-io-node/linux-setup.md b/docs/src/gateways/ar-io-node/linux-setup.md
@@ -180,7 +180,7 @@ These packages are not required to run a node in its basic form. However, they w
   - `AR_IO_WALLET` is optional, and sets the wallet you want associated with your Gateway. An associated wallet is required to join the AR.IO network.
   - `OBSERVER_WALLET` is the public address of the wallet used to sign Observer transactions. This is required for Observer to run, but may be omitted if you are running a gateway outside of the AR.IO network and do not plan to run Observer. You will need to supply the keyfile to this wallet in the next step.
 
-  Advanced configuration options can be found at [ar.io/docs](https://ar.io/docs/gateways/ar-io-node/advanced-config.html)
+  Advanced configuration options can be found at [docs.ar.io](https://docs.ar.io/gateways/ar-io-node/advanced-config.html)
 
 - Supply Your Observer Wallet Keyfile:
 

diff --git a/docs/src/gateways/ar-io-node/testnet.md b/docs/src/gateways/ar-io-node/testnet.md
@@ -10,22 +10,22 @@ tags: [testnet, join, application, jwk, qty, fqdn, label, note, properties]
 
 1. Must have a fully functional AR.IO gateway.
     - This includes the ability to resolve ArNS subdomains.
-    - Follow installation instructions for [windows](/gateways/ar-io-node/windows-setup) or [linux](/gateways/ar-io-node/linux-setup) and get help from the [AR.IO community](https://discord.gg/7zUPfN4D6g).
+    - Follow installation instructions for [windows](/gateways/ar-io-node/windows-setup) or [linux](/gateways/ar-io-node/linux-setup) and get help from the [ar.io community](https://discord.gg/7zUPfN4D6g).
 
 2. Gateway must be associated with an Arweave Wallet.
-    - Learn about creating Arweave wallets [here](/../wallet)
+    - Learn about creating Arweave wallets [here](https://ar.io/wallet)
 
 3. Arweave wallet must be funded with enough AR tokens to pay for transaction gas.
 
 ## Submit an Application
 
-Joining the AR.IO Testnet requires staking a minimum of 10,000 Test IO Tokens. You must have Test IO Tokens before you are able to join. Test IO Tokens are currently distributed through an application system in the [AR.IO Discord](https://discord.gg/7zUPfN4D6g).
+Joining the ar.io Testnet requires staking a minimum of 10,000 Test IO Tokens. You must have Test IO Tokens before you are able to join. Test IO Tokens are currently distributed through an application system in the [ar.io Discord](https://discord.gg/7zUPfN4D6g).
 
-New applications for joining the Testnet are not currently being accepted. Be sure to join the [AR.IO Discord](https://discord.com/invite/7zUPfN4D6g) to stay up to date on Testnet status and possible future availability prior to the launch of the Mainnet.
+New applications for joining the Testnet are not currently being accepted. Be sure to join the [ar.io Discord](https://discord.com/invite/7zUPfN4D6g) to stay up to date on Testnet status and possible future availability prior to the launch of the Mainnet.
 
 ## Setting up and Running the Join Script
 
-Joining the AR.IO Testnet is currently completed by manually running a script. The process for doing so is as follows:
+Joining the ar.io Testnet is currently completed by manually running a script. The process for doing so is as follows:
 
 ### Clone the Repo
 
@@ -54,7 +54,7 @@ Joining the testnet requires signing and funding a transaction that interacts wi
 
 You will need to provide some information specific to your gateway before running the join script. You can do this by opening the script file in any code or text editor. The file is located at `testnet-contract > tools > join-network.ts`
 
-Each line that needs to be edited begins with "const", followed by a variable name, and "=" sign, and its value. Each line is accompanied by a note to inform you of its purpose. The following variables MUST be changed in order to successfully join the AR.IO Testnet:
+Each line that needs to be edited begins with "const", followed by a variable name, and "=" sign, and its value. Each line is accompanied by a note to inform you of its purpose. The following variables MUST be changed in order to successfully join the ar.io Testnet:
 
 - **qty**: Quantity of Test IO Tokens to stake to join the Testnet. This value must be at least 10,000, and not greater than the number of Test IO tokens in your wallet.
 - **label**: A friendly label for your Gateway. There currently a 16 character limit for this value.
@@ -78,7 +78,7 @@ Once you have Test IO Tokens and all of your settings configured properly, it's
 yarn ts-node tools/join-network.ts
 ```
 
-This will create an Arweave transaction interacting with the Testnet Smartweave contract, so it will require AR tokens to pay for gas. AR.IO recommends having at least 0.05 AR to ensure a successful transaction.
+This will create an Arweave transaction interacting with the Testnet Smartweave contract, so it will require AR tokens to pay for gas. ar.io recommends having at least 0.05 AR to ensure a successful transaction.
 
 
 

diff --git a/docs/src/gateways/ar-io-node/windows-setup.md b/docs/src/gateways/ar-io-node/windows-setup.md
@@ -85,12 +85,10 @@ Before starting the installation process, ensure you have the following:
      - `AR_IO_WALLET` is optional, and sets the wallet you want associated with your Gateway. An associated wallet is required to join the AR.IO network.
      - `OBSERVER_WALLET` is the public address of the wallet used to sign Observer transactions. This is required for Observer to run, but may be omitted if you are running a gateway outside of the AR.IO network and do not plan to run Observer. You will need to supply the keyfile to this wallet in the next step.
 
-    Advanced configuration options can be found at [ar.io/docs](https://ar.io/docs/gateways/ar-io-node/advanced-config.html)
+    Advanced configuration options can be found at [docs.ar.io](https://docs.ar.io/gateways/ar-io-node/advanced-config.html)
 
    - Save the file with the name ".env" and make sure to select "All Files" as the file type. This helps to ensure the file saves as ".env" and not ".env.txt"
 
-     Advanced configuration options can be found at [ar.io/docs](https://ar.io/docs/gateways/ar-io-node/advanced-config.html)
-
    **Note**: The `.env` file should be saved inside the same directory where you cloned the repository (e.g., `ar-io-node`).
 
 ## Supply Your Observer Wallet Keyfile: