[2.2.x] Fixed #30505 -- Doc'd how changes in the order of Field.choices affect migrations.

Backport of 5248abe9b0425c1fc989c60a55860cdb4d135bcf from master

1 files changed, 4 insertions, 1 deletions

diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
index 90edd682ee..4aeb318f7b 100644
--- a/docs/topics/db/models.txt
+++ b/docs/topics/db/models.txt
@@ -154,7 +154,7 @@ ones:
     <Field.blank>`, the field will be required.
 
 :attr:`~Field.choices`
-    An :term:`iterable` of 2-tuples to use as choices for this field. If this
+    A :term:`sequence` of 2-tuples to use as choices for this field. If this
     is given, the default form widget will be a select box instead of the
     standard text field and will limit choices to the choices given.
 
@@ -168,6 +168,9 @@ ones:
             ('GR', 'Graduate'),
         ]
 
+    .. note::
+        A new migration is created each time the order of ``choices`` changes.
+
     The first element in each tuple is the value that will be stored in the
     database. The second element is displayed by the field's form widget.