diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index 54c42815..11928849 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -15,7 +15,7 @@ Changelog
 * **Backwards icompatible:** Rename the (``content_type``, ``object_id``) index on ``TaggedItem``.
   It is very unlikely for this to affect your code itself, and a migration will rename the index. This should not cause any downtime according to my research (Postgres does not lock the table for index renames, and Oracle holds a tiny lock to do it, and the change is only to the metadata, so is not dependent on table size).
 
-* **Backwards incompatible:** Remove the ``.indexed_together`` and ``.unique_together`` attributes on ``TaggedItem``
+* **Backwards incompatible:** Remove the ``.index_together`` and ``.unique_together`` attributes on ``TaggedItem``
 
   We are instead using ``constraints`` and ``indexes`` to set up these properties.
 * Remove support for Django 3.2.