Replace 'label' terminology with 'name' per PM feedback

The term 'label' has a specific DNS meaning (string between dots).
Using 'name' is clearer and avoids confusion.

Author: ngayerie

src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx

@@ -340,15 +340,15 @@ For [proxied (orange cloud)](/dns/proxy-status/) names, Cloudflare synthesizes H
 
 If you have disabled Universal SSL (for example, because you use [Advanced Certificates](/ssl/edge-certificates/advanced-certificate-manager/) exclusively), Cloudflare will not generate HTTPS records for proxied names.
 
-For [DNS-only (grey cloud)](/dns/proxy-status/) names, you can manually add HTTPS records and Cloudflare will serve them. However, **all records on the same label must be DNS-only** for the manual HTTPS record to be served.
+For [DNS-only (grey cloud)](/dns/proxy-status/) names, you can manually add HTTPS records and Cloudflare will serve them. However, **all records with the same name must be DNS-only** for the manual HTTPS record to be served.
 
 <Details header="Example: Manual HTTPS records and proxy status">
 
-A label refers to all DNS records in a zone that share the same name. For Cloudflare to serve a manually-added HTTPS record, every record on that label must be DNS-only (grey cloud).
+For Cloudflare to serve a manually-added HTTPS record, every record with the same name must be DNS-only (grey cloud).
 
 <Example>
 
-**Will work** — All records on the label are DNS-only:
+**Will work** — All records with the same name are DNS-only:
 
 | Type  | Name        | Content         | Proxy status |
 | ----- | ----------- | --------------- | ------------ |
@@ -361,14 +361,14 @@ The HTTPS record will be served because the A record is DNS-only.
 
 <Example>
 
-**Will not work** — Mixed proxy status on the same label:
+**Will not work** — Mixed proxy status for the same name:
 
 | Type  | Name        | Content         | Proxy status |
 | ----- | ----------- | --------------- | ------------ |
 | AAAA  | example.com | `2001:db8::1`   | Proxied      |
 | HTTPS | example.com | `1 . alpn="h3"` | -            |
 
-The HTTPS record will **not** be served because the AAAA record on the same label is proxied.
+The HTTPS record will **not** be served because the AAAA record with the same name is proxied.
 
 </Example>
 

src/content/docs/ssl/reference/browser-compatibility.mdx

@@ -48,7 +48,7 @@ If your domain has [HTTP/2 or HTTP/3 enabled](/speed/optimization/protocol/), [p
 :::caution[Universal SSL required for automatic HTTPS records]
 Disabling Universal SSL will prevent automatic HTTPS record generation for proxied hostnames, even if you have [Advanced Certificates](/ssl/edge-certificates/advanced-certificate-manager/) or [custom certificates](/ssl/edge-certificates/custom-certificates/) configured. This is because automatic HTTPS record generation is tied specifically to the Universal SSL feature.
 
-If you need HTTPS records without Universal SSL, you can manually add them, but only if **all records on the same label are DNS-only (grey cloud)**. Refer to [SVCB and HTTPS records](/dns/manage-dns-records/reference/dns-record-types/#svcb-and-https) for details and examples.
+If you need HTTPS records without Universal SSL, you can manually add them, but only if **all records with the same name are DNS-only (grey cloud)**. Refer to [SVCB and HTTPS records](/dns/manage-dns-records/reference/dns-record-types/#svcb-and-https) for details and examples.
 :::
 
 ## OCSP and HTTP versions