Fix stray documentation links (#1656)

Author: jasagredo

CONTRIBUTING.md

@@ -28,8 +28,8 @@ We have two types of documentation:
 When starting to work on Consensus, we recommend to take a look at the following
 resources:
 
- - [Preflight guide](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/PreflightGuide/)
- - [Glossary](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/Glossary/)
+ - [Preflight guide](https://ouroboros-consensus.cardano.intersectmbo.org/docs/tutorials/preflight_guide/)
+ - [Glossary](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/glossary/)
 
 When adding or improving documentation about the implementation, it is
 preferable to add haddock comments since they are closer to the code. However
@@ -336,7 +336,7 @@ package, we should release it to CHaP instead (see the
 [CHaP README](https://github.com/IntersectMBO/cardano-haskell-packages)
 for more).
 
-In general, we strive to avoid having `source-repository-package`s on our `main` branch. However, there are situations where we want to prevent pull requests from piling up while awaiting the release of upstream components[^1]. 
+In general, we strive to avoid having `source-repository-package`s on our `main` branch. However, there are situations where we want to prevent pull requests from piling up while awaiting the release of upstream components[^1].
 In these cases, we allow merging pull requests that contain `source-repository-package`s, provided the referenced commit is on the `main` branch of the upstream package.
 
 If you do add a temporary `source-repository-package` stanza, you need to

docs/website/contents/references/miscellaneous/chain_sync.md

@@ -23,7 +23,7 @@ Note on terminology:
 2.  From (1), the intersection between their chain and our chain must be within
     `k` blocks from our tip.
 3.  Since our fragment will be anchored `k` back, from (2) we get that the
-    intersection between their chain and our chain must lie on our fragment.   
+    intersection between their chain and our chain must lie on our fragment.
     (NOTE: In the case of corruption of volatile DB -- or being near genesis --
     our fragment may be shorter than `k`, but even in that case, the length of
     our fragment will dictate our maximum rollback.)
@@ -37,7 +37,7 @@ Note on terminology:
     fragment, which would mean that we would miss some blocks.
 
 Note that if both nodes are following the same chain and are up to date, the
-intersection will be the _tip_ of both fragments.    
+intersection will be the _tip_ of both fragments.
 
 ## Chain evolution
 
@@ -73,7 +73,7 @@ The scenario is something like this:
 
 ```
                                 k
-                           /~~~~~~~~~~\                                 
+                           /~~~~~~~~~~\
 
 ..................\........------------ our fragment
                    \
@@ -115,7 +115,7 @@ We get notified through the chain sync protocol about updates to their chain:
       our chain, so the new intersection point must /be/ the rollback point.
       If that rollback point lies on our fragment (and hence is within @k@),
       all is good; otherwise, we disconnect.
-  
+
     Notes:
     - We could additionally (and optionally) check that they do not roll
      back more than `k`, and if they do, treat them as adversarial (disconnect).
@@ -158,4 +158,4 @@ trim their fragment so that it is anchored at our anchor point.
   sufficient number of headers to determine if their chain is preferred over
   ours (this needs careful consideration when adopting genesis).
 
-[^glossary]: See the [Glossary](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/Glossary/)
+[^glossary]: See the [Glossary](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/glossary/)

docs/website/contents/tutorials/preflight_guide.md

@@ -303,7 +303,7 @@ for Ungrindable Blockchains" by Kiayias et al](https://eprint.iacr.org/2021/1698
 [Magic Wormhole]: https://github.com/magic-wormhole/magic-wormhole
 [db-analyser]: https://github.com/IntersectMBO/ouroboros-consensus/blob/main/ouroboros-consensus-cardano/README.md#db-analyser
 [Cardano ledger]: https://github.com/IntersectMBO/cardano-ledger
-[Glossary]: https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/Glossary/
+[Glossary]: https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/glossary/
 [db-analyser snapshot]: https://github.com/IntersectMBO/ouroboros-consensus/blob/main/ouroboros-consensus-cardano/README.md#saving-a-snapshot
 [preflight epic]: https://github.com/IntersectMBO/ouroboros-consensus/issues/887
 [Ouroboros Praos paper]: https://iohk.io/en/research/library/papers/ouroboros-praos-an-adaptively-secure-semi-synchronous-proof-of-stake-protocol/

docs/website/docusaurus.config.js

@@ -194,6 +194,22 @@ const config = {
             from: '/docs/for-developers/utxo-hd/overview',
             to: '/docs/references/miscellaneous/utxo-hd/',
           },
+          {
+            from: '/docs/for-developers/utxo-hd/Overview/',
+            to: '/docs/references/miscellaneous/utxo-hd/',
+          },
+          {
+            from: '/docs/for-developers/PreflightGuide/',
+            to: '/docs/tutorials/preflight_guide/',
+          },
+          {
+            from: '/docs/for-developers/Glossary/',
+            to: '/docs/references/glossary/',
+          },
+          {
+            from: '/docs/for-developers/BootstrapPeersIER/',
+            to: '/docs/references/miscellaneous/bootstrap_peers_IER/',
+          },
         ],
         createRedirects(existingPath) {
           if (existingPath.includes('/docs/references/miscellaneous/utxo-hd')) {

ouroboros-consensus-cardano/CHANGELOG.md

@@ -38,7 +38,7 @@
 ### Breaking
 
 - Implement the UTxO-HD feature. See the documentation in [the
-  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/utxo-hd/Overview/).
+  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/miscellaneous/utxo-hd/).
   Fill in the UTxO-HD type families and instances for Shelley based blocks, the
   Byron block and the Cardano block.
 

ouroboros-consensus-diffusion/CHANGELOG.md

@@ -30,7 +30,7 @@
 ### Breaking
 
 - Implement the UTxO-HD feature. See the documentation in [the
-  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/utxo-hd/Overview/).
+  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/miscellaneous/utxo-hd/).
   - `hStateQueryServer` now needs a `ResourceRegistry` to allocate `Forker`s.
   - `DiskPolicyArgs` was transformed into `SnapshotPolicyArgs`.
   - `StdRunNodeArgs` got two new fields:
@@ -254,7 +254,7 @@ NOTE: version jumps from `0.11.0.0` to `0.13.0.0` because `0.12.0.0` was created
 
 - Added the Genesis State Machine (GSM), though for now it is merely the
   simpler [Bootstrap Peers State
-  Machine](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/BootstrapPeersIER/).
+  Machine](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/miscellaneous/bootstrap_peers_IER/).
 
 - Added `rnGetUseBootstrapPeers` to `RunNodeArgs`, for dynamically
   enabling/disabling the GSM. The proper GSM must always be running, despite

ouroboros-consensus/CHANGELOG.md

@@ -62,7 +62,7 @@
 ### Breaking
 
 - Implement the UTxO-HD feature. See the documentation in [the
-  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/for-developers/utxo-hd/Overview/).
+  webpage](https://ouroboros-consensus.cardano.intersectmbo.org/docs/references/miscellaneous/utxo-hd/).
   - The `LedgerState` type family changed its kind to `Type -> (Type -> Type) ->
     Type` to account for `MapKind`s.
   - `LedgerTables` store a `MapKind` of `TxIn l` to `TxOut l`.