Integrate cargo-linkcheck and fix broken links.

.github/workflows/merge-acceptance.yaml

@@ -10,10 +10,13 @@ jobs:
       uses: ts-graphviz/setup-graphviz@v1
     - uses: taiki-e/cache-cargo-install-action@v1
       with:
-        tool: mdbook@0.4.29
+        tool: mdbook@0.4.35
     - uses: taiki-e/cache-cargo-install-action@v1
       with:
         tool: mdbook-graphviz@0.1.6
+    - uses: taiki-e/cache-cargo-install-action@v1
+      with:
+        tool: mdbook-linkcheck@0.7.7
     - uses: actions/checkout@v3
     - run: mdbook build
     - name: Check for Orphaned Files

.github/workflows/render-site.yaml

@@ -21,10 +21,13 @@ jobs:
       uses: ts-graphviz/setup-graphviz@v1
     - uses: taiki-e/cache-cargo-install-action@v1
       with:
-        tool: mdbook@0.4.29
+        tool: mdbook@0.4.35
     - uses: taiki-e/cache-cargo-install-action@v1
       with:
         tool: mdbook-graphviz@0.1.6
+    - uses: taiki-e/cache-cargo-install-action@v1
+      with:
+        tool: mdbook-linkcheck@0.7.7
 
     # Now get the user content:
     - uses: actions/checkout@v3

README.md

@@ -18,6 +18,7 @@ There are two github CI workflows:
 
 - `cargo install mdbook`
 - `cargo install mdbook-graphviz`
+- `cargo install mdbook-linkcheck`
 
 ### Other prerequisites
 

book.toml

@@ -12,6 +12,8 @@ build-dir = "./docs"
 [output.html]
 default-theme = "light"
 
+[output.linkcheck]
+
 [preprocessor.graphviz]
 command = "mdbook-graphviz"
 after = ["links"]

src/introduction/a-path-to-pos-zcash.md

@@ -1,6 +1,6 @@
 # A Path to Proof-of-Stake Zcash
 
-The [TFL](./terminology.md#definition-tfl) design provides a possible first step in transitioning [Zcash](https://z.cash) to a [PoS](./terminology.md#definition-pos) protocol. Here we describe how a transition to PoS relates to "the Zcash roadmap" and how TFL fits into one approach to a PoS transition.
+The [TFL](../terminology.md#definition-tfl) design provides a possible first step in transitioning [Zcash](https://z.cash) to a [PoS](../terminology.md#definition-pos) protocol. Here we describe how a transition to PoS relates to "the Zcash roadmap" and how TFL fits into one approach to a PoS transition.
 
 ## The Zcash Tech-Tree
 
@@ -23,7 +23,7 @@ After this transition to pure PoS, there are likely to be future improvements to
 
 Our primary motivation for proposing (at least) two steps is to minimize disruption to usability, safety, security, and the ecosystem during each step.
 
-With this approach, the Zcash Tech Tree with the [TFL](./terminology.md#definition-tfl) approach might look something like this:
+With this approach, the Zcash Tech Tree with the [TFL](../terminology.md#definition-tfl) approach might look something like this:
 
 ```dot process
 {{#include ../diagrams/zcash-tech-tree-tfl-steps.dot}}

src/introduction/status-and-next-steps.md

@@ -46,4 +46,4 @@ This design proposal is being developed by [Electric Coin Company](https://elect
 
 The fine-grained day-to-day goals and tasks for this project are present in [the Zcash Developers Hub](https://zcash.github.io/developers) in the [TFL-focused DAG](https://zcash.github.io/developers/zcash-tfl-dag).
 
-Please also see [Getting Involved](./getting-involved.md) if you are interested in tracking this progress more closely, or in contributing.
+Please also see [Get Involved](./get-involved.md) if you are interested in tracking this progress more closely, or in contributing.

src/overview.md

@@ -10,5 +10,5 @@ The integration of the current PoW consensus with the TFL produces a new top-lev
 
 In the following subchapters we introduce the [Design at a Glance](./overview/design-at-a-glance.md), then provide an overview of the major components of the design.
 
-Following this overview chapter, we proceed into a detailed [Protocol Specification](./protocol-specification.md).
+Following this overview chapter, we proceed into a detailed [Protocol Specification (TODO)]().