Fix build errors

Author: v-jaswel

articles/container-apps/ingress-overview.md

@@ -101,7 +101,7 @@ Visit the [how to article on ingress](ingress-how-to.md#use-additional-tcp-ports
 
 You can access your app in the following ways:
 
-- The default fully qualified domain name (FQDN): Each app in a Container Apps environment is automatically assigned an FQDN based on the environment's DNS (Domain Name System) suffix. This suffix is determined by the [`CONTAINER_APP_ENV_DNS_SUFFIX` environment variable](environment-variables#apps). To customize an environment's DNS suffix, see [Custom environment DNS Suffix](environment-custom-dns-suffix.md).
+- The default fully qualified domain name (FQDN): Each app in a Container Apps environment is automatically assigned an FQDN based on the environment's DNS (Domain Name System) suffix. This suffix is determined by the [`CONTAINER_APP_ENV_DNS_SUFFIX` environment variable](environment-variables.md#apps). To customize an environment's DNS suffix, see [Custom environment DNS Suffix](environment-custom-dns-suffix.md).
 
 - A custom domain name: You can configure a custom DNS domain for your Container Apps environment. For more information, see [Custom domain names and certificates](./custom-domains-certificates.md).
 

articles/container-apps/networking-configuration.md

@@ -153,7 +153,7 @@ You can enable peer-to-peer encryption in the ARM template for Container Apps en
 
 ---
 
-# Rule-based routing (preview)
+## Rule-based routing (preview)
 
 With rule-based routing, you create a fully qualified domain name (FQDN) on your container apps environment. You then use rules to route requests to this FQDN to different container apps, depending on the path of each request. This offers the following benefits.