Fix broken links.

Author: v-jaswel

articles/container-apps/dns.md

@@ -39,11 +39,11 @@ This feature is supported for both Consumption and Dedicated plans in workload p
 
 ### Tutorials
 - To learn more about how to configure private endpoints in Azure Container Apps, see the [Use a private endpoint with an Azure Container Apps environment](how-to-use-private-endpoint.md) tutorial.
-- Private link connectivity with Azure Front Door is supported for Azure Container Apps. Refer to [create a private link with Azure Front Door](how-to-integrate-with-azure-front-door.md) for more information.
+- Private link connectivity with Azure Front Door is supported for Azure Container Apps. Refer to [create a private link with Azure Front Door](./how-to-integrate-with-azure-front-door.md) for more information.
 
 ### Considerations
 
-- To use a private endpoint, you must disable [public network access](#public-network-access). By default, public network access is enabled, which means private endpoints are disabled.
+- To use a private endpoint, you must disable [public network access](networking.md#public-network-access). By default, public network access is enabled, which means private endpoints are disabled.
 - To use a private endpoint with a custom domain and an *Apex domain* as the *Hostname record type*, you must configure a private DNS zone with the same name as your public DNS. In the record set, configure your private endpoint's private IP address instead of the container app environment's IP address. When you configure your custom domain with CNAME, the setup is unchanged. For more information, see [Set up custom domain with existing certificate](custom-domains-certificates.md).
 - Your private endpoint's VNet can be separate from the VNet integrated with your container app.
 - You can add a private endpoint to both new and existing workload profile environments.

articles/container-apps/ingress-overview.md

@@ -128,7 +128,7 @@ Azure Container Apps provides built-in authentication and authorization features
 
 You can configure your app to support client certificates (mTLS) for authentication and traffic encryption. For more information, see [Configure client certificates](client-certificate-authorization.md).
 
-For details on how to use peer-to-peer environment level network encryption, see [networking configuration](./environment-level-networking.md#peer-to-peer-encryption).
+For details on how to use peer-to-peer environment level network encryption, see [networking configuration](./ingress-environment-configuration.md#peer-to-peer-encryption).
 
 ## Traffic splitting
 

articles/container-apps/networking.md

@@ -163,4 +163,4 @@ IP addresses are broken down into the following types:
 
 ## Next steps
 
-- [Networking configuration in Azure Container Apps environment](environment-level-networking.md)
+- [Ingress in Azure Container Apps](ingress-overview.md)

articles/container-apps/whats-new.md

@@ -84,7 +84,7 @@ You can now find updates and release announcements for [Azure Container Apps](ht
 | [Generally Available: Session affinity](./sticky-sessions.md) | Session affinity enables you to route all requests from a single client to the same Container Apps replica. This is useful for stateful workloads that require session affinity. |
 | [Generally Available: Azure Key Vault references for secrets](https://azure.microsoft.com/updates/generally-available-azure-key-vault-references-for-secrets-in-azure-container-apps/) | Azure Key Vault references enable you to source a container app’s secrets from secrets stored in Azure Key Vault. Using the container app's managed identity, the platform automatically retrieves the secret values from Azure Key Vault and injects it into your application's secrets. |
 | [Public preview: additional TCP ports](./ingress-overview.md#additional-tcp-ports) | Azure Container Apps now support additional TCP ports, enabling applications to accept TCP connections on multiple ports. This feature is in preview. |
-| [Public preview: environment level peer-to-peer encryption](./environment-level-networking.md#peer-to-peer-encryption) | When end-to-end encryption is required, peer-to-peer encryption will encrypt data transmitted between applications within an environment. |
+| [Public preview: environment level peer-to-peer encryption](./ingress-environment-configuration.md#peer-to-peer-encryption) | When end-to-end encryption is required, peer-to-peer encryption will encrypt data transmitted between applications within an environment. |
 | [Retirement: ACA preview API versions 2022-06-01-preview and 2022-11-01-preview](https://azure.microsoft.com/updates/retirement-azure-container-apps-preview-api-versions-20220601preview-and-20221101preview/) | Starting on November 16, 2023, Azure Container Apps control plane API versions 2022-06-01-preview and 2022-11-01-preview will be retired. Before that date, migrate to the latest stable API version (2023-05-01) or latest preview API version (2023-04-01-preview). |
 | [Dapr: Stable Configuration API](https://docs.dapr.io/developing-applications/building-blocks/configuration/) | Dapr's Configuration API is now stable and supported in Azure Container Apps. Learn how to do [Dapr integration with Azure Container Apps](./dapr-overview.md)|
 

articles/spring-apps/migration/migrate-to-azure-container-apps-custom-domain.md

@@ -113,7 +113,7 @@ az containerapp env update \
 
 After you enable peer-to-peer-encryption, one container app can access other container apps using HTTPS with mTLS - for example, `https://<app-name>`. The certificate used in mTLS is system-assigned.
 
-For more information, see the [Peer-to-peer encryption](../../container-apps/environment-level-networking.md#peer-to-peer-encryption) section of [Networking configuration in Azure Container Apps environment](../../container-apps/environment-level-networking.md).
+For more information, see the [Peer-to-peer encryption](../../container-apps/ingress-environment-configuration.md#peer-to-peer-encryption) section of [Configure ingress in an Azure Container Apps environment](../../container-apps/ingress-environment-configuration.md).
 
 ## Traffic to external services
 

articles/spring-apps/migration/migrate-to-azure-container-apps-network.md

@@ -134,7 +134,7 @@ Azure Container Apps supports deployment with a private DNS zone. For more infor
 
 ## Access an app in Azure Container Apps within a customer virtual network
 
-Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/networking.md#private-endpoint) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
+Azure Container Apps provides both [Public network access](../../container-apps/networking.md#public-network-access) and [Private endpoint](../../container-apps/dns.md#private-endpoint) features to expose applications to the internet or to secure them within a private network. Similarly, Azure Spring Apps supports these features as described in the following articles:
 
 - [Access an app in Azure Spring Apps in a virtual network](../basic-standard/access-app-virtual-network.md)
 - [Access applications using Azure Spring Apps Standard consumption and dedicated plan in a virtual network](../consumption-dedicated/quickstart-access-standard-consumption-within-virtual-network.md)