From 0f90792d8deae227b2f7ba7b1259d9f2d791f426 Mon Sep 17 00:00:00 2001
From: Adriaan Joubert <45142747+adriaanjoubert@users.noreply.github.com>
Date: Thu, 3 Apr 2025 20:56:29 +0300
Subject: [PATCH] Fix typo (#12495)

(cherry picked from commit 51007fe428d87e5d5bfc2c04cd4224fda2e00879)
---
 doc/build/errors.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/build/errors.rst b/doc/build/errors.rst
index 237d5d0ab3..99701ba279 100644
--- a/doc/build/errors.rst
+++ b/doc/build/errors.rst
@@ -136,7 +136,7 @@ What causes an application to use up all the connections that it has available?
   upon to release resources in a timely manner.
 
   A common reason this can occur is that the application uses ORM sessions and
-  does not call :meth:`.Session.close` upon them one the work involving that
+  does not call :meth:`.Session.close` upon them once the work involving that
   session is complete. Solution is to make sure ORM sessions if using the ORM,
   or engine-bound :class:`_engine.Connection` objects if using Core, are explicitly
   closed at the end of the work being done, either via the appropriate
-- 
2.47.3