From b62d8ce94bff65642ba31b51d9fc3a45a4584c5e Mon Sep 17 00:00:00 2001
From: Jamie <2119834+jamieQ@users.noreply.github.com>
Date: Mon, 8 Dec 2025 04:34:56 -0600
Subject: [PATCH] [fix]: minor typo cleanup in Swift 5 exclusivity article

---
 _posts/2019-02-05-swift-5-exclusivity.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_posts/2019-02-05-swift-5-exclusivity.md b/_posts/2019-02-05-swift-5-exclusivity.md
index 5090dda59..1900bf5f0 100644
--- a/_posts/2019-02-05-swift-5-exclusivity.md
+++ b/_posts/2019-02-05-swift-5-exclusivity.md
@@ -280,9 +280,9 @@ considered a violation of exclusivity when two separate properties are
 written and read; `point.x` and `point.y`. Because `Point` is declared
 as a `struct`, it is considered a value type, meaning that all of its
 properties are part of a whole value, and accessing one property
-accesses the entire value. The compiler makes exception to this rule
+accesses the entire value. The compiler makes an exception to this rule
 when it can prove safety via a straighforward static analysis. In
-particular, when same statement initiates accesses of two disjoint
+particular, when the same statement initiates accesses of two disjoint
 stored properties, the compiler avoids reporting an exclusivity
 violation. In the next example, the statement that calls `modifyX`
 first accesses `point` in order to immediately pass its property `x`