fixed broken links

Author: spelluru

articles/event-grid/event-domains.md

@@ -27,7 +27,7 @@ Event domains make available to you the same architecture used by Azure services
 
 ### Example use case
 
-Event domains are most easily explained using an example. Let’s say you run Contoso Construction Machinery, where you manufacture tractors, digging equipment, and other heavy machinery. As a part of running the business, you push real-time information to customers about equipment maintenance, systems health, and contract updates. All of this information goes to various endpoints including your app, customer endpoints, and other infrastructure that customers have set up.
+Event domains are most easily explained using an example. Let's say you run Contoso Construction Machinery, where you manufacture tractors, digging equipment, and other heavy machinery. As a part of running the business, you push real-time information to customers about equipment maintenance, systems health, and contract updates. All of this information goes to various endpoints including your app, customer endpoints, and other infrastructure that customers have set up.
 
 Event domains allow you to model Contoso Construction Machinery as a single eventing entity. Each of your customers is represented as a topic within the domain. Authentication and authorization are handled using Azure Active Directory. Each of your customers can subscribe to their topic and get their events delivered to them. Managed access through the event domain ensures they can only access their topic.
 
@@ -39,13 +39,13 @@ It also gives you a single endpoint, which you can publish all of your customer
 
 With a domain, you get fine grain authorization and authentication control over each topic via Azure's role-based access control (RBAC). You can use these roles to restrict each tenant in your application to only the topics you wish to grant them access to.
 
-RBAC in event domains works the same way [managed access control](security-authentication.md#management-access-control) works in the rest of Event Grid and Azure. Use RBAC to create and enforce custom role definitions in event domains.
+RBAC in event domains works the same way [managed access control](security-authorization.md) works in the rest of Event Grid and Azure. Use RBAC to create and enforce custom role definitions in event domains.
 
 ### Built in roles
 
 Event Grid has two built-in role definitions to make RBAC easier for working with event domains. These roles are **EventGrid EventSubscription Contributor (Preview)** and **EventGrid EventSubscription Reader (Preview)**. You assign these roles to users who need to subscribe to topics in your event domain. You scope the role assignment to only the topic that users need to subscribe to.
 
-For information about these roles, see [Built-in roles for Event Grid](security-authentication.md#built-in-roles).
+For information about these roles, see [Built-in roles for Event Grid](security-authorization.md#built-in-roles).
 
 ## Subscribing to topics