diff --git a/site/features.md b/site/features.md
index 73691bce..aaa1a43c 100644
--- a/site/features.md
+++ b/site/features.md
@@ -115,7 +115,8 @@ Weave detects when a container has exited and releases its
 automatically allocated addresses so they can be re-used.
 
 See the [Automatic IP Address Management](ipam.html) documentation for
-further details. We also have a page on [the basics of IP addressing](ip-addresses.html)
+further details. We also have an explanation of
+[the basics of IP addressing](ip-addresses.html)
 
 Instead of getting weave to allocate IP addresses automatically, it is
 also possible to specify an address and network explicitly, expressed
diff --git a/site/ip-addresses.md b/site/ip-addresses.md
index da5438c6..41ca345b 100644
--- a/site/ip-addresses.md
+++ b/site/ip-addresses.md
@@ -64,8 +64,8 @@ chances of overlap. But it could be that you or your hosting provider
 are using some of these private addresses in the same range, which would
 cause a clash.
 
-Here's an example that came up recently: on `weave launch`, the
-following error message appeared:
+Here's an example: on `weave launch`, the following error message
+can appear:
 
 ````
 Network 10.32.0.0/12 overlaps with existing route 10.0.0.0/8 on host.