From 011cbbdae1acef476e0d0edee0c6c18f33a86ac1 Mon Sep 17 00:00:00 2001
From: andrea-mosk <39099407+andrea-mosk@users.noreply.github.com>
Date: Tue, 14 Jan 2025 18:11:39 +0100
Subject: [PATCH] Update content/en/dora_metrics/setup/deployments.md

Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>
---
 content/en/dora_metrics/setup/deployments.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/dora_metrics/setup/deployments.md b/content/en/dora_metrics/setup/deployments.md
index e12c97d9e813c..0bf5069659c45 100644
--- a/content/en/dora_metrics/setup/deployments.md
+++ b/content/en/dora_metrics/setup/deployments.md
@@ -254,7 +254,7 @@ If the two metadata entries are defined for a service, only `extensions[datadogh
 
 - Change lead time stage breakdown metrics are only available for GitHub.
 - Change lead time is not available for the first deployment of a service that includes Git information.
-- The maximum number of commits considered when computing Change Lead Time for a specific deployment is 5000.
+- The Change Lead Time calculation includes a maximum of 5000 commits per deployment.
 - For rebased branches, *change lead time* calculations consider the new commits created during the rebase, not the original commits.
 - When using "Squash" to merge pull requests:
   - For GitHub: Metrics are emitted for the original commits.