Merge pull request #27 from ReconJSON/codingo-type-references

codingo · web-flow · commit 3e5c7e5676d6 · 2018-12-08T22:06:17.000+10:00
Updating missing 'ReconJSON' type links
diff --git a/DNS.md b/DNS.md
@@ -1,6 +1,6 @@
 ### DNS
 
-The `DNS` object SHALL be used to describe the DNS configuration of a specific `Host`. If attribute values are not known, they MUST NOT be included unless specified otherwise in the description below. See DNS.md file for futher usage for the `Host` object.
+The `DNS` object SHALL be used to describe the DNS configuration of a specific `Host`. If attribute values are not known, they MUST NOT be included unless specified otherwise in the description below. See DNS.md file for futher usage for the [`Host`](Host.md) object(s).
 
 
 The `DNS` object has the following attributes defined:
diff --git a/ServiceDescriptor.md b/ServiceDescriptor.md
@@ -1,6 +1,6 @@
 ### ServiceDescriptor
 
-The `ServiceDescriptor` object SHALL be used to describe a specific attribute or configuration of the `Service` object. There MAY be several `ServiceDescriptor` objects to a single `Service` object. Since the `ServiceDescriptor` object is the object in which the specifics about programs are to be stored, it is impossible for the authors of this standard to construct a `ServiceDescriptor` object for each and every use case. As a result, community sourcing of this attribute is needed. There will be several `ServiceDescriptor` definitions in the `ServiceDescriptors` folder for basic use (HTTP(s) paths, HTTPS certs, and CSP Definitions) but more will be added as needed. If attribute values are not known, they MUST NOT be included unless specified otherwise in the description below or in another ServiceDescriptor spec doc.
+The `ServiceDescriptor` object SHALL be used to describe a specific attribute or configuration of the [`Service`](Service.md) object. There MAY be several `ServiceDescriptor` objects to a single [`Service`](Service.md) object. Since the `ServiceDescriptor` object is the object in which the specifics about programs are to be stored, it is impossible for the authors of this standard to construct a `ServiceDescriptor` object for each and every use case. As a result, community sourcing of this attribute is needed. There will be several `ServiceDescriptor` definitions in the `ServiceDescriptors` folder for basic use (HTTP(s) paths, HTTPS certs, and CSP Definitions) but more will be added as needed. If attribute values are not known, they MUST NOT be included unless specified otherwise in the description below or in another ServiceDescriptor spec doc.
 
 `ServiceDescriptor` objects SHOULD be returned in the context of a `Host > Port > Service`. However they MAY be returned by themselves. As such, `ServiceDescritors` SHOULD contain information to help identifiy which `Host`, `Port`, and `Service` to which they belong.
 
