documentation fixme

Author: crocodile-dentist

CONTRIBUTING.md

@@ -89,6 +89,9 @@ is very helpful to diagnose build time compiler errors.
 Any contributions should be well documented.  APIs should have well-written
 `haddocks`.  If a particular function expects a precondition to be satisfied it
 should be explicitly mentioned.  The inline documentation is published at
+
+-- TODO link
+
 <https://ouroboros-network.cardano.intersectmbo.org>.  When writing haddocks
 it's always good to put oneself in the position of somebody who hasn't yet
 interacted with your code changes.  It's good to explain the key design choices

README.md

@@ -1,5 +1,7 @@
 # Decentralized Message Queue
 
+TODO fix these links
+
 [![mingw64](https://img.shields.io/github/actions/workflow/status/intersectmbo/ouroboros-network/build.yml?event=merge_group&label=mingw64&style=for-the-badge)](https://github.com/intersectmbo/ouroboros-network/actions/workflows/build.yml)
 [![Nightly CI](https://img.shields.io/github/actions/workflow/status/intersectmbo/ouroboros-network/nightly.yml?branch=main&label=Nightly&style=for-the-badge)](https://github.com/intersectmbo/ouroboros-network/actions/workflows/nightly.yml)
 
@@ -8,7 +10,7 @@ and consuming messages which are diffused over a P2P network to other nodes.
 
 This repository provides the `dmq-node` executable to participate in the DMQ network.
 
-todo
+TODO diagram
 ```mermaid
 stateDiagram-v2
     dn: dmq-node

StyleGuide.md

@@ -1168,4 +1168,4 @@ There are more general guidelines on how we write and structure code.
    use that shared code in a test suite defined in another package. To avoid
    this problem, we avoid sharing source directories in `cabal` files.
 
-[consensus-style-guide]: ../ouroboros-consensus/docs/StyleGuide.md
+[consensus-style-guide]: https://github.com/IntersectMBO/ouroboros-consensus/blob/main/docs/website/contents/howtos/contributing/style_guide.md