diff --git a/_alerts/2017-07-12-disruptive-forks.md b/_alerts/2017-07-12-disruptive-forks.md
index a3749df0..eaf7b312 100644
--- a/_alerts/2017-07-12-disruptive-forks.md
+++ b/_alerts/2017-07-12-disruptive-forks.md
@@ -5,17 +5,20 @@
 title: "Potential disruptive chain forks"
 shorturl: "disruptive-forks"
 active: true
-banner: "Warning: Bitcoin may be unsafe to use on August 1st (click here for details)"
+banner: "Warning: Bitcoin may be unsafe to use starting July 31st (click here for details)"
 
 ## 7/12 to 7/28: "warning" (orange); 7/29 until resolution: "alert" (red)
 bannerclass: "warning"
 ---
-*Last updated: 2017-07-12 12:00 UTC.  This page will be updated when new
-information becomes available.  See the [list of updates][].*
+{% assign start='<span class="date">2017/08/01 00:00 UTC</span>' %}
 
-On 1 August 2017, Bitcoin confirmation scores may become unreliable for
+*Last updated: <span class="date">2017/07/12 12:00 UTC</span>.  This
+page will be updated when new information becomes available.  See the
+[list of updates][].*
+
+At {{start}}, Bitcoin confirmation scores may become unreliable for
 an unknown length of time.  This means that any bitcoins you receive
-after August 1st may disappear from your wallet at a later time or be a
+after that time may later disappear from your wallet or be a
 type of bitcoin that other people will not accept as payment.
 
 Once the situation is resolved, confirmation scores will either
@@ -25,7 +28,7 @@ return to using Bitcoin normally; in the later case, you will need to
 take extra steps in order to begin safely receiving bitcoins again.
 
 This post currently describes what actions you can take to prepare for
-this situation.  Subsequent to August 1st, we will update this post as
+this situation.  Subsequent to {{start}}, we will update this post as
 best we can with relevant information, but you are also advised to
 monitor other Bitcoin [news sites][] and [community resources][] for
 updates and to cross-check all information, as someone may attempt to
@@ -35,15 +38,15 @@ Remember that you alone are responsible for the safety of your bitcoins,
 and that if you lose control of them for any reason, there is nothing
 the operators or contributors to this website can do to help you.
 
-## Before August 1st
+## Preparation
 
 1. If you accept bitcoins as payments, we recommend that you stop
-accepting Bitcoin payments at least 12 hours before 00:00 UTC on August
-1st (24 to 48 hours may be safer).  This will give time for all pending
-payments to confirm on the Bitcoin block chain before the event.
+accepting Bitcoin payments at least 12 hours before {{start}}, although
+24 to 48 hours earlier may be safer.  This will give time for all
+pending payments to confirm on the Bitcoin block chain before the event.
 
 1. If you send bitcoins as payments, note that many services may stop
-accepting bitcoins at 00:00 UTC on August 1st or earlier.
+accepting bitcoins at {{start}} or earlier.
 
 1. Be wary of storing your bitcoins on an exchange or other third-party
 wallet.  If they accept transactions during the event, they could lose
@@ -51,9 +54,9 @@ money and will likely spread those loses across all their users.  If
 there end up being two or more competing versions of Bitcoin, then they
 may refuse to give you your bitcoins on versions they don't like.
 
-## On August 1st
+## During the event
 
-1. Do not trust any payments you receive after August 1st until the situation
+1. Do not trust any payments you receive after {{start}} until the situation
 is resolved.  No matter how many confirmations the new payment says it
 has, it can disappear from your wallet at any point up until the
 situation is resolved.
@@ -66,7 +69,7 @@ recovery if you attempt this.
 by "splitting" your coins.  Some of these offers may be scams, and
 software claiming to split your coins can also steal them.
 
-## After August 1st
+## After the event
 
 No information available yet.  Please wait for multiple trustworthy
 sources to state that the event is resolved before returning to normal
@@ -78,9 +81,24 @@ A [full history][] of this document is available.  The following points
 summarize major changes, with the most recent changes being listed
 first.
 
-- 2017-07-12 12:00 UTC: initial version.
+- <span class="date">2017/07/12 12:00 UTC</span>: initial version.
 
 [full history]: https://github.com/bitcoin-dot-org/bitcoin.org/commits/master/_alerts/2017-07-12-disruptive-forks.md
 [list of updates]: #document-history
 [news sites]: /en/resources#news
 [community resources]: /en/community
+
+<script src="/js/jquery/jquery-1.11.2.min.js"></script>
+<script>
+// Localize dates
+$(".date").each(function() {
+  // Try to parse the string as a date
+  epoch = Date.parse($(this).text());
+  // Only convert the string to localtime if it's a number
+  if (isNaN(epoch) == false) {
+    var utcdate=new Date(epoch);
+    var localedate = utcdate.toString();
+    $(this).text(localedate);
+  }
+});
+</script>