From ce165805481988e95887bf62c45cd616af5bba0f Mon Sep 17 00:00:00 2001
From: Tom Christie <tom@tomchristie.com>
Date: Fri, 19 Sep 2014 14:31:49 +0100
Subject: [PATCH] Tweak

---
 topics/release-notes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/topics/release-notes.html b/topics/release-notes.html
index 256d04966..4f8ebe661 100644
--- a/topics/release-notes.html
+++ b/topics/release-notes.html
@@ -217,7 +217,7 @@ a.fusion-poweredby {
 <h2 id="versioning">Versioning</h2>
 <p>Minor version numbers (0.0.x) are used for changes that are API compatible.  You should be able to upgrade between minor point releases without any other code changes.</p>
 <p>Medium version numbers (0.x.0) may include API changes, in line with the <a href="#deprecation-policy">deprecation policy</a>.  You should read the release notes carefully before upgrading between medium point releases.</p>
-<p>Major version numbers (x.0.0) are reserved for substantial project milestones.  No major point releases are currently planned.</p>
+<p>Major version numbers (x.0.0) are reserved for substantial project milestones.</p>
 <h2 id="deprecation-policy">Deprecation policy</h2>
 <p>REST framework releases follow a formal deprecation policy, which is in line with <a href="https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy">Django's deprecation policy</a>.</p>
 <p>The timeline for deprecation of a feature present in version 1.0 would work as follows:</p>