updates per nick

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/aks/dapr-overview.md

@@ -44,10 +44,10 @@ Microsoft categorizes issues raised against the Dapr extension into two parts:
 
 The following table breaks down support priority levels for each of these categories.
 
-|   | Description | Functional issues | Security risks/Regressions |
-| - | ----------- | ----------------- | -------------------------- | 
-| **Extension operations** | Issues encountered while attempting to install Dapr into a cluster. | Microsoft investigates and addresses as needed. | Microsoft prioritizes for immediate resolution. | 
-| **Dapr runtime** | Issues encountered when using the Dapr runtime, APIs, and components via the extension. | Microsoft investigates new functional issues. Known open source functional issues won't be investigated by Microsoft at this time. | Microsoft works with the open source community to investigate high priority payload issues. Issues may be resolved in a hotfix or future Dapr open source release, depending on priority, severity, and size of the issue. Once fixes are released in Dapr open source, they are then made available in the Dapr extension. |
+|   | Description | Security risks/Regressions | Functional issues |
+| - | ----------- | -------------------------- | ----------------- |
+| **Extension operations** | Issues encountered during extension operations, such as installing/uninstalling or upgrading the Dapr extension. | Microsoft prioritizes for immediate resolution. | Microsoft investigates and addresses as needed. | 
+| **Dapr runtime** | Issues encountered when using the Dapr runtime, APIs, and components via the extension. | Microsoft works with the open source community to investigate high priority payload issues. Issues may be resolved in a hotfix or future Dapr open source release, depending on priority, severity, and size of the issue. Once fixes are released in Dapr open source, they are then made available in the Dapr extension. | Microsoft investigates new functional issues. Known open source functional issues won't be investigated by Microsoft at this time. |
 
 ### Dapr versions
 

includes/dapr-in-azure/dapr-support-policy.md

@@ -5,12 +5,12 @@ ms.date: 04/22/2024
 ms.author: hannahhunter
 ---
 
-#### Tier 1 versus tier 2 components
+#### Tier 1 versus Tier 2 components
 
-A subset of Dapr components is supported for the Dapr extension for AKS and Arc-enabled Kubernetes. Within that subset, Dapr components are broken into two support categories: tier 1 or tier 2.  
+A subset of Dapr components is supported for the Dapr extension for AKS and Arc-enabled Kubernetes. Within that subset, Dapr components are broken into two support categories: Tier 1 or Tier 2.  
 
-- [Tier 1 components:](#tier-1-components) Fully managed, stable components that receive immediate investigation in critical (security or serious regression) scenarios. Otherwise, collaborate with open source to address in a hotfix or the next regular release.
-- [Tier 2 components:](#tier-2-components) Built-in components that receive immediate investigation and are supported with best effort attempt to address with third party provider.
+- [Tier 1 components:](../../articles/aks/dapr-overview.md#tier-1-components) Stable components that receive immediate investigation in critical (security or serious regression) scenarios. Otherwise, collaborate with open source to address in a hotfix or the next regular release.
+- [Tier 2 components:](../../articles/aks/dapr-overview.md#tier-2-components) Components that receive immediate investigation and are supported with best effort attempt to address with third party provider.
 
 ##### Tier 1 components