Fixed issues

spelluru · spelluru · commit 9f23d2fc2bbe · 2024-04-16T12:44:18.000-04:00
diff --git a/articles/event-grid/mqtt-automotive-connectivity-and-data-solution.md b/articles/event-grid/mqtt-automotive-connectivity-and-data-solution.md
@@ -81,7 +81,7 @@ Direct messages are executed with the minimum amount of hops for the best possib
 1. **Event Grid** checks for authorization for the Companion app Service to determine if it can send messages to the provided topics.
 1. Companion app subscribes to responses from the specific vehicle / command combination.
 
-In the case of vehicle state-dependent commands that require user consent **(B)**:
+When vehicle state-dependent commands require user consent **(B)**:
 
 1. The vehicle owner / user provides consent for the execution of command and control functions to a **digital service** (in this example a companion app). This is normally done when the user downloads/activate the app and the OEM activates their account. This triggers a configuration change on the vehicle to subscribe to the associated command topic in the MQTT broker.
 2. The **companion app** uses the command and control managed API to request execution of a remote command.
@@ -102,7 +102,7 @@ This dataflow covers the process to register and provision vehicles and devices
 
 :::image type="content" source="media/mqtt-automotive-connectivity-and-data-solution/provisioning-dataflow.png" alt-text="Diagram of the provisioning dataflow." border="false" lightbox="media/mqtt-automotive-connectivity-and-data-solution/provisioning-dataflow.png":::
 
-1. The **Factory System** commissions the vehicle device to the desired construction state. This may include firmware & software initial installation and configuration. As part of this process, the factory system will obtain and write the device *certificate*, created from the **Public Key Infrastructure** provider.
+1. The **Factory System** commissions the vehicle device to the desired construction state. This can include firmware & software initial installation and configuration. As part of this process, the factory system will obtain and write the device *certificate*, created from the **Public Key Infrastructure** provider.
 1. The **Factory System** registers the vehicle & device using the *Vehicle & Device Provisioning API*.
 1. The factory system triggers the **device provisioning client** to connect to the *device registration*  and provision the device. The device retrieves connection information to the *MQTT broker*.
 1. The *device registration* application creates the device identity with MQTT broker.
@@ -161,7 +161,7 @@ Each *vehicle messaging scale unit* supports a defined vehicle population (for e
 * [Azure Functions](../azure-functions/functions-overview.md) processes the vehicle messages. It can also be used to implement management APIs that require short-lived execution.
 * [Azure Kubernetes Service (AKS)](../aks/intro-kubernetes.md) is an alternative when the functionality behind the Managed APIs consists of complex workloads deployed as containerized applications.
 * [Azure Cosmos DB](../cosmos-db/introduction.md) stores the vehicle, device and user consent settings.
-* [Azure API Management](../azure/api-management/api-management-key-concepts.md) provides a managed API gateway to existing back-end services such as vehicle lifecycle management (including OTA) and user consent management.
+* [Azure API Management](../api-management/api-management-key-concepts.md) provides a managed API gateway to existing back-end services such as vehicle lifecycle management (including OTA) and user consent management.
 * [Azure Batch](../batch/batch-technical-overview.md) runs large compute-intensive tasks efficiently, such as vehicle communication trace ingestion.
 
 #### Data and Analytics
diff --git a/articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md b/articles/service-bus-messaging/service-bus-to-event-grid-integration-example.md
@@ -165,7 +165,7 @@ If you don't see any invocations after waiting and refreshing for sometime, foll
 * Learn more about [Azure Event Grid](../event-grid/index.yml).
 * Learn more about [Azure Functions](../azure-functions/index.yml).
 * Learn more about the [Logic Apps feature of Azure App Service](../logic-apps/index.yml).
-* Learn more about [Azure Service Bus](../service-bus/service-bus-messaging-overview.md).
+* Learn more about [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md).
 
 
 [2]: ./media/service-bus-to-event-grid-integration-example/sbtoeventgrid2.png
diff --git a/articles/service-bus-messaging/service-bus-to-event-grid-integration-function.md b/articles/service-bus-messaging/service-bus-to-event-grid-integration-function.md
@@ -134,7 +134,7 @@ If you don't see any function invocations after waiting and refreshing for somet
 * Learn more about [Azure Event Grid](../event-grid/index.yml).
 * Learn more about [Azure Functions](../azure-functions/index.yml).
 * Learn more about the [Logic Apps feature of Azure App Service](../logic-apps/index.yml).
-* Learn more about [Azure Service Bus](../service-bus/service-bus-messaging-overview.md).
+* Learn more about [Azure Service Bus](../service-bus-messaging/service-bus-messaging-overview.md).
 
 
 [2]: ./media/service-bus-to-event-grid-integration-example/sbtoeventgrid2.png
diff --git a/articles/stream-analytics/includes/resource-logs-schema.md b/articles/stream-analytics/includes/resource-logs-schema.md
@@ -59,5 +59,5 @@ Message| Log message.
 Type | Type of message. Maps to internal categorization of errors. For example, **JobValidationError** or **BlobOutputAdapterInitializationFailure**.
 Correlation ID | GUID that uniquely identifies the job execution. All execution log entries from the time the job starts until the job stops have the same **Correlation ID** value.
 
-For reference, see a list of [all resource logs category types supported in Azure Monitor](../azure-monitor/platform/resource-logs-schema.md) or [all the resource log category types collected for Azure Stream Analytics](../monitor-azure-stream-analytics-reference.md#resource-logs).
+For reference, see a list of [all resource logs category types supported in Azure Monitor](../../azure-monitor/platform/resource-logs-schema.md) or [all the resource log category types collected for Azure Stream Analytics](../monitor-azure-stream-analytics-reference.md#resource-logs).
 
diff --git a/articles/stream-analytics/monitor-azure-stream-analytics-reference.md b/articles/stream-analytics/monitor-azure-stream-analytics-reference.md
@@ -48,9 +48,9 @@ For the resource logs schema and properties for data errors and events, see [Res
 ### Stream Analytics jobs
 microsoft.streamanalytics/streamingjobs
 
-- [AzureActivity](../azure-monitor/reference/tables/AzureActivity.md)
-- [AzureMetrics](../azure-monitor/reference/tables/AzureMetrics.md)
-- [AzureDiagnostics](../azure-monitor/reference/tables/AzureDiagnostics.md)
+- [AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity)
+- [AzureMetrics](/azure/azure-monitor/reference/tables/AzureMetrics)
+- [AzureDiagnostics](/azure/azure-monitor/reference/tables/AzureDiagnostics)
 
 [!INCLUDE [horz-monitor-ref-activity-log](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-activity-log.md)]
 - [Microsoft.StreamAnalytics resource provider operations](../role-based-access-control/permissions/internet-of-things.md#microsoftstreamanalytics)
diff --git a/articles/stream-analytics/sql-database-output.md b/articles/stream-analytics/sql-database-output.md
@@ -12,7 +12,7 @@ ms.date: 07/21/2022
 
 You can use [Azure SQL Database](https://azure.microsoft.com/services/sql-database/) as an output for data that's relational in nature or for applications that depend on content being hosted in a relational database. Azure Stream Analytics jobs write to an existing table in SQL Database. The table schema must exactly match the fields and their types in your job's output. The Azure portal experience for Stream Analytics allows you to [test your streaming query and also detect if there are any mismatches between the schema](sql-db-table.md) of the results produced by your job and the schema of the target table in your SQL database. To learn about ways to improve write throughput, see the [Stream Analytics with Azure SQL Database as output](stream-analytics-sql-output-perf.md) article. While you can also specify [Azure Synapse Analytics SQL pool](../synapse-analytics/overview-what-is.md) as an output via the SQL Database output option, it is recommended to use the dedicated [Azure Synapse Analytics output connector](azure-synapse-analytics-output.md) for best performance.
 
-You can also use [Azure SQL Managed Instance](../azure-sql/managed-instance/sql-managed-instance-paas-overview.md) as an output. You have to [configure public endpoint in SQL Managed Instance](../azure-sql/managed-instance/public-endpoint-configure.md) and then manually configure the following settings in Azure Stream Analytics. Azure virtual machine running SQL Server with a database attached is also supported by manually configuring the settings below.
+You can also use [Azure SQL Managed Instance](/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview.md) as an output. You have to [configure public endpoint in SQL Managed Instance](/azure/azure-sql/managed-instance/public-endpoint-configure.md) and then manually configure the following settings in Azure Stream Analytics. Azure virtual machine running SQL Server with a database attached is also supported by manually configuring the settings below.
 
 ## Output configuration
 
@@ -41,7 +41,7 @@ Partitioning needs to enabled and is based on the PARTITION BY clause in the que
 
 ## Output batch size
 
-You can configure the max message size by using **Max batch count**. The default maximum is 10,000 and the default minimum is 100 rows per single bulk insert. For more information, see [Azure SQL limits](../azure-sql/database/resource-limits-logical-server.md). Every batch is initially bulk inserted with maximum batch count. Batch is split in half (until minimum batch count) based on retryable errors from SQL.
+You can configure the max message size by using **Max batch count**. The default maximum is 10,000 and the default minimum is 100 rows per single bulk insert. For more information, see [Azure SQL limits](/azure/azure-sql/database/resource-limits-logical-server.md). Every batch is initially bulk inserted with maximum batch count. Batch is split in half (until minimum batch count) based on retryable errors from SQL.
 
 ## Limitation
 
