From 675f4783b37b1588b598349448193a20ae1a80a8 Mon Sep 17 00:00:00 2001
From: Fahri Gedik <53567152+fahrigedik@users.noreply.github.com>
Date: Tue, 13 Jan 2026 12:27:27 +0300
Subject: [PATCH] Update conclusion on persistent messages and scalability

Added a note about the impact of persistent messages on scalability in the conclusion section.
---
 docs/en/Community-Articles/2026-01-11/article.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/en/Community-Articles/2026-01-11/article.md b/docs/en/Community-Articles/2026-01-11/article.md
index b529b9e752..2f1f25db45 100644
--- a/docs/en/Community-Articles/2026-01-11/article.md
+++ b/docs/en/Community-Articles/2026-01-11/article.md
@@ -148,6 +148,7 @@ Because a synchronous send makes a blocking call until a confirmation is receive
 
 #### 4. Overall Scalability
 This is because, upon receipt, the message broker has to spend more time persisting messages to disk, thus negatively affecting scalability. Persistent messages always give lower total throughput, which can limit scalability under high usage loads and high message volumes.
+
 ---
 
 ## Conclusion
@@ -166,4 +167,4 @@ The answers to these questions will help you determine whether the Async Chain o
 
 To see an example project where this pattern is implemented, you can check out the repository:
 
-🔗 **[GitHub Repository](https://github.com/fahrigedik/SoftwareArchitecturePatterns)**
\ No newline at end of file
+🔗 **[GitHub Repository](https://github.com/fahrigedik/SoftwareArchitecturePatterns)**