[2.2.x] Fixed #30419 -- Favored Meta.indexes over Meta.index_together in optimization docs.

Backport of 888fdf182e164fa4b24aa82fa833c90a2b9bee7a from master

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/topics/db/optimization.txt b/docs/topics/db/optimization.txt
index 6c2946645e..671f57a8ae 100644
--- a/docs/topics/db/optimization.txt
+++ b/docs/topics/db/optimization.txt
@@ -39,10 +39,10 @@ Use standard DB optimization techniques
 
 * Indexes_. This is a number one priority, *after* you have determined from
   profiling what indexes should be added. Use
-  :attr:`Field.db_index <django.db.models.Field.db_index>` or
-  :attr:`Meta.index_together <django.db.models.Options.index_together>` to add
-  these from Django. Consider adding indexes to fields that you frequently
-  query using :meth:`~django.db.models.query.QuerySet.filter()`,
+  :attr:`Meta.indexes <django.db.models.Options.indexes>` or
+  :attr:`Field.db_index <django.db.models.Field.db_index>` to add these from
+  Django. Consider adding indexes to fields that you frequently query using
+  :meth:`~django.db.models.query.QuerySet.filter()`,
   :meth:`~django.db.models.query.QuerySet.exclude()`,
   :meth:`~django.db.models.query.QuerySet.order_by()`, etc. as indexes may help
   to speed up lookups. Note that determining the best indexes is a complex