Merge pull request #52831 from Delapouite/patch-1

fix(event-hubs): correct typo rouge → rogue

Author: ktoliver

articles/event-hubs/authenticate-shared-access-signature.md

@@ -18,7 +18,7 @@ Shared access signature (SAS) gives you granular control over the type of access
 - The permissions granted by the SAS. For example, a SAS for an Event Hubs namespace might grant the listen permission, but not the send permission.
 - Only clients that present valid credentials can send data to an event hub.
 - A client can't impersonate another client.
-- A rouge client can be blocked from sending data to an event hub.
+- A rogue client can be blocked from sending data to an event hub.
 
 This article covers authenticating the access to Event Hubs resources using SAS. To learn about **authorizing** access to Event Hubs resources using SAS, see [this article](authorize-access-shared-access-signature.md). 
 
@@ -230,4 +230,4 @@ See the following related articles:
 - [Authenticate requests to Azure Event Hubs from an application using Azure Active Directory](authenticate-application.md)
 - [Authenticate a managed identity with Azure Active Directory to access Event Hubs Resources](authenticate-managed-identity.md)
 - [Authorize access to Event Hubs resources using Azure Active Directory](authorize-access-azure-active-directory.md)
-- [Authorize access to Event Hubs resources using Shared Access Signatures](authorize-access-shared-access-signature.md)
+- [Authorize access to Event Hubs resources using Shared Access Signatures](authorize-access-shared-access-signature.md)