From bc05d7e4c91302151b73fff7806a940cf11e0f09 Mon Sep 17 00:00:00 2001
From: Zachary Becker <111648125+zjbecker@users.noreply.github.com>
Date: Mon, 25 Nov 2024 15:31:20 +0000
Subject: [PATCH] Update data-retention-overview.md

typo
---
 powerapps-docs/maker/data-platform/data-retention-overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/powerapps-docs/maker/data-platform/data-retention-overview.md b/powerapps-docs/maker/data-platform/data-retention-overview.md
index e7b4cadbc1..4106d851f6 100644
--- a/powerapps-docs/maker/data-platform/data-retention-overview.md
+++ b/powerapps-docs/maker/data-platform/data-retention-overview.md
@@ -107,7 +107,7 @@ Dataverse long term retention requires no additional storage purchases and it do
 For example:
 
 - Suppose the database capacity consumed by Contoso is 1,000 GB today and the scheduled long term retention policy was run and retains 200 GB of data with Dataverse long term retention.
-- With an average compression of at lease 50%, the retained data size is 100 GB, a savings of 50% compared to when the data was in the active state.
+- With an average compression of at least 50%, the retained data size is 100 GB, a savings of 50% compared to when the data was in the active state.
 - This implies Contoso now has 800 GB of active data and 100 GB of inactive data in Dataverse.
 - In this scenario, the [storage capacity reports](#storage-capacity-reports) display the database usage as 900 GB (800 GB + 100 GB).