Skip to content

Commit d9b7e0d

Browse files
Correct wrong usages of Object Representation
1 parent 1044c08 commit d9b7e0d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

index.html

+2-2
Original file line numberDiff line numberDiff line change
@@ -433,7 +433,7 @@ <h3>Example Conventions</h3>
433433
<p>Note that in the examples used in this document, output
434434
is of necessity shown in serialized form as JSON. While the algorithms
435435
describe operations on the <a>JSON-LD internal representation</a>, when
436-
they as displayed as examples, the Object Representation is used. In particular,
436+
they as displayed as examples, the JSON serialization is used. In particular,
437437
the internal representation use of <a>maps</a> are represented using
438438
<a>JSON objects</a>.</p>
439439

@@ -458,7 +458,7 @@ <h3>Example Conventions</h3>
458458
<p>In the <a>internal representation</a>, the example above would be of a
459459
<a>map</a> containing <code>@context</code>, <code>@id</code>, <code>name</code>, and <code>knows</code> <a>entries</a>,
460460
with either <a>maps</a>, <a>strings</a>, or <a>arrays</a> of
461-
maps or strings values. In the Object Representation, <a>JSON objects</a> are used
461+
maps or strings values. In the JSON serialization, <a>JSON objects</a> are used
462462
for maps, while arrays and strings are serialized using a
463463
convention common to many programming languages.</p>
464464
</section>

0 commit comments

Comments
 (0)