upd readme

Author: Alexey Vekshin

README.md

@@ -35,13 +35,15 @@ resource "godaddy-dns_record" "new-cname" {
 It currently supports `A`, `AAAA`, `CNAME`, `MX`, `NS` and `TXT` records. `SRV` are not supported; if anyone hosting AD on GoDaddy or uses them for VOIP or something like that, please let me know by creating an issue.
 
 GoDaddy API does not have stable identities for DNS records, and in case of external modifications (e.g. via web console) behaviour is slightly different for "single-valued" vs "multi-valued" records
-- for "single-valued" record types (`A` and `CNAME`) there could be only 1 record of this type with a given name, so these are just replaced by update
-- for "multi-valued" record types (`MX`, `NS`, `TXT`) there could be several records with a given name (e.g. multiple MXes with different priorities and targets), so matching is done on value; if record's value is modified outside of Terraform, it is treated as a completely different record and is preserved (and original record is considered gone), so record is re-created on update.
+- for "single-valued" record types (`CNAME`) there could be only 1 record of this type with a given name, so these are just replaced by update
+- for "multi-valued" record types (`A`, `MX`, `NS`, `TXT`) there could be several records
+with a given name (e.g. multiple MXes with different priorities and targets), so matching is done on value
+- if record's value is modified outside of Terraform, it is treated as a completely different record and is preserved, while original record is considered gone and is re-created on `apply` (use `refresh` + `import` to re-link modified record back to original).
 
 ## Differences vs alternative providers
 
 Differences vs n3integration provider and its forks:
-- granularity: top-level configuration object is record, not domain
+- configuration object is record, not (top-level) domain no need to bring it all under terraform management
+- could safely manage a subset of records (e.g. only one TXT or CNAME at domain top), keeping the rest intact
 - updates do not result in scary plans threatening to destroy all the records in the whole domain
-- external modifications are mostly fine: update will not complain if record is already set to the desired state, delete will be NOOP if record is already gone
-- `destroy` is fully supported
+- `destroy` is fully supported and removes only previously created records