validation error fixes

Author: bandersmsft

articles/azure-databricks/index.yml

@@ -85,15 +85,15 @@ landingContent:
       - linkListType: deploy
         links:
           - text: Deploy Azure Databricks in your virtual network
-            url: vnet-injection.md
+            url: https://docs.microsoft.com/azure/databricks/administration-guide/cloud-configurations/azure/vnet-inject
       - linkListType: tutorial
         links:
           - text: Query a SQL Server Linux Docker container in a virtual network from an Azure Databricks notebook
             url: vnet-injection-sql-server.md
   - title: Stream data
     linkLists:
       - linkListType: learn
-        links: 
+        links:
           - text: Work with streaming data in Azure Databricks
             url: https://docs.microsoft.com/learn/modules/streaming-in-azure-databricks/
       - linkListType: tutorial
@@ -115,4 +115,4 @@ landingContent:
           - text: Databricks REST API
             url: /rest/api/databricks
           - text: R developer's guide
-            url: ../machine-learning/r-developers-guide.md
+            url: ../machine-learning/r-developers-guide.md

articles/logic-apps/logic-apps-exception-handling.md

@@ -244,7 +244,7 @@ You can customize an action's "run after" behavior so that the action runs when
 
 ## Evaluate actions with scopes and their results
 
-Similar to running steps after individual actions with the `runAfter` property, you can group actions together inside a [scope](../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md). You can use scopes when you want to logically group actions together, assess the scope's aggregate status, and perform actions based on that status. After all the actions in a scope finish running, the scope itself gets its own status. 
+Similar to running steps after individual actions with the `runAfter` property, you can group actions together inside a [scope](../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md). You can use scopes when you want to logically group actions together, assess the scope's aggregate status, and perform actions based on that status. After all the actions in a scope finish running, the scope itself gets its own status.
 
 To check a scope's status, you can use the same criteria that you use to check a logic app's run status, such as `Succeeded`, `Failed`, and so on.
 
@@ -262,7 +262,7 @@ Although catching failures from a scope is useful, you might also want context t
 
 The [`result()`](../logic-apps/workflow-definition-language-functions-reference.md#result) function provides context about the results from all the actions in a scope. The `result()` function accepts a single parameter, which is the scope's name, and returns an array that contains all the action results from within that scope. These action objects include the same attributes as the `actions()` object, such as the action's start time, end time, status, inputs, correlation IDs, and outputs. To send context for any actions that failed within a scope, you can easily pair a `@result()` expression with the `runAfter` property.
 
-To run an action for each action in a scope that has a `Failed` result, and to filter the array of results down to the failed actions, you can pair a `@result()` expression with a [**Filter Array**](../connectors/connectors-native-query.md) action and a [**For each**](../logic-apps/logic-apps-control-flow-loops.md) loop. You can take the filtered result array and perform an action for each failure using the `For_each` loop.
+To run an action for each action in a scope that has a `Failed` result, and to filter the array of results down to the failed actions, you can pair a `@result()` expression with a [**Filter Array**](logic-apps-perform-data-operations.md#filter-array-action) action and a [**For each**](../logic-apps/logic-apps-control-flow-loops.md) loop. You can take the filtered result array and perform an action for each failure using the `For_each` loop.
 
 Here's an example, followed by a detailed explanation, that sends an HTTP POST request with the response body for any actions that failed within the scope "My_Scope":
 
@@ -364,4 +364,4 @@ To evaluate run statuses, you can monitor the logs and metrics, or publish them
 ## Next steps
 
 * [See how a customer builds error handling with Azure Logic Apps](../logic-apps/logic-apps-scenario-error-and-exception-handling.md)
-* [Find more Logic Apps examples and scenarios](../logic-apps/logic-apps-examples-and-scenarios.md)
+* [Find more Logic Apps examples and scenarios](../logic-apps/logic-apps-examples-and-scenarios.md)