From cc940fc0ed8cb22727db60e46462a39b19721482 Mon Sep 17 00:00:00 2001
From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com>
Date: Fri, 13 Sep 2024 14:20:30 -0400
Subject: [PATCH] update

---
 .../identity-protection/hello-for-business/rdp-sign-in.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/security/identity-protection/hello-for-business/rdp-sign-in.md b/windows/security/identity-protection/hello-for-business/rdp-sign-in.md
index 31f02333d6..bc28fecee5 100644
--- a/windows/security/identity-protection/hello-for-business/rdp-sign-in.md
+++ b/windows/security/identity-protection/hello-for-business/rdp-sign-in.md
@@ -15,7 +15,7 @@ This article describes two certificate deployment approaches, where authenticati
 - Using an Active Directory Certificate Services (AD CS) enrollment policy
 
 >[!IMPORTANT]
-> If you deploying the certificate using Microsoft Intune, and you have [User Account Control](../../application-security/application-control/user-account-control/index.md) configure to *Prompt for credentials on the secure desktop* you won't be able to use the *run as* feature.
+> If you deploy the certificate using Microsoft Intune, and you have [User Account Control](../../application-security/application-control/user-account-control/index.md) configured to *Prompt for credentials on the secure desktop*, you won't be able to use the *run as* feature.
 > In such scenario, when you try to execute an application with elevated privileges and choose the Windows Hello for Business credential, you'll receive the error message: **The username or password is incorrect**.
 
 > [!TIP]