From f402b5a89501de8c0f81100ed0c83da650a2ce85 Mon Sep 17 00:00:00 2001
From: Chen-Yuanmeng <118530431+Chen-Yuanmeng@users.noreply.github.com>
Date: Mon, 27 Oct 2025 15:39:25 +0800
Subject: [PATCH] Correct typo in CASSANDRA-14092.txt

---
 CASSANDRA-14092.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CASSANDRA-14092.txt b/CASSANDRA-14092.txt
index cdf3c6a2f6..6db77479c8 100644
--- a/CASSANDRA-14092.txt
+++ b/CASSANDRA-14092.txt
@@ -4,7 +4,7 @@ CASSANDRA-14092: MAXIMUM TTL EXPIRATION DATE
 The maximum expiration timestamp that can be represented by the storage engine has been raised to
 2106-02-07T06:28:13+00:00 from the previous 2038-01-19T03:14:06+00:00, which means that INSERTS using 
 TTL that would expire after this date are not currently supported. Notice that on previous versions <5.0 
-or when 5.0 is ran in compatibility mode (<="oa" sstable formats) the limit stays at at 2038-01-19T03:14:06+00:00.
+or when 5.0 is run in compatibility mode (<="oa" sstable formats) the limit stays at 2038-01-19T03:14:06+00:00.
 
 There is a new yaml property storage_compatibility_mode that determines the
 Cassandra major version we want to stay compatible with. Its default is CASSANDRA_4, which means that