Prepare for publication.

diff --git a/blog/data/2012-10-26-system-downtime.txt b/blog/data/2012-10-26-system-downtime.txt
index aa75978d166972cf95d94e2f1ea1f798c74ad0c3..bce5c87b0e345f158883257f02b4be0efdf5cbcd 100644 (file)
--- a/blog/data/2012-10-26-system-downtime.txt
+++ b/blog/data/2012-10-26-system-downtime.txt
@@ -70,9 +70,9 @@ Technician:  [xxx]
 been a bit too free form to make it easy to automatically process them
 into a database for further analysis, and I would have used ISO 8601
 dates myself to make it easier to process (in other words I would ask
 been a bit too free form to make it easy to automatically process them
 into a database for further analysis, and I would have used ISO 8601
 dates myself to make it easier to process (in other words I would ask

-people to write '2012-06-16 06:00' instead of the start time format
-listed above).  There are also other issues with the format that could
-be improved, read the article for the details.</p>
+people to write '2012-06-16 06:00 +0000' instead of the start time
+format listed above).  There are also other issues with the format
+that could be improved, read the article for the details.</p>

 
 <p>I find the idea of standardising outage messages seem to be such a
 good idea that I would like to get it implemented here at the
 
 <p>I find the idea of standardising outage messages seem to be such a
 good idea that I would like to get it implemented here at the