From 78c842a3230f026ad678d243e5459cd6b314d99a Mon Sep 17 00:00:00 2001
From: Juan Catalano <jc@streema.com>
Date: Sun, 24 Mar 2013 22:53:48 -0700
Subject: Adapted uses of versionchanged/versionadded to the new form.

Refs #20104.
---
 docs/topics/db/sql.txt | 1 +
 1 file changed, 1 insertion(+)

(limited to 'docs/topics/db/sql.txt')

diff --git a/docs/topics/db/sql.txt b/docs/topics/db/sql.txt
index 34cfa382d3..3bf0684b29 100644
--- a/docs/topics/db/sql.txt
+++ b/docs/topics/db/sql.txt
@@ -222,6 +222,7 @@ For example::
         return row
 
 .. versionchanged:: 1.6
+
     In Django 1.5 and earlier, after performing a data changing operation, you
     had to call ``transaction.commit_unless_managed()`` to ensure your changes
     were committed to the database. Since Django now defaults to database-level
-- 
cgit v1.3