From 0f2e82b9ec9797147945a6f9a402b5ae0fb1d9f4 Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Sat, 25 Apr 2015 15:05:48 -0400
Subject: [PATCH] Fixed #24704 -- Clarified system check interaction with
 runserver.

---
 docs/ref/django-admin.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 2b68f6575d..fd989e1344 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -785,9 +785,9 @@ reduction.
 .. _pyinotify: https://pypi.python.org/pypi/pyinotify/
 
 When you start the server, and each time you change Python code while the
-server is running, the server will check your entire Django project for errors (see
-the :djadmin:`check` command). If any errors are found, they will be printed
-to standard output, but it won't stop the server.
+server is running, the system check framework will check your entire Django
+project for some common errors (see the :djadmin:`check` command). If any
+errors are found, they will be printed to standard output.
 
 You can run as many servers as you want, as long as they're on separate ports.
 Just execute ``django-admin runserver`` more than once.