From 7c2c4d7c9af33cb58d538893d2b5b0e0a788912f Mon Sep 17 00:00:00 2001
From: Habin Song <83588265+boulce@users.noreply.github.com>
Date: Tue, 15 Oct 2024 00:57:43 +0900
Subject: [PATCH] Update scheduling.adoc

Change 'OutOfMemoryErrors' to 'OutOfMemoryError'.

Closes gh-33703
---
 framework-docs/modules/ROOT/pages/integration/scheduling.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/framework-docs/modules/ROOT/pages/integration/scheduling.adoc b/framework-docs/modules/ROOT/pages/integration/scheduling.adoc
index 796d1ea326d..c57059aa3fc 100644
--- a/framework-docs/modules/ROOT/pages/integration/scheduling.adoc
+++ b/framework-docs/modules/ROOT/pages/integration/scheduling.adoc
@@ -733,7 +733,7 @@ reached, does the executor create a new thread beyond the core size. If the max
 has also been reached, then the executor rejects the task.
 
 By default, the queue is unbounded, but this is rarely the desired configuration,
-because it can lead to `OutOfMemoryErrors` if enough tasks are added to that queue while
+because it can lead to `OutOfMemoryError` if enough tasks are added to that queue while
 all pool threads are busy. Furthermore, if the queue is unbounded, the max size has
 no effect at all. Since the executor always tries the queue before creating a new
 thread beyond the core size, a queue must have a finite capacity for the thread pool to