From 9b5ce2ca19d56ba9e3265dc1656fa12033abadcd Mon Sep 17 00:00:00 2001
From: adirdidi <68847945+adirdidi@users.noreply.github.com>
Date: Wed, 10 Mar 2021 19:48:14 +0200
Subject: [PATCH] Update production-deployment.md

---
 .../microsoft-defender-atp/production-deployment.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md
index 3abbeec81e..5a69318c36 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/production-deployment.md
@@ -242,7 +242,7 @@ Defender for Endpoint is built in Azure cloud, deployed in the following regions
 You can find the Azure IP ranges in [Azure IP Ranges and Service Tags – Public Cloud](https://www.microsoft.com/download/details.aspx?id=56519).
 
 > [!NOTE]
-> As a cloud-based solution, the IP address ranges can change. It's recommended you move to a DNS-based rules.
+> As a cloud-based solution, the IP address ranges can change. It's recommended you move to DNS-based rules.
 
 > [!NOTE]
 > If you are a US Government customer, please see the corresponding section in the [Defender for Endpoint for US Government](gov.md#service-backend-ip-ranges) page.