Update rfd text to reflect tag change

Author: darakian

rfds/0000-public-forum-link.md

@@ -18,13 +18,10 @@ By the nature of multitude of possible ways an advisory disclosure may conclude,
 ## Proposed Solution
 [proposed-solution]: #proposed-solution
 
-This RFD proposes one new optional CVE property of the form
+This RFD proposes one reference type
 
 ```
-"discussionForum": {
-              "description": "The canonical forum for discussing CVE details.",
-              "$ref": "#/definitions/uriType"
-          },
+"discussion-forum"
 ```
 
 The details are not set in stone, but the idea is to provide a URL which points a consumer of a CVE in the right direction should they have issue with the record. Tooling could even integrate this into how records are presented. Ideally this is public both for the benefit of community knowledge and to reduce duplicate work on the part of the humans tasked to operate the forum.
@@ -46,7 +43,7 @@ Low. This field can be safely ignored.
 ## Compatibility and Migration
 [compatibility-and-migration]: #compatibility-and-migration
 
-It adds one optional property
+It adds one new reference type
 
 ## Success Metrics
 [success-metrics]: #success-metrics
@@ -80,4 +77,4 @@ How to handle the case where an adp and cna both publish unique discussion forum
 ## Future Possibilities
 [future-possibilities]: #future-possibilities
 
-I'd love to see a CNA use this field dynamically such that the record for CVE-808-12345 would point to the individual topic for that CVE record. With this approach user would be welcomed to an ongoing conversation rathar than needing to search.
+I'd love to see a CNA use this dynamically such that the record for CVE-808-12345 would point to the individual topic for that CVE record. With this approach user would be welcomed to an ongoing conversation rathar than needing to search.