Update docs/README.md

Co-authored-by: Marcin Rataj <[email protected]>

docs/README.md

@@ -78,9 +78,7 @@ Looking up `fictive.domain` will return the entry of `_dnslink.fictive.domain`!
 
 Using a `_dnslink` subdomain prevents conflicts with `CNAME` and `ALIAS` records. It also allows you to delegate control over your DNSLink records to a third party without giving away full control over the original DNS zone, and decreases the size of DNS response packets on domains which have other types of `TXT` records.
 
-`TXT` records on the `domain` without the `_dnslink` subdomain are discouraged and exist for legacy reasons. We historically started with supporting records on the normal domain, and only found the issue with `CNAME` and `ALIAS` records later on.
-
-It is _not required_ but strongly recommended to **set the dnslink entry on the `_dnslink` subdomain!**
+`TXT` records on a domain without the `_dnslink` subdomain might be supported by some systems for legacy reasons, but are highly discouraged for any new deployments.
 
 ### Multiple entries