diff --git a/docs/ref/contrib/contenttypes.txt b/docs/ref/contrib/contenttypes.txt
index 28a2e40819..cc8671b1b9 100644
a
|
b
|
behavior; if desired, you can avoid the cascade-deletion by not using
|
443 | 443 | behavior can be provided via the :data:`~django.db.models.signals.pre_delete` |
444 | 444 | signal. |
445 | 445 | |
| 446 | Methods on ``GenericRelation`` managers |
| 447 | --------------------------------------- |
| 448 | |
| 449 | .. method:: remove(*objs, bulk=True) |
| 450 | |
| 451 | Removes the specified model objects from the related object set and |
| 452 | deletes them from the database. |
| 453 | |
| 454 | .. code-block:: python |
| 455 | |
| 456 | >>> b.tags.remove(t) # Deletes TaggedItem t from database. |
| 457 | |
| 458 | .. method:: clear() |
| 459 | |
| 460 | Removes all items from the related object set and deletes them from the |
| 461 | database. |
| 462 | |
| 463 | .. code-block:: python |
| 464 | |
| 465 | >>> b.tags.clear() # Deletes all related TaggedItems from database. |
| 466 | |
| 467 | In both the above examples this behaviour differs from that of |
| 468 | :class:`django.db.models.fields.related.RelatedManager` which has |
| 469 | methods named ``remove`` and ``clear`` which disassociate the |
| 470 | related objects without deleting them from the database. |
| 471 | |
446 | 472 | Generic relations and aggregation |
447 | 473 | --------------------------------- |
448 | 474 | |