Skip to content

Commit 58e9315

Browse files
GiaoGiaoCatethanresnick
authored andcommitted
Fix miss link (json-api#1034)
1 parent c422b79 commit 58e9315

File tree

2 files changed

+15
-15
lines changed

2 files changed

+15
-15
lines changed

_format/1.0/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ A relationship object that represents a to-many relationship **MAY** also contai
268268
269269
#### <a href="#document-resource-object-related-resource-links" id="document-resource-object-related-resource-links" class="headerlink"></a> Related Resource Links
270270

271-
A "related resource link" provides access to [resource objects] [linked][links]
271+
A "related resource link" provides access to [resource objects][resource objects] [linked][links]
272272
in a [relationship][relationships]. When fetched, the related resource object(s)
273273
are returned as the response's primary data.
274274

_format/1.1/index.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ A relationship object that represents a to-many relationship **MAY** also contai
268268
269269
#### <a href="#document-resource-object-related-resource-links" id="document-resource-object-related-resource-links" class="headerlink"></a> Related Resource Links
270270

271-
A "related resource link" provides access to [resource objects] [linked][links]
271+
A "related resource link" provides access to [resource objects][resource objects] [linked][links]
272272
in a [relationship][relationships]. When fetched, the related resource object(s)
273273
are returned as the response's primary data.
274274

@@ -633,22 +633,22 @@ The following characters **MUST NOT** be used in member names:
633633

634634
#### <a href="#document-member-names-at-members" id="document-member-names-at-members" class="headerlink"></a> @-Members
635635

636-
Member names **MAY** also begin with an at sign (U+0040 COMMERCIAL AT, "@").
637-
Members named this way are called "@-Members". @-Members **MAY** appear
638-
anywhere in a JSON API document.
636+
Member names **MAY** also begin with an at sign (U+0040 COMMERCIAL AT, "@").
637+
Members named this way are called "@-Members". @-Members **MAY** appear
638+
anywhere in a JSON API document.
639639

640-
However, JSON API processors **MUST** completely ignore @-Members (i.e. not
641-
treat them as JSON API data).
640+
However, JSON API processors **MUST** completely ignore @-Members (i.e. not
641+
treat them as JSON API data).
642642

643-
Moreover, the existence of @-Members **MUST** be ignored when interpreting all
644-
JSON API definitions and processing instructions given outside of this
645-
subsection. For example, an [attribute][attributes] is defined above as any
646-
member of the attributes object. However, because @-Members must be ignored
647-
when interpreting that definition, an @-Member that occurs in an attributes
648-
object is not an attribute.
643+
Moreover, the existence of @-Members **MUST** be ignored when interpreting all
644+
JSON API definitions and processing instructions given outside of this
645+
subsection. For example, an [attribute][attributes] is defined above as any
646+
member of the attributes object. However, because @-Members must be ignored
647+
when interpreting that definition, an @-Member that occurs in an attributes
648+
object is not an attribute.
649649

650-
> Note: Among other things, "@" members can be used to add JSON-LD data to a
651-
JSON API document. Such documents should be served with [an extra header](http://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld)
650+
> Note: Among other things, "@" members can be used to add JSON-LD data to a
651+
JSON API document. Such documents should be served with [an extra header](http://www.w3.org/TR/json-ld/#interpreting-json-as-json-ld)
652652
to convey to JSON-LD clients that they contain JSON-LD data.
653653

654654
## <a href="#fetching" id="fetching" class="headerlink"></a> Fetching Data

0 commit comments

Comments
 (0)