fix warnings

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

Author: hhunter-ms

articles/container-apps/dapr-component-authentication.md renamed to articles/container-apps/dapr-component-connect-services.md

@@ -1,6 +1,6 @@
 ---
 title: Connecting to services via Dapr components
-description: Learn more about how Dapr components work on your Azure Container App service to develop applications.
+description: Learn more about connecting Dapr components with Azure and external services.
 ms.author: hannahhunter
 author: hhunter-ms
 ms.service: azure-container-apps
@@ -9,7 +9,7 @@ ms.topic: conceptual
 ms.date: 09/23/2024
 ---
 
-## Connecting to services via Dapr components
+# Connecting to services via Dapr components
 
 Securely establish connections to Azure and external services for Dapr components using any of the following approaches.
 
@@ -18,14 +18,14 @@ Securely establish connections to Azure and external services for Dapr component
    - [An Azure Key Vault secret store](#azure-key-vault-secret-stores), which uses managed identity, or
    - [Platform-Managed Kubernetes secrets](#platform-managed-kubernetes-secrets)
 
-### Using managed identity
+## Using managed identity
 
 For Azure-hosted services, Dapr can use [the managed identity of the scoped container apps][aca-managed-id] to authenticate to the backend service provider. When using managed identity, you don't need to include secret information in a component manifest. Using managed identity is preferred as it eliminates storage of sensitive input in components and doesn't require managing a secret store.
 
 > [!NOTE]
 > The `azureClientId` metadata field (the client ID of the managed identity) is **required** for any component authenticating with user-assigned managed identity.
 
-### Using a Dapr secret store component reference
+## Using a Dapr secret store component reference
 
 When you create Dapr components for non-Entra ID enabled services, certain metadata fields require sensitive input values. The recommended approach for retrieving these secrets is to reference an existing Dapr secret store component that securely accesses secret information.
 
@@ -34,14 +34,14 @@ To set up a reference:
 1. [Create a Dapr secret store component using the Azure Container Apps schema.](#creating-a-dapr-secret-store-component) The component type for all supported Dapr secret stores begins with `secretstores.`.
 1. [Create extra components (as needed) which reference the Dapr secret store component](#referencing-dapr-secret-store-components) you created to retrieve the sensitive metadata input.
 
-#### Creating a Dapr secret store component
+### Creating a Dapr secret store component
 
 When creating a secret store component in Azure Container Apps, you can provide sensitive information in the metadata section in either of the following ways:
 
 - [For an **Azure Key Vault secret store**,](#using-managed-identity) use managed identity to establish the connection. 
 - [For **non-Azure secret stores**,](#platform-managed-kubernetes-secrets) use platform-managed Kubernetes secrets that are defined directly as part of the component manifest.
 
-##### Azure Key Vault secret stores
+#### Azure Key Vault secret stores
 
 The following component showcases the simplest possible secret store configuration using an Azure Key Vault secret store. In this example, publisher and subscriber applications are configured to both have a system or user-assigned managed identity with appropriate permissions on the Azure Key Vault instance.
 
@@ -60,7 +60,7 @@ scopes:
   - subscriber-app
 ```
 
-##### Platform-managed Kubernetes secrets
+#### Platform-managed Kubernetes secrets
 
 Kubernetes secrets, Local environment variables, and Local file Dapr secret stores aren't supported in Azure Container Apps. As an alternative for the upstream Dapr default Kubernetes secret store, Azure Container Apps provides a platform-managed approach for creating and leveraging Kubernetes secrets.
 
@@ -88,7 +88,7 @@ scopes:
   - subscriber-app
 ```
 
-#### Referencing Dapr secret store components
+### Referencing Dapr secret store components
 
 Once you [create a Dapr secret store using one of the previous approaches](#creating-a-dapr-secret-store-component), you can reference that secret store from other Dapr components in the same environment. The following example demonstrates using Entra ID authentication.