[5.1.x] Fixed typo in docs/topics/performance.txt.

Backport of ca113adbae1cc2129256f51ac71e8aed2a381576 from main.

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/topics/performance.txt b/docs/topics/performance.txt
index cedd824e30..4e23d1b6bc 100644
--- a/docs/topics/performance.txt
+++ b/docs/topics/performance.txt
@@ -137,7 +137,7 @@ one that it is comfortable to code for.
 
     Firstly, in a real-life case you need to consider what is happening before
     and after your count to work out what's an optimal way of doing it *in that
-    particular context*. The database optimization documents describes :ref:`a
+    particular context*. The database optimization document describes :ref:`a
     case where counting in the template would be better
     <overuse_of_count_and_exists>`.