Update enforce-dns-only.mdx

[smittal123]

Updating enforce dns only devdocs for different zone types.

Summary

Screenshots (optional)

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[hannes-cf]

Suggested change

	For secondary zones with overrides enabled, the enforce DNS-only setting will grey-cloud any record you have manually proxied. The proxy status override persists until the record is deleted on the primary and transferred again — changes to content or TTL on the primary do not reset the override.
	For secondary zones with overrides enabled, the enforce DNS-only setting will disable the proxy status on any record you have manually proxied. The proxy status override persists until the record is deleted on the primary even if it gets transferred again — changes to content or TTL on the primary do not affect the proxy status.

[RebeccaTamachiro]

I'm not sure I understand what we want to call out with this note, maybe it's the the proxy status override persists in the second sentence that is tripping me up - By this we mean:

a- the effects of the enforce_dns_only setting will persist, meaning that what we describe here in "Disable enforce DNS-only" does not apply in this case.
b- we're just reminding users of how Secondary DNS overrides work, with no particular implication for the behaviors of Enforce DNS-only
c- we just want to reassure them that, even if new transfers occur while enforce_dns_only is active, the proxy status won't be affected (sticking to DNS-only while the setting is active and returning to proxied once it's turned off)

[smittal123]

Yes, the intent is (c) - we want to reassure users that while enforce_dns_only is active, zone transfers won't unexpectedly change their proxy status. The DNS-only setting persists through content/TTL changes on the primary.