Update 3.0.md

I have updated the text to try and address concerns raised in the TDC call.

- Clarified that compatibility with CommonMark is only relevant for tooling that renders rich text.  
- Clarified that tooling is not limited to only supporting CommonMark .27 features. Other newer features can be supported
- Clarified that tooling should only ignore and not fail when features with security concerns are used.

Author: darrelmiller

versions/3.0.md

@@ -168,7 +168,7 @@ password | `string` | `password` | Used to hint UIs the input needs to be obscur
 
 ### <a name="richText"></a>Rich Text Formatting
 Throughout the specification `description` fields are noted as supporting CommonMark markdown formatting.
-OpenAPI compliant tooling MUST support markdown that is compliant with [CommonMark 0.27](http://spec.commonmark.org/0.27/). Tooling MAY limit some CommonMark features to address security concerns. 
+Where OpenAPI tooling renders rich text it MUST support, at a minimum, markdown syntax as described by [CommonMark 0.27](http://spec.commonmark.org/0.27/). Tooling MAY choose to ignore some CommonMark features to address security concerns. 
 
 ### <a name="relativeReferences"></a>Relative References in URLs