summaryrefslogtreecommitdiff
path: root/docs/ref/databases.txt
diff options
context:
space:
mode:
authorClifford Gama <53076065+cliff688@users.noreply.github.com>2025-03-13 20:18:35 +0200
committerGitHub <noreply@github.com>2025-03-13 15:18:35 -0300
commitefe3ca09e029c63e25f6e19843cb0c68cc7fa816 (patch)
treedfa385b0b2fea4caa7292915eb0a8b92b00e9b30 /docs/ref/databases.txt
parente7a9d756eedd0317132c81c3695d4a34bba5dcd3 (diff)
Fixed incorrect formatting for inline pluralized code references in docs.
Diffstat (limited to 'docs/ref/databases.txt')
-rw-r--r--docs/ref/databases.txt6
1 files changed, 3 insertions, 3 deletions
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.