URL Fixes

docs/src/installation/autonomous-control-plane.md

@@ -104,7 +104,7 @@ Setting up a second server with the same software components is an option, but t
 
 Given that we provide part of the local storage of the server as backing storage for the stateful sets in the `kind` cluster, the data stored on the server itself must be synced to a second server in some way.
 
-Her comes [DRBD](https://github.com/LINBIT/drbd) into play, this is a linux kernel module which can be configured to mirror one or more local block devices to another server connected over tcp. With the help of [pacemaker](https://www.clusterlabs.org/pacemaker/) a coordinated failover of resources running on top of filesystems created on such replicated drbd devices, a high available statefule server pair is possible. It is also possible to prevent split brain if both servers have a out-of-band management build in with power off capability.
+Her comes [DRBD](https://github.com/LINBIT/drbd) into play, this is a linux kernel module which can be configured to mirror one or more local block devices to another server connected over tcp. With the help of [pacemaker](https://clusterlabs.org/projects/pacemaker/) a coordinated failover of resources running on top of filesystems created on such replicated drbd devices, a high available statefule server pair is possible. It is also possible to prevent split brain if both servers have a out-of-band management build in with power off capability.
 DRBD can also be configured to sync storage between WAN links with a higher latency by using a async mechanism.
 
 Sample drbd configuration:
@@ -161,7 +161,7 @@ TODO: Where to connect the `needle` servers
 
 - Naming of the metal-stack chain elements, is `needle` and `nail` appropriate ?
 - Storage in the `needle` partition
-  - [MinIO DirectPV](https://min.io/docs/directpv) --> new to me, dont know exactly how this works, looks interesting
+  - [MinIO DirectPV](https://min.io/docs/directpv/) --> new to me, dont know exactly how this works, looks interesting
   - lightOS
   - [Diskomator](https://github.com/poettering/diskomator) --> Crazy
   - the needle server as initiator, maybe also replicated with drbd ?

docs/src/installation/deployment.md

@@ -6,7 +6,7 @@ In order to build up your deployment, we recommend to make use of the same Ansib
 
 In order to wrap up deployment dependencies there is a special [deployment base image](https://github.com/metal-stack/metal-deployment-base/pkgs/container/metal-deployment-base) hosted on GitHub that you can use for running the deployment. Using this Docker image eliminates a lot of moving parts in the deployment and should keep the footprints on your system fairly small and maintainable.
 
-This document will from now on assume that you want to use our Ansible deployment roles for setting up metal-stack. We will also use the deployment base image, so you should also have [Docker](https://docs.docker.com/get-docker/) installed. It is in the nature of software deployments to differ from site to site, company to company, user to user. Therefore, we can only describe you the way of how the deployment works for us. It is up to you to tweak the deployment described in this document to your requirements.
+This document will from now on assume that you want to use our Ansible deployment roles for setting up metal-stack. We will also use the deployment base image, so you should also have [Docker](https://docs.docker.com/get-started/get-docker/) installed. It is in the nature of software deployments to differ from site to site, company to company, user to user. Therefore, we can only describe you the way of how the deployment works for us. It is up to you to tweak the deployment described in this document to your requirements.
 
 ```@contents
 Pages = ["deployment.md"]