Fix dead links in docs (#4312)

michellewong793 · web-flow · commit 6ae3a232fc4a · 2020-02-04T15:55:50.000-08:00
* fix dead links in docs

* Make links not be hardcoded
diff --git a/frontend/website/pages/docs/developers/code-reviews.mdx b/frontend/website/pages/docs/developers/code-reviews.mdx
@@ -11,7 +11,7 @@ A good pull request:
 
 ## OCaml things
 
-- Are the [style guidelines](../style-guide) being followed?
+- Are the [style guidelines](./style-guide) being followed?
 - Do the signatures make sense? Are they minimal and reusable?
 - Does anything need to be functored over?
 - Are there any error cases that aren't handled correctly?
diff --git a/frontend/website/pages/docs/faq.mdx b/frontend/website/pages/docs/faq.mdx
@@ -11,7 +11,7 @@ Currently, a 4-core processor and 8 GB of RAM are the minimum requirements.  In
 
 #### What about software?
 
-You can download all the software required to run a Coda node [here](https://codaprotocol.com/docs/getting-started/#installation). Right now, we have builds that work on MacOS, as well as Debian and Ubuntu. You can also [build from source](https://github.com/codaprotocol/coda).
+You can download all the software required to run a Coda node [here](./getting-started/#installation). Right now, we have builds that work on MacOS, as well as Debian and Ubuntu. You can also [build from source](https://github.com/codaprotocol/coda).
 
 #### What can I do on the Coda network?
 
diff --git a/frontend/website/pages/docs/my-first-transaction.mdx b/frontend/website/pages/docs/my-first-transaction.mdx
@@ -3,7 +3,7 @@ export default Page({title: "My First Transaction"});
 
 # My First Transaction
 
-In this section, we'll make our first transaction on the Coda network. After [installing the software](../getting-started), we'll need to create a new account before we can send or receive coda. Let's first start up the node so that we can start issuing commands.
+In this section, we'll make our first transaction on the Coda network. After [installing the software](./getting-started), we'll need to create a new account before we can send or receive coda. Let's first start up the node so that we can start issuing commands.
 
 ## Start up a node
 
@@ -19,6 +19,7 @@ The host and port specified above refer to the seed peer address - this is the i
 
 If you forwarded custom ports (other than 8302 and 8303), you'll need to replace the default ports above with the ones you forwarded.
 
+
 <Alert>
 
   The daemon process needs to be running whenever you issue commands from `coda client`, so make sure you don't kill it by accident.
diff --git a/frontend/website/pages/docs/node-operator.mdx b/frontend/website/pages/docs/node-operator.mdx
@@ -132,4 +132,4 @@ When you [start the daemon](/docs/my-first-transaction/#start-up-a-node), set th
 
 As a snark-worker, you get to share some of the block reward for each block your compressed transactions make it in to. The block producer is responsible for gathering compressed transactions before including them into a block, and will be incentivized by the protocol to reward snark-workers.
 
-That about covers the roles and responsibilities as a Code node operator. Since Coda is a permissionless peer-to-peer network, everything is managed and run in a decentralized manner by nodes all over the world. Similarly, the Coda project is also distributed and permissionless to join. The code is all open source, and there is much work to be done, both technical and non-technical. To learn more about how you can get involved with Coda, please check out the [Contributing to Coda section](../contributing).
+That about covers the roles and responsibilities as a Code node operator. Since Coda is a permissionless peer-to-peer network, everything is managed and run in a decentralized manner by nodes all over the world. Similarly, the Coda project is also distributed and permissionless to join. The code is all open source, and there is much work to be done, both technical and non-technical. To learn more about how you can get involved with Coda, please check out the [Contributing to Coda section](./contributing).
diff --git a/frontend/website/pages/docs/snarks/index.mdx b/frontend/website/pages/docs/snarks/index.mdx
@@ -7,7 +7,7 @@ SNARKs are a powerful cryptographic tool that enable applications
 that give users unprecedented levels of oversight and privacy.
 They are also a key-ingredient in building scalable decentralized systems like Coda.
 
-For a high-level overview, check out [this blogpost](https://codaprotocol.com/blog/zkp-guide.html).
+For a high-level overview, check out [this blogpost](/blog/zero-knowledge-proofs-an-intuitive-explanation).
 
 **snarky** is a domain specific language for using SNARKs.
 This section is intended to be a guide on how to get started using SNARKs in

Original file line number	Diff line number	Diff line change
`@@ -132,4 +132,4 @@ When you [start the daemon](/docs/my-first-transaction/#start-up-a-node), set th`
`132`	`132`
`133`	`133`	`As a snark-worker, you get to share some of the block reward for each block your compressed transactions make it in to. The block producer is responsible for gathering compressed transactions before including them into a block, and will be incentivized by the protocol to reward snark-workers.`
`134`	`134`
`135`		-That about covers the roles and responsibilities as a Code node operator. Since Coda is a permissionless peer-to-peer network, everything is managed and run in a decentralized manner by nodes all over the world. Similarly, the Coda project is also distributed and permissionless to join. The code is all open source, and there is much work to be done, both technical and non-technical. To learn more about how you can get involved with Coda, please check out the [Contributing to Coda section](../contributing).
	`135`	+That about covers the roles and responsibilities as a Code node operator. Since Coda is a permissionless peer-to-peer network, everything is managed and run in a decentralized manner by nodes all over the world. Similarly, the Coda project is also distributed and permissionless to join. The code is all open source, and there is much work to be done, both technical and non-technical. To learn more about how you can get involved with Coda, please check out the [Contributing to Coda section](./contributing).