From aaa974353a5f6f4312cfbf55ece63993423599ef Mon Sep 17 00:00:00 2001 From: Ilya Dmitrichenko Date: Wed, 3 May 2017 16:47:37 +0100 Subject: [PATCH] Use absolute path for links to other pages --- site/using-weave/weave-cloud.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/site/using-weave/weave-cloud.md b/site/using-weave/weave-cloud.md index c9a25cac..a8f5b089 100644 --- a/site/using-weave/weave-cloud.md +++ b/site/using-weave/weave-cloud.md @@ -85,7 +85,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/using-weave#testing) ### How Peer Discovery Works @@ -109,12 +109,12 @@ error message in its log and exit. To check the logs run: host1$ docker logs weave When a Weave Net instance is formed for the first time, the peers must -initialize the [IP Allocation Manager](site/ipam.md). This process, +initialize the [IP Allocation Manager](/site/ipam.md). This process, and the configuration options available, are unchanged when using Weave Cloud. When you shut down a peer for good, use [the `weave reset` -command](site/ipam/stop-remove-peers-ipam.md) and it will be removed +command](/site/ipam/stop-remove-peers-ipam.md) and it will be removed from the Weave Cloud database so future peers will not attempt to connect to it.