Improve language.

diff --git a/blog/data/2012-10-26-system-downtime.txt b/blog/data/2012-10-26-system-downtime.txt
index bce5c87b0e345f158883257f02b4be0efdf5cbcd..239fa36749eee68ab4fd9d99a098dd1deec56542 100644 (file)
--- a/blog/data/2012-10-26-system-downtime.txt
+++ b/blog/data/2012-10-26-system-downtime.txt
@@ -28,10 +28,11 @@ etc etc.  The article is a good read to get some empirical data on
 what kind of problems affect a data centre, but what really inspired
 me was the kind of reporting they had put in place since 2000.<p>
 
-<p>The centre set up a mailing list, and send fairly standardised
-messages to this list when a outage was planned or when it already
-occurred.  Here is the two example from the article: First the
-unplanned outage:
+<p>The centre set up a mailing list, and started to send fairly
+standardised messages to this list when a outage was planned or when
+it already occurred, to announce the plan and get feedback on the
+assumtions on scope and user impact.  Here is the two example from the
+article: First the unplanned outage:
 
 <blockquote><pre>
 Subject:     Exchange 2003 Cluster Issues