Link fixes. Mostly resolves #23

docs/API/wallet-api.md

@@ -263,7 +263,7 @@ Using default settings this will generate a new address with:
 The newly generated address will be added to the `~/.qrl/walletd.json` file. This file will be created if it does not already exist.
 
 :::note
-Ensure the tree height is large enough for your needs and transfer all funds out of the address before all [OTS keys](build/fundamentals/ots-keys) are used!
+Ensure the tree height is large enough for your needs and transfer all funds out of the address before all [OTS keys](/build/fundamentals/ots-keys) are used!
 :::
 
 <Tabs
@@ -1981,7 +1981,7 @@ Send up to 80 bytes of message data onto the chain.
 Send message data onto the chain. Allows up to 80 Bytes of data to be sent onto the QRL blockchain.
 
 :::info Message Encoding
-For more information on the QRL Message Encoding please see the [Message documentation](build/messages)
+For more information on the QRL Message Encoding please see the [Message documentation](/use/tools/messages/overview)
 :::
 
 <Tabs
@@ -2900,7 +2900,7 @@ This method will transfer tokens held in a QRL Address in the local wallet. Usin
 :::note
 To find all addresses held by an address use the [QRL Block Explorer](https://explorer.theqrl.org) to look up the address and list all tokens held. 
 
-Additionally you can use another API to lookup the address details and tokens held by address. For instance the [GetTokensByAddresss Method](api/qrl-public-api#gettokensbyaddress) will return a list of tokens held by that address.
+Additionally you can use another API to lookup the address details and tokens held by address. For instance the [GetTokensByAddresss Method](/api/qrl-public-api#gettokensbyaddress) will return a list of tokens held by that address.
 :::
 
 :::info Requires token transaction hash

docs/Build/Address/slaves.md

@@ -31,7 +31,7 @@ Slave addresses are advanced and are not usually needed for most users!
 
 ## Overview
 
-A slave key is generated using the [QRL command line tools](use/node/node-cli/node-cli-slave-xmss) or via the API.
+A slave key is generated using the [QRL command line tools](/use/node/node-cli/node-cli-slave-xmss) or via the API.
 
 This process is similar to generating a QRL address and will output a slaves.json file which contains the private keys for each slave generated (Up to 100).
 

docs/Build/Fundamentals/qrl-emission.md

@@ -62,7 +62,7 @@ $b=Z_{t-1}-Z_t$
 
 The QRL emission schedule, or amount of quanta generated with each block mined, was updated in QIP-16 (*QRL Improvement Proposal*) through a public on-chain vote to reduce the total reward each block paid out by a factor of 60%. 
 
-You can read more about the [QIP process here](build/qip/overview), and review the history of this QIP in the GitHub repository.
+You can read more about the [QIP process here](/build/qip/overview), and review the history of this QIP in the GitHub repository.
 
 
 

docs/Tutorials/Node/mainnet-testnet-node.md

@@ -150,7 +150,7 @@ qrl --json --port_pub 19019 state
 From this output you can see the testnet node is running, the blockheight is different form the mainnet node running and the networkID is different.
 
 :::tip 
-Check the node blockHeight against the [QRL Testnet Explorer](https:testnet-explorer.theqrl.org)
+Check the node blockHeight against the [QRL Testnet Explorer](https://testnet-explorer.theqrl.org)
 :::
 
 ## Final Thoughts

docs/Use/Node/node-cli/node-cli-slave-xmss.md

@@ -22,13 +22,10 @@ slug: /use/node/node-cli/node-cli-slave-xmss
 
 The QRL wallet is an XMSS Merkle tree constructed using the private key to generate leaves. Each "leaf" can also generate a tree of OTS Slave keys that can be used to sign transactions. This allows further expansion of a QRL wallet extending the number of transactions you can process before needing to regenerate a new wallet.
 
-> To create a slaves.json file you will need a QRL wallet.json file and a working installation of QRL. See the guide for creating a [QRL CLII Wallet](use/node/node-cli/overview)
-{: .info}
+> To create a slaves.json file you will need a QRL wallet.json file and a working installation of QRL. See the guide for creating a [QRL CLI Wallet](/use/node/node-cli/overview)
 
 Currently the only way to generate a slaves.json file is by using the command line utility `qrl`. This can be installed by following the [QRL Node Guide](/use/node).  You will need to have shell access and be logged into the computer running qrl.
 
-
-
 ## Create a Slaves.json
 
 To generate a slaves.json file you will need to be connected to an active and synced node. This can be a local node, as well any of the peers shown in your nodes peer list. You also need a wallet to use for the slaves file.

docs/Use/Tools/notarize/notarization.md

@@ -31,7 +31,7 @@ Once notarized, any exact copy of that document can be cryptographically verifie
  ## Advanced users
 
 :::note
-There are multiple ways to access the notarization process through the [QRL API](/api) and [Command Line Tools](use/node/node-cli/overview) using the `message_tx` with appropriate [message encoding](/build/messages/message-tx-encoding).
+There are multiple ways to access the notarization process through the [QRL API](/api) and [Command Line Tools](/use/node/node-cli/overview) using the `message_tx` with appropriate [message encoding](/build/messages/message-tx-encoding).
 :::
 
 

docs/Use/Tools/notarize/verify-data.md

@@ -25,7 +25,7 @@ Use our Document Notarization guide to get started with on-chain quantum resista
 
 ## Document Verification
 
-Browse to the [QRL Block Explorer](https:explorer.theqrl.org) and lookup the transaction hash from the initial document notarization.
+Browse to the [QRL Block Explorer](https://explorer.theqrl.org) and lookup the transaction hash from the initial document notarization.
 
 You can either save the tx_hash from the original transaction or simply lookup the QRL address used to send the notarization.
 

docs/Use/Wallet/Ledger/new-wallet.md

@@ -19,7 +19,7 @@ slug: /use/wallet/ledger/new
 
 ## Installing the QRL App
 
-Using the [Ledger Live](https://www.ledger.com/pages/ledger-live) application, [follow these instructions](https://support.ledger.com/hc/en-us/articles/360019184453?support=true:
+Using the [Ledger Live](https://www.ledger.com/ledger-live) application, [follow these instructions](https://support.ledger.com/hc/en-us/articles/360019184453?support=true):
 
 1. Open the **Manager** in Ledger Live
 2. **Connect and Unlock** your Ledger Nano

docs/Use/Wallet/Ledger/open-ledger-wallet.md

@@ -39,5 +39,5 @@ Chrome users, there is a bug with chrome that will not allow the Ledger to work.
 :::
 
 :::info Firefox Connection Issues
-If you are a Firefox user, ensure you have enabled **u2f** before proceeding. [Enabling U2F support in Mozilla Firefox](https://support.yubico.com/support/solutions/articles/15000017511-enabling-u2f-support-in-mozilla-firefox)
+If you are a Firefox user, ensure you have enabled **u2f** before proceeding. [Enabling U2F support in Mozilla Firefox](https://www.key-id.com/enable-fido-u2f-firefox/)
 :::