Skip to content

Commit 31eef03

Browse files
committed
Consistent use of "JSON Pointer"
1 parent 1e94ea4 commit 31eef03

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/oas.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ Therefore, all implementations SHOULD allow users to provide documents with thei
160160

161161
###### Resolving URI fragments
162162

163-
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).
163+
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).
164164

165165
###### Relative URI References in CommonMark Fields
166166

0 commit comments

Comments
 (0)