From 118f8bf9e6e3c4a9fa693fa35176e0287cc4e0fb Mon Sep 17 00:00:00 2001
From: Stefanie Molin <24376333+stefmolin@users.noreply.github.com>
Date: Mon, 10 Apr 2023 15:58:38 -0400
Subject: [PATCH] Backport PR #52573: DOC: Fix typo in whatsnew/v2.0.0.rst

---
 doc/source/whatsnew/v2.0.0.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/source/whatsnew/v2.0.0.rst b/doc/source/whatsnew/v2.0.0.rst
index 23b05634acf1b..b912fd5ee9d2d 100644
--- a/doc/source/whatsnew/v2.0.0.rst
+++ b/doc/source/whatsnew/v2.0.0.rst
@@ -207,7 +207,7 @@ Copy-on-Write improvements
   with a :class:`DataFrame`.
 
 - Trying to set values using chained assignment (for example, ``df["a"][1:3] = 0``)
-  will now always raise an warning when Copy-on-Write is enabled. In this mode,
+  will now always raise a warning when Copy-on-Write is enabled. In this mode,
   chained assignment can never work because we are always setting into a temporary
   object that is the result of an indexing operation (getitem), which under
   Copy-on-Write always behaves as a copy. Thus, assigning through a chain