Random link fixes (ipfs#1382)

ElPaisano · web-flow · commit ff1ab453b81c · 2022-12-19T16:43:23.000-07:00
diff --git a/docs/concepts/case-study-snapshot.md b/docs/concepts/case-study-snapshot.md
@@ -93,7 +93,7 @@ These voting systems are used to calculate the results of a vote based on the vo
 
 ## How Snapshot uses IPFS
 
-Snapshot uses IPFS to make the whole voting process fully transparent and auditable. Every space, proposal, vote, and user action is added to IPFS and has a [content identifier (CID)](/concepts/content-addressing.md).
+Snapshot uses IPFS to make the whole voting process fully transparent and auditable. Every space, proposal, vote, and user action is added to IPFS and has a [content identifier (CID)](../concepts/content-addressing.md).
 
 Additionally, the Snapshot UI is also [available on IPFS](https://bafybeihzjoqahhgrhnsksyfubnlmjvkt66aliodeicywwtofodeuo2icde.ipfs.dweb.link/) and linked using the ENS name `shot.eth` which is accessible via any ENS resolution service, e.g. [shot.eth.limo](https://shot.eth.limo/)(see the `x-ipfs-path` and `X-Ipfs-Roots` headers when making an HTTP request.)
 
@@ -115,7 +115,7 @@ pineapple.js exposes a `pin` method that takes a JSON object and sends it to the
 
 ### Open access via IPFS Gateways
 
-After data is added to the IPFS network via pinning services, it is also made available for viewing by users via an [IPFS Gateway](/concepts/ipfs-gateway.md). Links to the signed messages for [proposals](https://snapshot.mypinata.cloud/ipfs/bafkreigva2y23hnepirhvup2widmawmjiih3kvvuaph3a7mrivkiqcvuki) and [votes](https://snapshot.mypinata.cloud/ipfs/bafkreibozdzgw5y5piburro6pxspw7yjcdaymj3fyqjl2rohsthnqfwc6e) are integrated into the Snapshot UI.
+After data is added to the IPFS network via pinning services, it is also made available for viewing by users via an [IPFS Gateway](../concepts/ipfs-gateway.md). Links to the signed messages for [proposals](https://snapshot.mypinata.cloud/ipfs/bafkreigva2y23hnepirhvup2widmawmjiih3kvvuaph3a7mrivkiqcvuki) and [votes](https://snapshot.mypinata.cloud/ipfs/bafkreibozdzgw5y5piburro6pxspw7yjcdaymj3fyqjl2rohsthnqfwc6e) are integrated into the Snapshot UI.
 
 ## IPFS benefits
 
diff --git a/docs/concepts/persistence.md b/docs/concepts/persistence.md
@@ -101,6 +101,6 @@ Options in this category include:
 - [Web3.Storage](https://Web3.Storage)
 - [NFT.storage](https://nft.storage/)
 - [Estuary](https://estuary.tech)
-- [Powergate](https://docs.filecoin.io/build/powergate)
+- [Powergate](https://docs.filecoin.io/build/tools/powergate/)
 - [ChainSafe Storage](https://storage.chainsafe.io)
 - [Fleek Storage](https://fleek.co/storage)
diff --git a/docs/how-to/create-simple-chat-app.md b/docs/how-to/create-simple-chat-app.md
@@ -5,7 +5,7 @@ description: "Learn how to deploy a minimal chat app entirely in the browser usi
 
 # Create a simple chat app
 
-This how-to demonstrates a minimal chat app in [js-ipfs](/reference/js/api.md#js-ipfs) entirely in the browser.
+This how-to demonstrates a minimal chat app in [js-ipfs](../reference/js/api.md#js-ipfs) entirely in the browser.
 
 Here’s a quick demo of the app:
 
@@ -32,7 +32,7 @@ To test and deploy your own version with your own nodes (recommended for deploym
 - [Advertising set up](#advertising) to let other peers know your users are there
 - [Publishing set up and staying connected](#communication) to peers
 
-Besides [IPFS](/concepts/what-is-ipfs.md) (with CIDv1) and JavaScript, our chat app uses these technologies:
+Besides [IPFS](../concepts/what-is-ipfs.md) (with CIDv1) and JavaScript, our chat app uses these technologies:
 
 - [Libp2p](https://libp2p.io/)’s [WebRTC](https://www.npmjs.com/package/libp2p-webrtc-star)-Star and [circuit relay](https://docs.libp2p.io/concepts/circuit-relay) for discovery and connecting (with two libraries:  [js-ipfs](https://github.com/ipfs/js-ipfs/blob/master/docs/BROWSERS.md),  Bootstrap–with minified CSS), and [Kubo](https://docs.ipfs.tech/reference/go/api/#working-with-go) for p2p circuit connecting with websockets,
 - some [Python code](#advertising) that we supply for advertising, and
diff --git a/docs/how-to/exchange-files-between-nodes.md b/docs/how-to/exchange-files-between-nodes.md
@@ -135,13 +135,15 @@ We'll need to bundle the dependencies to run the app. Let's do it:
 
 You should see something like this if all went well:
 
+<!-- markdown-link-check-disable -->  
 ```sh
 Starting up http-server, serving public
 Available on:
   http://127.0.0.1:12345
   http://192.168.2.92:12345
 Hit CTRL-C to stop the server
 ```
+<!-- markdown-link-check-enable-->
 
 Now go to http://127.0.0.1:12345 in a modern browser and you're on!
 
diff --git a/docs/how-to/websites-on-ipfs/link-a-domain.md b/docs/how-to/websites-on-ipfs/link-a-domain.md
@@ -125,7 +125,8 @@ Before we get started, you will need:
     a. Set the value to `dnslink=/ipfs/SITE_CID`, replacing `SITE_CID` with the CID of your website.
 1. Save your changes.
 
-You should now be able to visit your IPFS website at your Handshake domain! If your Handshake name is `yourname/`, you can visit your website at http://yourname/ (no dots, just yourname/!)
+You should now be able to visit your IPFS website at your Handshake domain! If your Handshake name is `yourname/`, you can visit your website at <!-- markdown-link-check-disable--> http://yourname/ 
+<!-- markdown-link-check-enable--> (no dots, just yourname/!)
 
 ### Subdomain
 
@@ -140,7 +141,9 @@ If you want to create your website on a subdomain rather than a bare TLD (e.g. `
    b. Set the value to `dnslink=/ipfs/SITE_CID`, replacing `SITE_CID` with the CID of your website.
 1. Save your changes.
 
-You should now be able to visit your IPFS website at your Handshake domain! If your Handshake name is `sub.yourname/`, you can visit your website at http://sub.yourname/
+You should now be able to visit your IPFS website at your Handshake domain! If your Handshake name is `sub.yourname/`, you can visit your website at
+<!-- markdown-link-check-disable--> http://sub.yourname/ 
+<!-- markdown-link-check-enable-->
 
 ::: tip
 If you prefer to use Handshake-powered DNSLink with your custom gateway, run [`ipfs daemon`](../../install/command-line.md) with config that has a Handshake resolver enabled for your domain: `ipfs config --json DNS.Resolvers '{ "yourname": "https://query.hdns.io/dns-query" }`. Learn how to run a self-hosted, site-specific DNSLink gateway from [gateway recipes in Kubo config docs](https://github.com/ipfs/kubo/blob/master/docs/config.md#gateway-recipes).
