From f241e15ec128fd0402c9662b2b8ca8fca5a1280d Mon Sep 17 00:00:00 2001 From: Tom Wilkie Date: Tue, 4 Aug 2015 11:00:32 +0000 Subject: [PATCH] Review feedback --- site/weavedns.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site/weavedns.md b/site/weavedns.md index 50ebc4b7..29a66fbf 100644 --- a/site/weavedns.md +++ b/site/weavedns.md @@ -75,8 +75,8 @@ of all containers for that hostname across the entire cluster. WeaveDNS returns IP addresses in a random order to facilitate basic load balancing and failure tolerance. Most client side resolvers sort -the returned addresses based on reachability, sorting local addresses -to the top of the list (see [RFC 3484](https://www.ietf.org/rfc/rfc3484.txt)). +the returned addresses based on reachability, placing local addresses +at the top of the list (see [RFC 3484](https://www.ietf.org/rfc/rfc3484.txt)). For example, if there is container with the desired hostname on the local machine, the application will receive that container's IP address. Otherwise, the application will receive the IP address of a random