From f94499161c611d7d23c3c24ed7918f34196c2334 Mon Sep 17 00:00:00 2001
From: dwlhs <31095845+dwlhs@users.noreply.github.com>
Date: Tue, 8 Aug 2023 13:53:09 +0200
Subject: [PATCH] Update understanding-http-authentication.md

Removed paranthesis
---
 .../wcf/feature-details/understanding-http-authentication.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/framework/wcf/feature-details/understanding-http-authentication.md b/docs/framework/wcf/feature-details/understanding-http-authentication.md
index 19f185337d866..610e77846d1d8 100644
--- a/docs/framework/wcf/feature-details/understanding-http-authentication.md
+++ b/docs/framework/wcf/feature-details/understanding-http-authentication.md
@@ -31,7 +31,7 @@ Authentication is the process of identifying who the client is, typically to det
   
 - If the resource needs to be protected, consider which authentication schemes provide the required level of security. The weakest standard authentication scheme discussed here's Basic authentication. Basic authentication doesn't protect the user's credentials. The strongest standard authentication scheme is Negotiate authentication, resulting in the Kerberos protocol.  
   
-- A server shouldn't present, for example, in the WWW-Authentication headers), any scheme that it isn't prepared to accept or that doesn't adequately secure the protected resource. Clients are free to choose between any of the authentication schemes the server presents. Some clients default to a weak authentication scheme or the first authentication scheme in the server's list.  
+- A server shouldn't present, for example, in the WWW-Authentication headers, any scheme that it isn't prepared to accept or that doesn't adequately secure the protected resource. Clients are free to choose between any of the authentication schemes the server presents. Some clients default to a weak authentication scheme or the first authentication scheme in the server's list.  
   
 ## See also