acrolinx junk 5

Author: banisadr

articles/event-grid/partner-onboarding-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Onboard as a Event Grid Partner
+title: Onboard as an Event Grid Partner
 description: Onboard as an Azure Event Grid Partner Topic Type. Understand the resource model and publishing flow for Partner Topics.
 services: event-grid
 author: banisadr
@@ -12,16 +12,16 @@ ms.author: babanisa
 
 # Become and Event Grid partner
 
-This article describes how to privately use the Event Grid partner resources as well as how to become a publicly available Partner Topic Type.
+This article describes how to privately use the Event Grid partner resources and how to become a publicly available Partner Topic Type.
 
-You do not need special permission to begin using the Event Grid resource types associated with publishing events as an Event Grid partner. In fact, you can use them today both to publish events privately to your own Azure Subscriptions, as well as to test out the resource model if you are considering becoming a partner.
+You don't need special permission to begin using the Event Grid resource types associated with publishing events as an Event Grid partner. In fact, you can use them today both to publish events privately to your own Azure Subscriptions, and to test out the resource model if you're considering becoming a partner.
 
 ## Becoming an Event Grid partner
 
-If you are interested in becoming a public Event Grid partner, please begin by filling out [this form](https://aka.ms/gridpartnerform), and then contacting the Event Grid team at [[email protected]](mailto:[email protected]).
+If you're interested in becoming a public Event Grid partner, begin by filling out [this form](https://aka.ms/gridpartnerform), and then contacting the Event Grid team at [[email protected]](mailto:[email protected]).
 
 ## How partner topics work
-Partner Topics take the existing architecture that Event Grid already uses in to publish events from Azure resoruces such as Storage and IoT Hub, and makes those tools publicly available for anyone to use. Using these tools is by default private to your Azure Subscription only. In order to make your events publicly available, please fill out the above form and [contact the Event Grid team](mailto:[email protected]).
+Partner Topics take the existing architecture that Event Grid already uses in to publish events from Azure resoruces such as Storage and IoT Hub, and makes those tools publicly available for anyone to use. Using these tools is by default private to your Azure Subscription only. To make your events publicly available, fill out the above form and [contact the Event Grid team](mailto:[email protected]).
 
 Partner topics allow you to publish events to Azure Event Grid for multitenant consumption.
 
@@ -30,17 +30,17 @@ Partner topics allow you to publish events to Azure Event Grid for multitenant c
 #### Partner flow
 
 1. Create an Azure tenant if you don't already have one.
-1. Using CLI create a new Event Grid `partnerRegistration`. This includes information such as display name, description, setup URI etc. 
+1. Using CLI create a new Event Grid `partnerRegistration`. This resource includes information such as display name, description, setup URI and so on. 
 ![Create Partner Topic](./media/partner-onboarding-how-to/createPartnerRegistration.png)
-1. Create one or more `partnerNamespaces` in each region you want to publish events. As part of this, Event Grid service will provision a publishing endpoint (e.g. https://contoso.westus-1.eventgrid.azure.net/api/events) and access keys.
+1. Create one or more `partnerNamespaces` in each region you want to publish events. As part of this, Event Grid service will provision a publishing endpoint (for example, https://contoso.westus-1.eventgrid.azure.net/api/events) and access keys.
 ![Create Partner Namespace](./media/partner-onboarding-how-to/createPartnerNamespace.png)
 1. Provide a way for customers to register in your system that they would like a partner topic.
-1. Contact the Event Grid team to let us know you would like your Partner Topic Type to become public. This will kickoff a review process.
+1. Contact the Event Grid team to let us know you would like your Partner Topic Type to become public.
 
 #### Customer flow
 
 1. Your customer will visit the Azure Portal to note the Azure Subscription ID and Resource Group they would like the Partner Topic created in.
-1. The customer will request a Partner Topic via your system. In response you will create an Event Tunnel your Partner Namespace.
+1. The customer will request a Partner Topic via your system. In response, you'll create an Event Tunnel your Partner Namespace.
 1. Event Grid will create a **Pending** Partner Topic in the customer's Azure Subscription and Resoruce Group.
 ![Create Event Channel](./media/partner-onboarding-how-to/createEventTunnelPartnerTopic.png)
 1. The customer activates the Partner Topic via the Azure Portal. Events may now flow from your service to the customer's Azure Subscription.
@@ -53,9 +53,9 @@ Below is the resource model for Partner Topics.
 ### Partner Registrations
 * Resource: `partnerRegistrations`
 * Used by: Partners
-* Description: Captures the global metadata of the SaaS partner (e.g. name, display name, description, setup URI).
+* Description: Captures the global metadata of the SaaS partner (for example, name, display name, description, setup URI).
 
-    Creating/updating a partner registration is a self-serve operation for the partners. This enables partners to build and test the complete end to end flow.
+    Creating/updating a partner registration is a self-serve operation for the partners. This self-serve ability enables partners to build and test the complete end to end flow.
 
     Only Microsoft approved partnerRegistrations are discoverable by customers.
 * Scope: Created in partner's Azure Subscription. Metadata visible to customers once public.
@@ -70,41 +70,41 @@ Below is the resource model for Partner Topics.
 ### Partner Namespaces
 * Resource: partnerNamespaces
 * Used by: Partners
-* Description: Provides a regional resource for publishing customer events to. Each Partner Namespace has a publishing endpoint and auth keys. The namespace is also how the partner requests a Partner Topic for a given customer as well as lists active customers.
+* Description: Provides a regional resource for publishing customer events to. Each Partner Namespace has a publishing endpoint and auth keys. The namespace is also how the partner requests a Partner Topic for a given customer and lists active customers.
 * Scope: Lives in partner’s subscription.
 
 ### Event Tunnels
 * Resource: `partnerNamespaces/eventTunnels`
 * Used by: Partners
-* Description: The Event Tunnels are a mirror of the customer's Partner Topic. By creating an Event Tunnel and specifying the customer's Azure Subscription and resource Group in the metadata, you are signaling to Event Grid to create a Partner Topic on behalf of the customer. Event Grid will issue an ARM call to create a corresponding partnerTopic in the customer’s subscription. The partner topic will be created in a "pending" state. There’s a 1-1 link between each eventTunnel and a partnerTopic.
+* Description: The Event Tunnels are a mirror of the customer's Partner Topic. By creating an Event Tunnel and specifying the customer's Azure Subscription and resource Group in the metadata, you're signaling to Event Grid to create a Partner Topic for the customer. Event Grid will issue an ARM call to create a corresponding partnerTopic in the customer’s subscription. The partner topic will be created in a "pending" state. There’s a 1-1 link between each eventTunnel and a partnerTopic.
 * Scope: Lives in partner’s subscription.
 
 ### Partner Topics
 * Resource: `partnerTopics`
 * Used by: Customers
-* Description: Partner Topics are similar to Custom Topic and System topic in Event Grid. Each Partner Topic is associated with a specific “source” (e.g. “Contoso:myaccount”) and a specific partner topic type  (e.g. “Contoso”). Customers create Event Subscriptions on the Partner Topic to route events to various event handlers.
+* Description: Partner Topics are similar to Custom Topic and System topic in Event Grid. Each Partner Topic is associated with a specific “source” (for example, `Contoso:myaccount`) and a specific partner topic type  (for example, “Contoso”). Customers create Event Subscriptions on the Partner Topic to route events to various event handlers.
 
-    Note that customers cannot directly create this resource. The only way to create this is be through a partner operation creating an Event Tunnel.
+    Customers can't directly create this resource. The only way to create a Partner Topic is through a partner operation creating an Event Tunnel.
 * Scope: Lives in customer’s subscription.
 
 ### Partner Topic Types
 * Resource: `partnerTopicTypes`
 * Used by: Customers
-* Description: This is a tenant wide resource type to enable customers to discover the list of approved partner topic types . The URL will look as follows: https://management.azure.com/providers/Microsoft.EventGrid/partnerTopicTypes)
+* Description: Partner Topic Types are tenant-wide resource types that enable customers to discover the list of approved partner topic types. The URL will look as follows: https://management.azure.com/providers/Microsoft.EventGrid/partnerTopicTypes)
 * Scope: Global
 
 ## Publishing Events to Event Grid
-When a you create a partnerNamespace in an Azure region, you will get a regional endpoint and corresponding auth keys. Publish batches of events to this endpoint for all customer Event Tunnels in that namespace. Based on the “source” field in the event, Azure Event Grid will map each event with the corresponding partner topic(s).
+When you create a partnerNamespace in an Azure region, you'll get a regional endpoint and corresponding auth keys. Publish batches of events to this endpoint for all customer Event Tunnels in that namespace. Based on the “source” field in the event, Azure Event Grid will map each event with the corresponding partner topic(s).
 
 ### Event Schema: CloudEvents v1.0
 Publish events to Azure Event Grid using the CloudEvents 1.0 schema. Event Grid supports both structured mode and batched mode. CloudEvents 1.0 is the only supported event schema for Partner Namespaces.
 
 ### Example Flow
 
-1.	The publishing service does a HTTP POST to https://contoso.westus2-1.eventgrid.azure.net/api/events?api-version=2018-01-01.
-2.	In the request, include a header value named aeg-sas-key that contains a key for authentication. This is the key provisioned during the creation of the partnerNamespace. For example, a valid header value is aeg-sas-key: VXbGWce53249Mt8wuotr0GPmyJ/nDT4hgdEj9DpBeRr38arnnm5OFg==.
+1.	The publishing service does an HTTP POST to https://contoso.westus2-1.eventgrid.azure.net/api/events?api-version=2018-01-01.
+2.	In the request, include a header value named aeg-sas-key that contains a key for authentication. This key is provisioned during the creation of the partnerNamespace. For example, a valid header value is aeg-sas-key: VXbGWce53249Mt8wuotr0GPmyJ/nDT4hgdEj9DpBeRr38arnnm5OFg==.
 3.	Set the Content-Type header to “application/cloudevents-batch+json; charset=UTF-8”.
-4.	Perform a HTTP POST to the above publish URL with a batch of events corresponding to that region. For example:
+4.	Perform an HTTP POST to the above publish URL with a batch of events corresponding to that region. For example:
 
 ``` json
 [
@@ -139,7 +139,7 @@ Publish events to Azure Event Grid using the CloudEvents 1.0 schema. Event Grid
 ]
 ```
 
-After posting to the partnerNamespace endpoint, you will receive a response. The response is a standard HTTP response code. Some common responses are:
+After posting to the partnerNamespace endpoint, you'll receive a response. The response is a standard HTTP response code. Some common responses are:
 |Result | Response |
 |-------|----------|
 | Success | 200 OK |