Update event-overview.md: added david's suggestions

Author: t-vnamani

articles/governance/policy/concepts/event-overview.md

@@ -32,15 +32,15 @@ Event Grid has a few benefits for customers and services in the Azure ecosystem:
 - Durable delivery:  In order for services and user applications to respond in real-time to policy compliance events,
   Event Grid seeks to offer policy events with minimum latency. Event Grid retries transmission of an event if a subscriber's
   endpoint fails to acknowledge receipt of it or if it doesn't, according to a predetermined retry schedule and retry policy.
-- Custom event producer: Event Grid  event producers and consumers do not need to be Azure or Microsoft services.
+- Custom event producer: Event Grid  event producers and consumers don't need to be Azure or Microsoft services.
   External applications can receive an alert, show the creation of a remediation task or collect messages on who responds to the
   state change.	
 See
 [Route policy state change events to Event Grid with Azure CLI](../tutorials/route-state-change-events.md)
 for a full tutorial.
 
 There are two primary entities when using Event Grid: 
-- Events: These events can be anything a user may want to react to – includes if a policy compliance state is
+- Events: These events can be anything a user may want to react to that includes if a policy compliance state is
    created, changed, and deleted of a resource such as a VM or storage accounts.
 - Event Grid Subscriptions: These event subscriptions are user configured entities that direct the proper set of events
   from a publisher to a subscriber. Event subscriptions can filter events based on the resource path the event
@@ -51,17 +51,17 @@ A common Azure Policy event scenario is tracking when the compliance state of a
 during policy evaluation. Event-based architecture is an efficient way to react to these changes
 and aids in the event based reaction to compliance state changes.
 
-Another scenario is to automatically trigger remediation tasks without manually ticking off 'create 
-remediation task' on the policy page. Event Grid checks for compliance state and resources that are currently 
+Another scenario is to automatically trigger remediation tasks without manually ticking off _create 
+remediation task_ on the policy page. Event Grid checks for compliance state and resources that are currently 
 noncompliant can be remedied. Learn more about [remediation structure](../concepts/remediation-structure.md).
-  > Remediation requires a managed identity and policies must be in Modify or DeployIfNotExists effect. [Learn more about
-effect types](../how-to//remediate-resources.md).
+Remediation requires a managed identity and policies must be in Modify or DeployIfNotExists effect. [Learn more about
+effect types](../how-to/remediate-resources.md).
 
 Additionally, Event Grid is helpful as an audit system to store state changes and understand cause of noncompliance over 
 time. The scenarios for Event Grid are endless and based on the motivation, Event Grid is configurable. 
 
 
-:::image type="content" source="../../../event-grid/media/overview/functional-model.png" alt-text="Event Grid model of sources and handlers" lightbox="../../../event-grid/media/overview/functional-model-big.png":::
+:::image type="content" source="../../../event-grid/media/overview/functional-model.png" alt-text="Screenshot of Event Grid model of sources and handlers." lightbox="../../../event-grid/media/overview/functional-model-big.png":::
 
 [!INCLUDE [policy-events.md](../../../../includes/policy/policy-events.md)]