fix(doc): fix deadlinks
diff --git a/src/components/classic/documentation/kahadb-master-slave.md b/src/components/classic/documentation/kahadb-master-slave.md
index 6a000c5..db083f4 100644
--- a/src/components/classic/documentation/kahadb-master-slave.md
+++ b/src/components/classic/documentation/kahadb-master-slave.md
@@ -27,7 +27,7 @@
Master Election
---------------
-KahaDB supports a pluggable Master Election algorithm but the only current implementation is one based on [ZooKeeper](http://hadoop.apache.org/zookeeper).
+KahaDB supports a pluggable Master Election algorithm but the only current implementation is one based on [ZooKeeper](https://zookeeper.apache.org/).
ZooKeeper is used to implement the master election algorithm. ZooKeeper is a very fast, replicated, in memory database with features that make it easy to implement cluster control algorithms. It is an Apache project which you can [freely download](http://hadoop.apache.org/zookeeper/releases.html). You must installed and have at least one ZooKeeper server running before setting up a KahaDB Master Slave configuration.
diff --git a/src/components/classic/documentation/networks-of-brokers.md b/src/components/classic/documentation/networks-of-brokers.md
index fb513b4..9c70e76 100644
--- a/src/components/classic/documentation/networks-of-brokers.md
+++ b/src/components/classic/documentation/networks-of-brokers.md
@@ -55,7 +55,7 @@
### Example using multicast discovery
-This example uses multicast [discovery](http://activemq.apache.orgFeatures/discovery)
+This example uses [multicast discovery](discovery#multicast)
```
<?xml version="1.0" encoding="UTF-8"?>
diff --git a/src/components/classic/documentation/shared-file-system-master-slave.md b/src/components/classic/documentation/shared-file-system-master-slave.md
index ca4bed7..c161537 100644
--- a/src/components/classic/documentation/shared-file-system-master-slave.md
+++ b/src/components/classic/documentation/shared-file-system-master-slave.md
@@ -69,7 +69,7 @@
-One of the other other slaves immediately grabs the exclusive lock on the file system to them commences becoming the master, starting all of its transport connectors.
+One of the other slaves immediately grabs the exclusive lock on the file system to them commences becoming the master, starting all of its transport connectors.
Clients loose connection to the stopped master and then the failover transport tries to connect to the available brokers - of which the only one available is the new master.
