Merge pull request #2703 from weaveworks/issues/2700-ip-link

Docs: improve IP route links
This commit is contained in:
Bryan Boreham authored and GitHub committed 2016-12-23 11:26:52 +00:00
commit 48508044d6
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -37,7 +37,7 @@ The most common prefix lengths are 8, 16 and 24, but there is nothing
stopping you using a /9 network or a /26. For example, `6.250.3.1/9` is on the
`6.128.0.0/9` network.
Several websites offer calculators to decode this kind of address, see: [IP Address Guide](http://www.ipaddressguide.com/cidr).
Several websites offer calculators to decode this kind of address, see, for example: [IP Address Guide](http://www.ipaddressguide.com/cidr).
The following is an example route table for a container that is attached to a Weave
network:
+1 -1
View File
@@ -179,7 +179,7 @@ The range parameter is written in
in this example "/16" means the first 16 bits of the address form the
network address and the allocator is to allocate container addresses
that all start 10.2. See [IP
addresses and routes](/site/using-weave/service-management.md#routing) for more information.
addresses and routes](/site/how-it-works/ip-addresses.md) for more information.
Weave shares the IP address range across all peers, dynamically
according to their needs. If a group of peers becomes isolated from