From 2948deb210520a3c7360c5b1fe4045146a15102e Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Mon, 28 Mar 2016 16:25:12 +0100 Subject: [PATCH] cosmetic: tweak link --- site/using-weave/service-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/using-weave/service-management.md b/site/using-weave/service-management.md index a58946f0..78672e07 100644 --- a/site/using-weave/service-management.md +++ b/site/using-weave/service-management.md @@ -50,7 +50,7 @@ Using the netcat service example described in An additional caveat is that `$HOST3` can only be reached from `$HOST1`, which is not accessible via `$HOST2`. Nonetheless, you still need to make the `$HOST3` service available to an application that is running in a container on `$HOST2`. -To satisfy this scenario, first expose the [application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`: +To satisfy this scenario, first [expose the application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`: host1$ weave expose -h host1.weave.local 10.2.1.3