From 573ec220872a9b7020b5d6466e3fd1e396cdc746 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Wed, 24 Sep 2014 12:43:56 +0100 Subject: [PATCH] Fixed typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 23748005..e764013c 100644 --- a/README.md +++ b/README.md @@ -191,7 +191,7 @@ In some scenarios containers are started independently, e.g. via some existing tool chain, or require more complex startup sequences than provided by `weave run`. And sometimes the decision which application network a container should be part of is made post startup. For these -situation, weave allows an existing, running container to be attached +situations, weave allows an existing, running container to be attached to the weave network. To illustrate, we can achieve the same effect as the first example with