From 0cd331b044645f7881ad115cb61b98ecceec93c3 Mon Sep 17 00:00:00 2001
From: 0nly1ken0bi <54916539+0nly1ken0bi@users.noreply.github.com>
Date: Sun, 3 Dec 2023 11:40:54 +0200
Subject: [PATCH] Fixed documentation to read better (#2008)

---
 Readme.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Readme.md b/Readme.md
index 769ea0e33..680bd2438 100644
--- a/Readme.md
+++ b/Readme.md
@@ -444,7 +444,7 @@ Limitations and caveats
 ---------------------
 Dapper caches information about every query it runs, this allows it to materialize objects quickly and process parameters quickly. The current implementation caches this information in a `ConcurrentDictionary` object. Statements that are only used once are routinely flushed from this cache. Still, if you are generating SQL strings on the fly without using parameters it is possible you may hit memory issues.
 
-Dapper's simplicity means that many feature that ORMs ship with are stripped out. It worries about the 95% scenario, and gives you the tools you need most of the time. It doesn't attempt to solve every problem.
+Dapper's simplicity means that many features that ORMs ship with are stripped out. It worries about the 95% scenario, and gives you the tools you need most of the time. It doesn't attempt to solve every problem.
 
 Will Dapper work with my DB provider?
 ---------------------