diff --git a/ReleasingMelange.wiki b/ReleasingMelange.wiki
index 40e24c8..547bbae 100644
--- a/ReleasingMelange.wiki
+++ b/ReleasingMelange.wiki
@@ -29,7 +29,6 @@
 
 From a mint checkout of the release commit, the commands to create and deploy a release are:
   # `git clean -xdf`
-  # cp -r <wherever overrides are stored> .`
   # `virtualenv venv`
   # `venv/pip/install -U lxml setuptools`
   # `venv/bin/python bootstrap.py`
@@ -38,8 +37,6 @@
   # `bin/gen-app-yaml <app ID>` - Melange's production app ID is google-melange
   # `thirdparty/google_appengine/appcfg.py --oauth2 update build`
 
-The elimination of the "overrides" step is tracked in [http://code.google.com/p/soc/issues/detail?id=1863 issue 1863].
-
 == Shifting traffic to a release ==
 
 The traffic splitting feature on [https://appengine.google.com/deployment?app_id=s~google-melange the production release dashboard] should be used to gradually shift traffic over to the new release while monitoring the logs for any stack traces or error messages that might indicate defects in the new release.