From 2bae3fc7c9c01821f92852fbfc708214fd30799e Mon Sep 17 00:00:00 2001
From: Somit Mitra <63601724+mitrasomit@users.noreply.github.com>
Date: Mon, 23 Dec 2024 14:36:07 +0530
Subject: [PATCH] Update event-delta.md

"...........updated since the the previous delta call."

Here "the" was duplicate.
---
 api-reference/v1.0/api/event-delta.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/api-reference/v1.0/api/event-delta.md b/api-reference/v1.0/api/event-delta.md
index 00dff165d6a..ee0ec4fa0f4 100644
--- a/api-reference/v1.0/api/event-delta.md
+++ b/api-reference/v1.0/api/event-delta.md
@@ -70,7 +70,7 @@ If successful, this method returns a `200 OK` response code and [event](../resou
 
 Within a round of **delta** function calls bound by the date range of a **calendarView**, you may find a **delta** call returning two types of events under `@removed` with the reason `deleted`: 
 - Events that are within the date range and that have been deleted since the previous **delta** call.
-- Events that are _outside_ the date range and that have been added, deleted, or updated since the the previous **delta** call.
+- Events that are _outside_ the date range and that have been added, deleted, or updated since the previous **delta** call.
 
 Filter the events under `@removed` for the date range that your scenario requires.