fix link and text

spec/registry/spec.md

@@ -35,7 +35,7 @@ Corresponds to the mapping, for a DID Document's DNS packet representation, of a
 | 2     | [secp256r1](https://neuromancer.sk/std/secg/secp256r1) |
 
 
-An example [Verification Method]((https://www.w3.org/TR/did-core/#verification-methods)) record represented as a DNS TXT
+An example [Verification Method](https://www.w3.org/TR/did-core/#verification-methods) record represented as a DNS TXT
 record is as follows:
 
 | Name      | Type | TTL  | Rdata                                                     |

spec/spec.md

@@ -175,9 +175,12 @@ The following section describes mapping a [[ref:DID Document]] to a DNS packet.
 long identifiers in resource name fields, resource names are aliased with zero-indexed values (e.g. `k0`, `k1`, `s0`, `s1`).
 The complete identifier is stored in the resource data field (e.g. `id=abcd,t=0,k=...`).
 
-* The _root record_, `_did.` or `_did.TLD.` if a [TLD](https://en.wikipedia.org/wiki/Top-level_domain) is being utilized
+* The _root record_, `_did.` or `_did.TLD.` if a [TLD](https://en.wikipedia.org/wiki/Top-level_domain) is used,
 contains a list of IDs of the keys and service endpoints used in different sections of the [[ref:DID Document]].
 
+* Verification Methods, Verification Relationships, and Services are separated by a `;`, while 
+values within each property are separatred by a `,`.
+
 An example is as follows:
 
 | Name       | Type | TTL  | Rdata                                                 |