diff options
Diffstat (limited to 'docs/topics/forms')
| -rw-r--r-- | docs/topics/forms/index.txt | 4 | ||||
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt index 0e98e50692..e7709834c2 100644 --- a/docs/topics/forms/index.txt +++ b/docs/topics/forms/index.txt @@ -164,7 +164,7 @@ So when we handle a model instance in a view, we typically retrieve it from the database. When we're dealing with a form we typically instantiate it in the view. -When we instantiate a form, we can opt to leave it empty or pre-populate it, for +When we instantiate a form, we can opt to leave it empty or prepopulate it, for example with: * data from a saved model instance (as in the case of admin forms for editing) @@ -207,7 +207,7 @@ Now you'll also need a view corresponding to that ``/your-name/`` URL which will find the appropriate key/value pairs in the request, and then process them. This is a very simple form. In practice, a form might contain dozens or -hundreds of fields, many of which might need to be pre-populated, and we might +hundreds of fields, many of which might need to be prepopulated, and we might expect the user to work through the edit-submit cycle several times before concluding the operation. diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 26a5fc8b0f..3332709089 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -820,7 +820,7 @@ Then, pass your ``BaseAuthorFormSet`` class to the factory function:: >>> AuthorFormSet = modelformset_factory( ... Author, fields=('name', 'title'), formset=BaseAuthorFormSet) -If you want to return a formset that doesn't include *any* pre-existing +If you want to return a formset that doesn't include *any* preexisting instances of the model, you can specify an empty QuerySet:: >>> AuthorFormSet(queryset=Author.objects.none()) |