diff --git a/docs/topics/forms/formsets.txt b/docs/topics/forms/formsets.txt
index 29139c5..0d1db8f 100644
a
|
b
|
happen when the user changes these values::
|
413 | 413 | |
414 | 414 | Default: ``False`` |
415 | 415 | |
416 | | Lets you create a formset with the ability to delete:: |
| 416 | Lets you create a formset with the ability to select forms for deletion:: |
417 | 417 | |
418 | 418 | >>> from django.forms.formsets import formset_factory |
419 | 419 | >>> from myapp.forms import ArticleForm |
… |
… |
delete fields you can access them with ``deleted_forms``::
|
461 | 461 | >>> [form.cleaned_data for form in formset.deleted_forms] |
462 | 462 | [{'DELETE': True, 'pub_date': datetime.date(2008, 5, 10), 'title': u'Article #1'}] |
463 | 463 | |
| 464 | If you are using a :class:`ModelFormSet<django.forms.models.BaseModelFormSet>`, |
| 465 | instances for deleted forms will be deleted when you call ``formset.save()``. |
| 466 | On the other hand, if you are using a plain ``FormSet``, it's up to you to |
| 467 | handle ``formset.deleted_forms``, perhaps in your ``FormSet``'s ``save()`` |
| 468 | method, as there's no general way of deleting a form. |
| 469 | |
464 | 470 | Adding additional fields to a formset |
465 | 471 | ------------------------------------- |
466 | 472 | |
… |
… |
If you manually render fields in the template, you can render
|
559 | 565 | </form> |
560 | 566 | |
561 | 567 | |
562 | | Similarly, if the formset has the ability to order (``can_order=True``), it is possible to render it |
563 | | with ``{{ form.ORDER }}``. |
| 568 | Similarly, if the formset has the ability to order (``can_order=True``), it is |
| 569 | possible to render it with ``{{ form.ORDER }}``. |
564 | 570 | |
565 | 571 | Using more than one formset in a view |
566 | 572 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |