Merge pull request #4946 from ralfhandl/3.2-json-pointer

3.2 Consistent use of "JSON Pointer"

Author: lornajane

src/oas.md

@@ -160,7 +160,7 @@ Therefore, all implementations SHOULD allow users to provide documents with thei
 
 ###### Resolving URI fragments
 
-If a URI contains a fragment identifier, then the fragment should be resolved per the fragment resolution mechanism of the referenced document. If the representation of the referenced document is JSON or YAML, then the fragment identifier SHOULD be interpreted as a JSON-Pointer as per [RFC6901](https://tools.ietf.org/html/rfc6901).
+If a URI contains a fragment identifier, then the fragment should be resolved per the fragment resolution mechanism of the referenced document. If the representation of the referenced document is JSON or YAML, then the fragment identifier SHOULD be interpreted as a JSON Pointer as per [RFC6901](https://tools.ietf.org/html/rfc6901).
 
 ###### Relative URI References in CommonMark Fields