From 572f833d9637e12a4e4854c8e1536777096c1727 Mon Sep 17 00:00:00 2001
From: PeishanFromMixpanel
 <129823695+PeishanFromMixpanel@users.noreply.github.com>
Date: Sat, 1 Feb 2025 01:16:16 +0800
Subject: [PATCH] Update warehouse-connectors.mdx

updated grammar - changed to "loses" from "looses" in the sentence "... This ensures that the snapshots are deleted even if Mixpanel loses access to them unexpectedly"
---
 pages/docs/tracking-methods/warehouse-connectors.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/docs/tracking-methods/warehouse-connectors.mdx b/pages/docs/tracking-methods/warehouse-connectors.mdx
index 48758c95d1..bedfb3c74c 100644
--- a/pages/docs/tracking-methods/warehouse-connectors.mdx
+++ b/pages/docs/tracking-methods/warehouse-connectors.mdx
@@ -370,7 +370,7 @@ change stream between two snapshot. Snapshots are stored in the `mixpanel` datas
   and Mixpanel will consider them the same row causing only one copy to appear in Mixpanel. We recommend ensuring that one
   of your columns is a unique row ID to avoid this.
 - The table snapshots managed by Mixpanel are always created to expire after 21 days. This ensures that the snapshots are
-  deleted even if Mixpanel looses access to them unexpectedly. Make sure that the sync does not go longer than 21 days without
+  deleted even if Mixpanel loses access to them unexpectedly. Make sure that the sync does not go longer than 21 days without
   running as each sync run needs access to the previous sync run's snapshot. (Under normal conditions Mirror maintains only one
   snapshot per-sync and removes the older run's snapshot as soon as it has been used by the subsequent sync run).