From 00031b73bda7d910aa19876694ebb6778c4b3e70 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 19 Feb 2013 11:31:41 -0500 Subject: [PATCH] Updated a couple admonitions to use the warning directive. --- docs/ref/unicode.txt | 2 +- docs/topics/auth/customizing.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index 784ff33398..92a446ff6b 100644 --- a/docs/ref/unicode.txt +++ b/docs/ref/unicode.txt @@ -68,7 +68,7 @@ Python 2 with unicode literals or Python 3:: See also :doc:`Python 3 compatibility `. -.. admonition:: Warning +.. warning:: A bytestring does not carry any information with it about its encoding. For that reason, we have to make an assumption, and Django assumes that all diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 9c31445455..2e7bf2e3db 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -408,7 +408,7 @@ This dotted pair describes the name of the Django app (which must be in your :setting:`INSTALLED_APPS`), and the name of the Django model that you wish to use as your User model. -.. admonition:: Warning +.. warning:: Changing :setting:`AUTH_USER_MODEL` has a big effect on your database structure. It changes the tables that are available, and it will affect the