diff --git a/docs/operational_guide/bootstrapping.md b/docs/operational_guide/bootstrapping.md
index 77a04096e3..a783caddf4 100644
--- a/docs/operational_guide/bootstrapping.md
+++ b/docs/operational_guide/bootstrapping.md
@@ -63,7 +63,7 @@ In this case, the peer bootstrapper running on node 1 will not be able to fullfi
 |  3   |   2   |   A   |
 |  3   |   3   |   A   |
 
-Note that a bootstrap consistency level of majority is the default value, but can be modified by changing the value of the key "m3db.client.bootstrap-consistency-level" in etcd to one of: "none", "one", "unstrict_majority" (attempt to read from majority, but settle for less if any errors occur), "majority" (strict majority), and "all".
+Note that a bootstrap consistency level of majority is the default value, but can be modified by changing the value of the key "m3db.client.bootstrap-consistency-level" in [etcd](https://coreos.com/etcd/) to one of: "none", "one", "unstrict_majority" (attempt to read from majority, but settle for less if any errors occur), "majority" (strict majority), and "all".
 
 **Note**: Any bootstrappers configuration that does not include the peers bootstrapper will be unable to handle dynamic topology changes of any kind.
 
diff --git a/docs/operational_guide/topology.md b/docs/operational_guide/topology.md
index e112794ee3..d0a7ab280c 100644
--- a/docs/operational_guide/topology.md
+++ b/docs/operational_guide/topology.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-M3DB stores its topology (mapping of which hosts are responsible for which shards) in etcd. There are three possible states that each host/shard pair can be in:
+M3DB stores its topology (mapping of which hosts are responsible for which shards) in [etcd](https://coreos.com/etcd/). There are three possible states that each host/shard pair can be in:
 
 1. Initializing
 2. Available