From 4a00a7bc79bffdc95179d32d417ca2db56efed6e Mon Sep 17 00:00:00 2001
From: Aldiyar Dabarov <36531464+dabarov@users.noreply.github.com>
Date: Fri, 22 Mar 2024 09:47:48 +0100
Subject: [PATCH] Fix typo in System Design Roadmap (#5380)

---
 .../system-design/content/112-caching/101-cdn-caching.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/data/roadmaps/system-design/content/112-caching/101-cdn-caching.md b/src/data/roadmaps/system-design/content/112-caching/101-cdn-caching.md
index a0916edce..0568af197 100644
--- a/src/data/roadmaps/system-design/content/112-caching/101-cdn-caching.md
+++ b/src/data/roadmaps/system-design/content/112-caching/101-cdn-caching.md
@@ -1,6 +1,6 @@
 # CDN Caching
 
-A Content Delivery Network (CDN) is a distributed network of servers that are strategically placed in various locations around the world. The main purpose of a CDN is to serve content to end-users with high availability and high performance by caching frequently accessed content on servers that are closer to the end-users/
+A Content Delivery Network (CDN) is a distributed network of servers that are strategically placed in various locations around the world. The main purpose of a CDN is to serve content to end-users with high availability and high performance by caching frequently accessed content on servers that are closer to the end-users.
 
 When a user requests content from a website that is using a CDN, the CDN will first check if the requested content is available in the cache of a nearby server. If the content is found in the cache, it is served to the user from the nearby server. If the content is not found in the cache, it is requested from the origin server (the original source of the content) and then cached on the nearby server for future requests.