From f2cfe63f212f825599d8d44a653f42cbdb532f7b Mon Sep 17 00:00:00 2001
From: rudysap <162417628+rudysap@users.noreply.github.com>
Date: Wed, 6 Mar 2024 14:39:13 +0100
Subject: [PATCH] Update define-a-timer-start-event

Remove a duplicated sentence
---
 docs/ci/Development/define-a-timer-start-event-ae14ad7.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ci/Development/define-a-timer-start-event-ae14ad7.md b/docs/ci/Development/define-a-timer-start-event-ae14ad7.md
index d60291b..9abb31e 100644
--- a/docs/ci/Development/define-a-timer-start-event-ae14ad7.md
+++ b/docs/ci/Development/define-a-timer-start-event-ae14ad7.md
@@ -16,7 +16,7 @@ If you want to configure a process to automatically start and run on a particula
 > ### Remember:  
 > -   When you deploy or undeploy an integration flow with *Scheduler*, the system automatically releases all the scheduler locks.
 > 
-> -   When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered. When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered.
+> -   When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered.
 > 
 > -   If the *Timer* is configured to trigger message processing at periodic intervals and the processing isn’t completed before the next scheduled interval, then the *Timer* skips the following interval.
 >