diff --git a/site/install/weave-cloud.md b/site/install/weave-cloud.md
index 4c3e02af..85780780 100644
--- a/site/install/weave-cloud.md
+++ b/site/install/weave-cloud.md
@@ -86,7 +86,7 @@ first and automatically create a connection to it.
 
 >**Note:** If there is a firewall between `$HOST1` and `$HOST2`,  you must permit traffic to flow through TCP 6783 and UDP 6783/6784, which are Weave’s control and data ports.
 
-Now you can proceed to [test container communications](/site/using-weave#testing)
+Now you can proceed to [test container communications](/site/install/using-weave#testing)
 
 ### <a name="how-it-works"></a>How Peer Discovery Works
 
diff --git a/site/tasks/manage/awsvpc.md b/site/tasks/manage/awsvpc.md
index 4e648147..386e2f66 100644
--- a/site/tasks/manage/awsvpc.md
+++ b/site/tasks/manage/awsvpc.md
@@ -75,7 +75,7 @@ your cluster.
   is all or nothing.  In this mode, all hosts in a cluster must be AWS
   instances. (We hope to ease this limitation in future.)
 - The `weave launch` command waits until the
-  [IP address manager](/site//operational-guide/concepts.md#ip-address-manager-ipam)
+  [IP address manager](/site/operational-guide/concepts.md#ip-address-manager-ipam)
   is ready, i.e. until after this peer has been able to make contact
   with other peers and confirm that it has joined the cluster the
   bridge.  Without AWS-VPC, `weave launch` returns without waiting.