Technically ambiguous reference docs for Field.primary_key
|Reported by:||Keryn Knight <django@…>||Owned by:||nobody|
|Has patch:||yes||Needs documentation:|
|Needs tests:||Patch needs improvement:|
In the Model Field Reference, the description for Field.primary_key says that Django will automatically add an IntegerField to hold the primary key - this is semi-correct, because Django actually provides an AutoField, itself internally represented as an IntegerField.
- Changed IntegerField to AutoField. This should be OK, as the AutoField documentation describes it being an IntegerField.
- Removed pluralisation in "for any fields in …", changing to "for any field in …" as there can be only one on a model.