Avoid bold for non-UI and consolidate specific records explanation

Author: RebeccaTamachiro

src/content/docs/dns/manage-dns-records/reference/wildcard-dns-records.mdx

@@ -8,9 +8,7 @@ sidebar:
 
 import { Details, Example, Render } from "~/components"
 
-Normal DNS records map a domain name to one or multiple IP addresses or other associated resources to a specific domain name (a one-to-many mapping).
-
-Wildcard DNS records allow you to have a many-to-many mapping, for example if you had hundreds or thousands of subdomains you wanted to point to the same resources. Wildcard records are used as the response for all subdomains that are not specifically covered by another DNS record.
+Normal DNS records map a domain name to one or multiple IP addresses or other associated resources to a specific domain name (a one-to-many mapping). Wildcard DNS records allow you to have a many-to-many mapping, for example if you had hundreds or thousands of subdomains you wanted to point to the same resources.
 
 Within Cloudflare, wildcard DNS records can be either [proxied or DNS-only](/dns/proxy-status/).
 
@@ -46,12 +44,19 @@ You can also create a wildcard DNS record specifically for a deeper subdomain. F
 
 ### Aspects to consider
 
-* **Wildcards are only supported on the first label**: This means that a hostname such as `subdomain.*.example.com` is not a wildcard on the level of the asterisk character. If you create a DNS record with that name, the asterisk is interpreted as the literal character `*` and not as the wildcard operator.
+#### Wildcards are only supported on the first label
+
+This means that a hostname such as `subdomain.*.example.com` is not a wildcard on the level of the asterisk character. If you create a DNS record with that name, the asterisk is interpreted as the literal character `*` and not as the wildcard operator.
+
+#### Wildcards are multi-level by default
+
+If you create a DNS record on `*.*.example.com`, only the first asterisk is interpreted as a wildcard while the second one is interpreted as the literal `*` character. A record `*.example.com` is already multi-level by default, meaning it would cover `abc.example.com` as well as `123.abc.example.com`, as long as there are no [specific DNS records](#specific-dns-records-take-precedence-over-wildcard-records) that would take precedence.
 
-* **You cannot create wildcards on multiple levels**: If you create a DNS record on `*.*.example.com`, only the first asterisk is interpreted as a wildcard while the second one is interpreted as the literal `*` character.
+#### Specific DNS records take precedence over wildcard records
 
-* **Specific DNS records take precedence over wildcard records**: Wildcards will be applied for multiple levels, but a specific record on any equal or lower level will terminate anything on or below this specific record.
+A wildcard record applies only when no exact record exists at the queried name. If a record or delegation exists, the wildcard does not apply.
 
+Wildcards will be applied for multiple levels, but a specific record on any equal or lower level will terminate anything on or below this specific record.
 
   <Details header="Example">