From eba100097cd2b991e1abb64646ebf7b777db000e Mon Sep 17 00:00:00 2001
From: Hamza Albreem <94292623+braim23@users.noreply.github.com>
Date: Thu, 1 Dec 2022 10:21:58 +0300
Subject: [PATCH] tiny fix

---
 docs/en/Deployment/Configuring-Production.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/Deployment/Configuring-Production.md b/docs/en/Deployment/Configuring-Production.md
index e4938bea44..5efa560621 100644
--- a/docs/en/Deployment/Configuring-Production.md
+++ b/docs/en/Deployment/Configuring-Production.md
@@ -21,7 +21,7 @@ That's all. ABP, then will add this prefix to all of your cache keys in your app
 
 > **Warning**: If you are building a microservice system, then you will have multiple applications that share the same distributed cache server. In such systems, all applications (or services) should normally use the same cache prefix, because you want all the applications to use the same cache data to have consistency between them.
 
-> **Warning**: Some of the ABP's startup templates are pre-configured to set a prefix value for the distributed cache. So, please check your application code if it is already configured.
+> **Warning**: Some of ABP's startup templates are pre-configured to set a prefix value for the distributed cache. So, please check your application code if it is already configured.
 
 ## Distributed Lock Prefix