From cf48962b361b573e580b79839c19b640b7f304a2 Mon Sep 17 00:00:00 2001
From: Becka R <rebecca@rebecca-robbins.com>
Date: Thu, 11 Feb 2016 11:27:15 -0800
Subject: [PATCH] Clarified "database column type" explanation.

---
 docs/topics/db/models.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 261ce14f44..99240dc65a 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -111,7 +111,8 @@ Each field in your model should be an instance of the appropriate
 :class:`~django.db.models.Field` class. Django uses the field class types to
 determine a few things:
 
-* The database column type (e.g. ``INTEGER``, ``VARCHAR``).
+* The column type, which tells the database what kind of data to store (e.g.
+  ``INTEGER``, ``VARCHAR``, ``TEXT``).
 
 * The default HTML :doc:`widget </ref/forms/widgets>` to use when rendering a form
   field (e.g. ``<input type="text">``, ``<select>``).