From 7841f541983273ca10839e1a703b92f0c5805b70 Mon Sep 17 00:00:00 2001
From: AHERRCAB <109002919+AHERRCAB@users.noreply.github.com>
Date: Wed, 16 Jul 2025 07:13:22 +0200
Subject: [PATCH] change mire --> more

---
 docs/ci/Development/configure-the-xi-sender-adapter-41a1a57.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ci/Development/configure-the-xi-sender-adapter-41a1a57.md b/docs/ci/Development/configure-the-xi-sender-adapter-41a1a57.md
index e3376a61..dd09dcd9 100644
--- a/docs/ci/Development/configure-the-xi-sender-adapter-41a1a57.md
+++ b/docs/ci/Development/configure-the-xi-sender-adapter-41a1a57.md
@@ -30,7 +30,7 @@ Consider the following when using the XI adapter.
 
 -   Avoid changing the temporary storage location for operative scenarios \(or do it carefully\).
 
-    Such an action can result in data loss. The reason is that outdated messages \(which won't be retried anymore\) can still be stored there, even if you've changed the *Temporary Storage* attribute in the meantime. When you plan to change this attribute, make sure that there are no mire messages in the temporary storage originally configured.
+    Such an action can result in data loss. The reason is that outdated messages \(which won't be retried anymore\) can still be stored there, even if you've changed the *Temporary Storage* attribute in the meantime. When you plan to change this attribute, make sure that there are no more messages in the temporary storage originally configured.
 
 -   If possible, as *Temporary Storage* use the *JMS Queue* option as it comes with a better performance and reduced database load.