eradicate last remaining wEaVeDnS misspellings

site/plugin/cni-plugin-how-to.md

@@ -73,4 +73,4 @@ The following other fields in the spec are supported:
 ###Caveats
 
 - The Weave Net router container must be running for CNI to allocate addresses
-- The CNI plugin does not add entries to Weave DNS.
+- The CNI plugin does not add entries to weaveDNS.

site/weave-docker-api/name-resolution-proxy.md

@@ -15,7 +15,7 @@ This ensures that:
 - name resolution of the container's hostname, for example, via `hostname -i`,
 returns the Weave Net IP address. This is required for many cluster-aware
 applications to work.
-- unqualified names get resolved via DNS, for example typically via weavedns
+- unqualified names get resolved via DNS, for example typically via weaveDNS
 to Weave Net IP addresses. This is required so that in a typical setup
 one can simply "ping <container-name>", i.e. without having to
 specify a `.weave.local` suffix.

site/weavedns/overview-using-weavedns.md

@@ -5,10 +5,11 @@ layout: default
 
 
 
-The Weave DNS server answers name queries on a Weave network and provides a simple way for containers to find each other. Just give
-the containers hostnames and then tell other containers to connect to those names.
-Unlike Docker 'links', this requires no code changes and it works across
-hosts.
+WeaveDNS is a DNS server that answers name queries on a Weave network
+and provides a simple way for containers to find each other. Just give
+the containers hostnames and then tell other containers to connect to
+those names.  Unlike Docker 'links', this requires no code changes and
+it works across hosts.
 
 WeaveDNS is deployed as an embedded service within the Weave router.
 The service is automatically started when the router is launched: