diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index f9dbb76..8583719 100644
a
|
b
|
update
|
1564 | 1564 | .. method:: update(**kwargs) |
1565 | 1565 | |
1566 | 1566 | Performs an SQL update query for the specified fields, and returns |
1567 | | the number of rows affected. |
| 1567 | the number of rows matched (which may not be equal to the number of rows |
| 1568 | updated if some rows already have the new value). |
1568 | 1569 | |
1569 | 1570 | For example, to turn comments off for all blog entries published in 2010, |
1570 | 1571 | you could do this:: |
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index c724eab..54f0692 100644
a
|
b
|
new value to be the new model instance you want to point to. For example::
|
959 | 959 | >>> Entry.objects.all().update(blog=b) |
960 | 960 | |
961 | 961 | The ``update()`` method is applied instantly and returns the number of rows |
962 | | affected by the query. The only restriction on the |
| 962 | matched by the query (which may not be equal to the number of rows updated if |
| 963 | some rows already have the new value). The only restriction on the |
963 | 964 | :class:`~django.db.models.query.QuerySet` that is updated is that it can only |
964 | 965 | access one database table, the model's main table. You can filter based on |
965 | 966 | related fields, but you can only update columns in the model's main |