Fill specifics around DNS record fields and adjust heading

Author: RebeccaTamachiro

src/content/docs/dns/reference/domain-connect.mdx

@@ -32,7 +32,7 @@ Domain Connect templates are published and maintained on a GitHub repository.
 2. Add your template. You can create a copy of one of the existing templates and edit it according to your needs.
    * Refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) for details on the different available fields.
 	 :::note
-	 Not all properties and fields are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [supported properties](#supported-properties) section below for details.
+	 Not all fields (properties) are supported by Cloudflare, and some will be mandatory for onboarding your template. Refer to the [properties support](#properties-support) section below for details.
 	 :::
    * If present, you must set the `syncBlock` field on your template to `false`. This means the template flow will be synchronous, which is the only option supported by Cloudflare.
    * You must also provide a synchronous public key domain (`syncPubKeyDomain` [^1]). When your template is in use, synchronous calls will be digitally signed.
@@ -65,7 +65,7 @@ Send an email to `[email protected]`, including the following inform
 
    If you have a [DNS provider discovery](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc#dns-provider-discovery) automation in place and will not list new DNS providers manually, Cloudflare can initially restrict your template to be exposed to the specified account only. Once you confirm everything is working as expected, Cloudflare will publish your template on the discovery endpoint, to be picked up by your automation.
 
-## Supported properties
+## Properties support
 
 In the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc) you will find the following properties:
 
@@ -100,7 +100,7 @@ For the full list, refer to the [Domain Connect Specification](https://github.co
 - **Shared**: Is not supported and will be ignored.
 - **Shared Service Name**: Is not supported and will be ignored.
 - **Synchronous Public Key Domain**: Required. Cloudflare only supports the synchronous flow and always checks for signature.
-- **Synchronous Redirect Domains**: Is not supported and will be ignored. Cloudflare looks at the `redirect_uri` provided in the signed apply template url.
+- **Synchronous Redirect Domains**: Is not supported and will be ignored. Cloudflare looks at the `redirect_uri` provided in the signed apply template URL.
 - **Multiple Instance**: Is not supported and will be ignored.
 - **Warn Phishing**: Is not supported and will be ignored.
 - **Host Required**: Is not supported and will be ignored.
@@ -109,7 +109,9 @@ For the full list, refer to the [Domain Connect Specification](https://github.co
 
 For the full list, refer to the [Domain Connect Specification](https://github.com/Domain-Connect/spec/blob/master/Domain%20Connect%20Spec%20Draft.adoc). Below are the details specific to Cloudflare.
 
-
+- **Essential**: Is not supported and will be ignored.
+- **TXT Conflict Matching Mode**: Is not supported and will be ignored.
+- **TXT Conflict Matching Prefix**: Is not supported and will be ignored.
 
 ## Template updates