Merge pull request #220279 from spelluru/egridschema1202

review and update schema articles - 2

Author: Maggiemouse1

articles/azure-maps/azure-maps-event-grid-integration.md

@@ -24,7 +24,7 @@ Azure Event Grid is a fully managed event routing service, which uses a publish-
 
 ## Azure Maps events types
 
-Event grid uses [event subscriptions](../event-grid/concepts.md#event-subscriptions) to route event messages to subscribers. An Azure Maps account emits the following event types:
+Event Grid uses [event subscriptions](../event-grid/concepts.md#event-subscriptions) to route event messages to subscribers. An Azure Maps account emits the following event types:
 
 | Event type | Description |
 | ---------- | ----------- |
@@ -75,6 +75,7 @@ Applications that handle Azure Maps geofence events should follow a few recommen
 * When a GET or a POST request in the Geofence API is called with the mode parameter set to `EnterAndExit`, then an Enter or Exit event is generated for each geometry in the geofence for which the status has changed from the previous Geofence API call.
 
 ## Next steps
+For details about all the events supported by Azure Maps and the schema, see [Azure Maps as an Event Grid source](../event-grid/event-schema-azure-maps.md).
 
 To learn more about how to use geofencing to control operations at a construction site, see:
 

articles/event-grid/event-grid-event-hubs-integration.md

@@ -13,8 +13,7 @@ Azure [Event Grid](overview.md) is an intelligent event routing service that ena
 [!INCLUDE [event-grid-event-hubs-functions-synapse-analytics.md](./includes/event-grid-event-hubs-functions-synapse-analytics.md)]
 
 ## Next steps
-
-* To learn about differences in the Azure messaging services, see [Choose between Azure services that deliver messages](compare-messaging-services.md).
-* For an introduction to Event Grid, see [About Event Grid](overview.md).
-* For an introduction to Event Hubs Capture, see [Enable Event Hubs Capture using the Azure portal](../event-hubs/event-hubs-capture-enable-through-portal.md).
 * For more information about setting up and running the sample, see [Event Hubs Capture and Event Grid sample](https://github.com/Azure/azure-event-hubs/tree/master/samples/e2e/EventHubsCaptureEventGridDemo).
+* In this tutorial, you created an event subscription for the `CaptureFileCreated` event. For more information about this event and all the events supported by Azure Blob Storage, see [Azure Event Hubs as an Event Grid source](event-schema-event-hubs.md). 
+* To learn more about the Event Hubs Capture feature, see [Capture events through Azure Event Hubs in Azure Blob Storage or Azure Data Lake Storage](../event-hubs/event-hubs-capture-overview.md).
+* To learn about differences in the Azure messaging services, see [Choose between Azure services that deliver messages](compare-messaging-services.md).

articles/event-grid/event-schema-aks.md

@@ -3,13 +3,13 @@ title: Azure Kubernetes Service as Event Grid source
 description: This article describes how to use Azure Kubernetes Service as an Event Grid event source. It provides the schema and links to tutorial and how-to articles. 
 author: zr-msft
 ms.topic: conceptual
-ms.date: 10/04/2021
+ms.date: 12/02/2022
 ms.author: zarhoads
 ---
 
 # Azure Kubernetes Service (AKS) as an Event Grid source
 
-This article provides the properties and schema for AKS events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md). It also gives you a list of quick starts and tutorials to use AKS as an event source.
+This article provides the properties and schema for AKS events. It also gives you a list of quick starts and tutorials to use AKS as an event source. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md) and [Cloud event schema](cloud-event-schema.md).
 
 ## Available event types
 
@@ -108,6 +108,4 @@ The data object contains the following properties:
 | `latestPreviewKubernetesVersion`   | string | The latest preview version of Kubernetes available.          |
 
 ## Next steps
-
-* For an introduction to Azure Event Grid, see [What is Event Grid?](overview.md)
-* For more information about creating an Azure Event Grid subscription, see [Event Grid subscription schema](subscription-creation-schema.md)
+See the following tutorial: [Quickstart: Subscribe to Azure Kubernetes Service (AKS) events with Azure Event Grid](../aks/quickstart-event-grid.md).

articles/event-grid/event-schema-azure-health-data-services.md

@@ -2,7 +2,7 @@
 title: Azure Health Data Services as Event Grid source
 description: Describes the properties that are provided for Azure Health Data Services events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 02/03/2022
+ms.date: 12/02/2022
 ---
 
 # Azure Health Data Services as an Event Grid source
@@ -156,8 +156,7 @@ This section contains examples of what events message data would look like for e
 ---
 
 ## Next steps
-
-* For an introduction to Azure Event Grid, see [What is Event Grid?](overview.md)
-* For more information about creating an Azure Event Grid subscription, see [Event Grid subscription schema](subscription-creation-schema.md). 
+See the following tutorial: [Deploy Events using the Azure portal](../healthcare-apis/events/events-deploy-portal.md).
+ 
 
 (FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

articles/event-grid/event-schema-azure-maps.md

@@ -2,7 +2,7 @@
 title: Azure Maps as Event Grid source
 description: Describes the properties and schema provided for Azure Maps events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 09/15/2021
+ms.date: 12/02/2022
 ---
 
 # Azure Maps as an Event Grid source

articles/event-grid/event-schema-azure-signalr.md

@@ -2,7 +2,7 @@
 title: Azure SignalR as Event Grid source
 description: Describes the properties that are provided for Azure SignalR events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 09/15/2021
+ms.date: 12/02/2022
 ---
 
 # Azure Event Grid event schema for SignalR Service

articles/event-grid/event-schema-event-hubs.md

@@ -2,7 +2,7 @@
 title: Azure Event Hubs as Event Grid source
 description: Describes the properties that are provided for event hubs events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 09/15/2021
+ms.date: 12/02/2022
 ---
 
 # Azure Event Hubs as an Event Grid source

articles/event-grid/event-schema-iot-hub.md

@@ -2,7 +2,7 @@
 title: Azure IoT Hub as Event Grid source
 description: This article provides the properties and schema for Azure IoT Hub events. It lists the available event types, an example event, and event properties.  
 ms.topic: conceptual
-ms.date: 09/15/2021
+ms.date: 12/02/2022
 ---
 
 # Azure IoT Hub as an Event Grid source
@@ -24,7 +24,7 @@ Azure IoT Hub emits the following event types:
 
 # [Event Grid event schema](#tab/event-grid-event-schema)
 
-The schema for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
+The schemas for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
 
 ```json
 [{
@@ -81,7 +81,7 @@ The DeviceTelemetry event is raised when a telemetry event is sent to an IoT Hub
 }]
 ```
 
-The schema for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
+The schemas for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
 
 ```json
 [{
@@ -131,7 +131,7 @@ The schema for DeviceCreated and DeviceDeleted events have the same structure. T
 
 # [Cloud event schema](#tab/cloud-event-schema)
 
-The schema for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
+The schemas for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
 
 ```json
 [{
@@ -186,7 +186,7 @@ The DeviceTelemetry event is raised when a telemetry event is sent to an IoT Hub
 }]
 ```
 
-The schema for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
+The schemas for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
 
 ```json
 [{
@@ -245,7 +245,7 @@ All events contain the same top-level data:
 | Property | Type | Description |
 | -------- | ---- | ----------- |
 | `id` | string | Unique identifier for the event. |
-| `topic` | string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
+| `topic` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
 | `subject` | string | Publisher-defined path to the event subject. |
 | `eventType` | string | One of the registered event types for this event source. |
 | `eventTime` | string | The time the event is generated based on the provider's UTC time. |
@@ -261,7 +261,7 @@ All events contain the same top-level data:
 | Property | Type | Description |
 | -------- | ---- | ----------- |
 | `id` | string | Unique identifier for the event. |
-| `source` | string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
+| `source` | string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
 | `subject` | string | Publisher-defined path to the event subject. |
 | `type` | string | One of the registered event types for this event source. |
 | `time` | string | The time the event is generated based on the provider's UTC time. |
@@ -293,7 +293,7 @@ For **Device Telemetry** IoT Hub event, the data object contains the device-to-c
 | -------- | ---- | ----------- |
 | `body` | string | The content of the message from the device. |
 | `properties` | string | Application properties are user-defined strings that can be added to the message. These fields are optional. |
-| `system properties` | string | [System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message system properties. If this is not set, then IoT Hub will write the messages in base 64 encoded format.  |
+| `system properties` | string | [System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message system properties. If this isn't set, then IoT Hub will write the messages in base 64 encoded format.  |
 
 For **Device Created** and **Device Deleted** IoT Hub events, the data object contains the following properties:
 
@@ -303,13 +303,13 @@ For **Device Created** and **Device Deleted** IoT Hub events, the data object co
 | `deviceID` | string | The unique identifier of the device twin. | 
 | `etag` | string | A validator for ensuring consistency of updates to a device twin. Each etag is guaranteed to be unique per device twin. |  
 | `deviceEtag` | string | A validator for ensuring consistency of updates to a device registry. Each deviceEtag is guaranteed to be unique per device registry. |
-| `status` | string | Whether the device twin is enabled or disabled. | 
+| `status` | string | Indicates whether the device twin is enabled or disabled. | 
 | `statusUpdateTime` | string | The ISO8601 timestamp of the last device twin status update. |
-| `connectionState` | string | Whether the device is connected or disconnected. | 
+| `connectionState` | string | Indicates whether the device is connected or disconnected. | 
 | `lastActivityTime` | string | The ISO8601 timestamp of the last activity. | 
 | `cloudToDeviceMessageCount` | integer | Count of cloud to device messages sent to this device. | 
 | `authenticationType` | string | Authentication type used for this device: either `SAS`, `SelfSigned`, or `CertificateAuthority`. |
-| `x509Thumbprint` | string | The thumbprint is a unique value for the x509 certificate, commonly used to find a particular certificate in a certificate store. The thumbprint is dynamically generated using the SHA1 algorithm, and does not physically exist in the certificate. | 
+| `x509Thumbprint` | string | The thumbprint is a unique value for the x509 certificate, commonly used to find a particular certificate in a certificate store. The thumbprint is dynamically generated using the SHA1 algorithm, and doesn't physically exist in the certificate. | 
 | `primaryThumbprint` | string | Primary thumbprint for the x509 certificate. |
 | `secondaryThumbprint` | string | Secondary thumbprint for the x509 certificate. | 
 | `version` | integer | An integer that is incremented by one each time the device twin is updated. |

articles/event-grid/event-schema-machine-learning.md

@@ -2,7 +2,7 @@
 title: Azure Machine Learning as Event Grid source
 description: Describes the properties that are provided for Machine Learning Workspace events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 09/15/2021
+ms.date: 12/02/2022
 ---
 
 # Azure Machine Learning as an Event Grid source