fixed broken links

Author: spelluru

articles/event-grid/.openpublishing.redirection.event-grid.json

@@ -130,11 +130,6 @@
       "redirect_url": "/azure/event-grid/faq",
       "redirect_document_id": false
     },          
-    {
-      "source_path": "edge/toc.yml",
-      "redirect_url": "/azure/event-grid/faq",
-      "redirect_document_id": false
-    },          
     {
       "source_path": "edge/forward-events-event-grid-cloud.md",
       "redirect_url": "/azure/event-grid/edge/forward-events-cloud",

articles/event-grid/transition.md

@@ -12,7 +12,7 @@ On March 31, 2023, Azure Event Grid on Azure IoT Edge will be retired. Be sure t
 
 ## Why are we retiring it?
 
-There's one major reason to retire Event Grid on IoT Edge, which is currently in preview, in March 2023: Event Grid has been evolving in the cloud native space to provide more robust capabilities not only in Azure but also in on-premises scenarios with [Kubernetes with Azure Arc](../kubernetes/overview.md).
+There's one major reason to retire Event Grid on IoT Edge, which is currently in preview, in March 2023: Event Grid has been evolving in the cloud native space to provide more robust capabilities not only in Azure but also in on-premises scenarios with [Kubernetes with Azure Arc](./kubernetes/overview.md).
 
 | Event Grid on IoT Edge | IoT Edge hub |
 | ---------------------------- | ----------------------------- | 
@@ -22,17 +22,16 @@ There's one major reason to retire Event Grid on IoT Edge, which is currently in
 
 To use the IoT Edge features, follow these steps:
 
-1. Learn about the feature differences between [Event Grid on IoT Edge](overview.md#when-to-use-event-grid-on-iot-edge) and [IoT Edge](../../iot-edge/how-to-publish-subscribe.md).
-2. Identify your scenario based on the feature table in the next section.
-3. Follow the documentation to change your architecture and make code changes based on the scenario you want to transition.
-4. Validate your updated architecture by sending and receiving messages/events.
+1. Identify your scenario based on the feature table in the next section.
+2. Follow the documentation to change your architecture and make code changes based on the scenario you want to transition.
+3. Validate your updated architecture by sending and receiving messages/events.
 
 ## Event Grid on IoT Edge vs. IoT Edge
 
 The following table highlights the key differences during this transition.
 
 | Event Grid on IoT Edge | IoT Edge |
 | --- | ----------- |
-| Publish, subscribe, and forward events locally or to the cloud | Use the message routing feature in the IoT Edge hub to facilitate local and cloud communication. It enables device-to-module, module-to-module, and device-to-device communications by brokering messages to keep devices and modules independent from each other. To learn more, see [Using routing for an IoT Edge hub](../../iot-edge/iot-edge-runtime.md#using-routing). </br> </br> If you're subscribing to an IoT Edge hub, it's possible to create an event to publish to Event Grid, if needed. For details, see [Azure IoT Hub and Event Grid on IoT Edge](../../iot-hub/iot-hub-event-grid.md). |
-| Forward events to IoT Hub | Use the IoT Edge hub to optimize connections when sending messages to the cloud with offline support. For details, see [IoT Edge hub cloud communication](../../iot-edge/iot-edge-runtime.md#using-routing). |
-| React to Blob Storage events on IoT Edge (preview) | You can use Azure function apps to react to Blob Storage events on the cloud when a blob is created or updated. For more information, see [Azure Blob Storage trigger for Azure Functions](../../azure-functions/functions-bindings-storage-blob-trigger.md) and [Tutorial: Deploy Azure Functions as modules - Azure IoT Edge](../../iot-edge/tutorial-deploy-function.md). Blob triggers in an IoT Edge Blob Storage module aren't supported. |
+| Publish, subscribe, and forward events locally or to the cloud | Use the message routing feature in the IoT Edge hub to facilitate local and cloud communication. It enables device-to-module, module-to-module, and device-to-device communications by brokering messages to keep devices and modules independent from each other. </br> </br> If you're subscribing to an IoT Edge hub, it's possible to create an event to publish to Event Grid, if needed. For details, see [Azure IoT Hub and Event Grid on IoT Edge](../iot-hub/iot-hub-event-grid.md). |
+| Forward events to IoT Hub | Use the IoT Edge hub to optimize connections when sending messages to the cloud with offline support. For details, see [IoT Edge hub cloud communication](../iot-edge/iot-edge-runtime.md#using-routing). |
+| React to Blob Storage events on IoT Edge (preview) | You can use Azure function apps to react to Blob Storage events on the cloud when a blob is created or updated. For more information, see [Azure Blob Storage trigger for Azure Functions](../azure-functions/functions-bindings-storage-blob-trigger.md) and [Tutorial: Deploy Azure Functions as modules - Azure IoT Edge](../iot-edge/tutorial-deploy-function.md). Blob triggers in an IoT Edge Blob Storage module aren't supported. |