Merge pull request #42923 from rcabr/patch-4

Updated section title 'Shared access signatures'

Author: ktoliver

articles/event-hubs/authorize-access-event-hubs.md

@@ -24,7 +24,7 @@ For more information about authenticating with Azure AD, see the following artic
 - [Authenticate requests to Azure Event Hubs using Azure Active Directory](authenticate-application.md)
 - [Authorize access to Event Hubs resources using Azure Active Directory](authorize-access-azure-active-directory.md).
 
-## Share access signatures 
+## Shared access signatures 
 Shared access signatures (SAS) for Event Hubs resources provide limited delegated access to Event Hubs resources. Adding constraints on time interval for which the signature is valid or on permissions it grants provides flexibility in managing resources. For more information, see [Authenticate using shared access signatures (SAS)](authenticate-shared-access-signature.md). 
 
 Authorizing users or applications using an OAuth 2.0 token returned by Azure AD provides superior security and ease of use over shared access signatures (SAS). With Azure AD, there's no need to store the access tokens with your code and risk potential security vulnerabilities. While you can continue to use shared access signatures (SAS) to grant fine-grained access to Event Hubs resources, Azure AD offers similar capabilities without the need to manage SAS tokens or worry about revoking a compromised SAS.