From 22c35826992cc52b7b9774e314e47c18063908d2 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Mon, 28 Mar 2016 16:27:21 +0100 Subject: [PATCH] cosmetic: tweak example links --- site/using-weave/service-export.md | 2 +- site/using-weave/service-management.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/site/using-weave/service-export.md b/site/using-weave/service-export.md index 73c9d2f5..45480476 100644 --- a/site/using-weave/service-export.md +++ b/site/using-weave/service-export.md @@ -8,7 +8,7 @@ accessible to the outside world (and, more generally, to other networks) from any Weave Net host, irrespective of where the service containers are located. -Returning to the netcat example service, described in [Deploying Applications](/site/using-weave/deploying-applications.md), +Returning to the [netcat example service](/site/using-weave/deploying-applications.md), you can expose the netcat service running on `HOST1` and make it accessible to the outside world via `$HOST2`. First, expose the application network to `$HOST2`, as explained in [Integrating a Host Network with a Weave Net](/site/using-weave/host-network-integration.md): diff --git a/site/using-weave/service-management.md b/site/using-weave/service-management.md index 78672e07..b0345835 100644 --- a/site/using-weave/service-management.md +++ b/site/using-weave/service-management.md @@ -45,8 +45,7 @@ Similar NAT rules to the above can used to expose services not just to the outsi Applications running in containers on a Weave network can be given access to services, which are only reachable from certain Weave hosts, regardless of where the actual application containers are located. -Using the netcat service example described in -[Deploying Applications](/site/using-weave/deploying-applications.md), and expanding upon it, you now decide to add a third containerized netcat service. This additional netcat service runs on `$HOST3`, and listens on port 2211, but it is not on the Weave network. +Expanding on the [netcat service example](/site/using-weave/deploying-applications.md), you now decide to add a third, non-containerized, netcat service. This additional netcat service runs on `$HOST3`, and listens on port 2211, but it is not on the Weave network. 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`.