Fix spelling mistakes.

docs/fastdp.md

@@ -24,7 +24,7 @@ The router relies on having access to the source and destination peer
 when deciding how to forward packets. When the Sleeve overlay is in
 use this information is conveyed directly within the encapsulation by
 including the names of the peers in question, a solution not
-accomodated directly by the vxlan wire format. Fortunately vxlan does
+accommodated directly by the vxlan wire format. Fortunately vxlan does
 have a twenty four bit segment ID field in the header we can use to
 encode this data - the challenge is to identify peers uniquely with a
 twelve bit identifier instead of the seventeen bytes used by Sleeve.
@@ -54,8 +54,8 @@ with low path MTUs.
 To avoid triggering this fallback in typical deployments, the datapath
 interface is statically configured with an MTU of 1410 bytes allowing
 it to work with most underlay network provider MTUs, including GCE at
-1460 bytes (the fifty byte difference accomodates the vxlan overhead).
-This value can be overriden by setting `WEAVE_MTU` at launch if
+1460 bytes (the fifty byte difference accommodates the vxlan overhead).
+This value can be overridden by setting `WEAVE_MTU` at launch if
 necessary.
 
 # Virtual Ports

docs/weavedns-design.md

@@ -9,7 +9,7 @@ The model is that each host has a service that is notified of
 hostnames and weave addresses for containers on the host.  Like IPAM,
 this service is embedded within the router.  It binds to
 the host bridge to answer DNS queries from local containers; for
-anything it can't answer, it uses the infomation in the host's
+anything it can't answer, it uses the information in the host's
 /etc/resolv.conf to query an 'fallback' server.
 
 The service is comprised of a DNS server, which answers all DNS queries
@@ -33,7 +33,7 @@ are re-broadcast around the cluster.
 The DNS server also listens to the Docker event stream, and removes
 entries for containers when they die.  Entries removed in this way are
 tombstoned, and the tombstone lazily broadcast around the cluster.
-After a short timeout the tombstones are independantly removed from
+After a short timeout the tombstones are independently removed from
 each host.
 
 

ipam/allocator.go

@@ -381,7 +381,7 @@ func (alloc *Allocator) Shutdown() {
 
 // AdminTakeoverRanges (Sync) - take over the ranges owned by a given
 // peer, and return how much space was transferred in the process.
-// Only done on adminstrator command.
+// Only done on administrator command.
 func (alloc *Allocator) AdminTakeoverRanges(peerNameOrNickname string) address.Count {
 	resultChan := make(chan address.Count)
 	alloc.actionChan <- func() {

site/ip-addresses/configuring-weave.md

@@ -32,7 +32,7 @@ If you are sure the addresses you want are not in use, then
 explicitly setting the range with `--ipalloc-range` in the
 command-line arguments to `weave launch` on all hosts forces Weave
 Net to use that range, even though it overlaps. Otherwise, you can
-pick a different range, preferrably another subset of the [Private
+pick a different range, preferably another subset of the [Private
 Networks](https://en.wikipedia.org/wiki/Private_network).  For example
 172.30.0.0/16.
 

site/ipam/overview-init-ipam.md

@@ -11,7 +11,7 @@ invocations of the `run`, `start`,
 `attach`, `detach`, `expose`, and `hide` commands. Weave Net can also assign
 addresses in multiple subnets.
 
-The following automatic IP address managment topics are discussed: 
+The following automatic IP address management topics are discussed:
 
  * [Initializing Peers on a Weave Network](#initialization)
  * [`--init-peer-count` and How Quorum is Achieved](#quorum)

site/troubleshooting.md

@@ -89,7 +89,7 @@ communication protocol name and supported versions (min..max).
  * **Name** - identifies the local Weave Router as a peer on the
 Weave network. The nickname shown in parentheses defaults to the name
 of the host on which the Weave container was launched. It
-can be overriden by using the `--nickname` argument at `weave
+can be overridden by using the `--nickname` argument at `weave
 launch`.
 
  * **Encryption** - indicates whether

site/weave-docker-api/set-up-proxy.md

@@ -40,7 +40,7 @@ based on the Docker daemon's settings, and the listening interfaces are
 autoconfigured based on your Docker client's settings.
 
 Multiple `-H` arguments can be specified. If you are working with a
-remote docker daemon, then any firewalls inbetween need to be
+remote docker daemon, then any firewalls in between need to be
 configured to permit access to the proxy port.
 
 All docker commands can be run via the proxy, so it is safe to adjust

site/weavedns-design.md

@@ -9,7 +9,7 @@ The model is that each host has a service that is notified of
 hostnames and weave addresses for containers on the host.  Like IPAM,
 this service is embedded within the router.  It binds to
 the host bridge to answer DNS queries from local containers; for
-anything it can't answer, it uses the infomation in the host's
+anything it can't answer, it uses the information in the host's
 /etc/resolv.conf to query an 'fallback' server.
 
 The service is comprised of a DNS server, which answers all DNS queries
@@ -33,7 +33,7 @@ are re-broadcast around the cluster.
 The DNS server also listens to the Docker event stream, and removes
 entries for containers when they die.  Entries removed in this way are
 tombstoned, and the tombstone lazily broadcast around the cluster.
-After a short timeout the tombstones are independantly removed from
+After a short timeout the tombstones are independently removed from
 each host.