From efe3ca09e029c63e25f6e19843cb0c68cc7fa816 Mon Sep 17 00:00:00 2001
From: Clifford Gama <53076065+cliff688@users.noreply.github.com>
Date: Thu, 13 Mar 2025 20:18:35 +0200
Subject: Fixed incorrect formatting for inline pluralized code references in
 docs.

---
 docs/ref/databases.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'docs/ref/databases.txt')

diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 8a36ac9bad..36a541f212 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -824,7 +824,7 @@ Substring matching and case sensitivity
 
 For all SQLite versions, there is some slightly counterintuitive behavior when
 attempting to match some types of strings.  These are triggered when using the
-:lookup:`iexact` or :lookup:`contains` filters in Querysets. The behavior
+:lookup:`iexact` or :lookup:`contains` filters in querysets. The behavior
 splits into two cases:
 
 1. For substring matching, all matches are done case-insensitively. That is a
@@ -1213,8 +1213,8 @@ string, and the data is silently converted to reflect this assumption.
 ``TextField`` limitations
 -------------------------
 
-The Oracle backend stores ``TextFields`` as ``NCLOB`` columns. Oracle imposes
-some limitations on the usage of such LOB columns in general:
+The Oracle backend stores each ``TextField`` as an ``NCLOB`` column. Oracle
+imposes some limitations on the usage of such LOB columns in general:
 
 * LOB columns may not be used as primary keys.
 
-- 
cgit v1.3