Skip to content

Commit 852c2a2

Browse files
committed
Amend text
1 parent df14c00 commit 852c2a2

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ terms which can be found in the core @context served with every request.
7373

7474
### Normalized NGSI-LD
7575

76-
The full "normalized" form is an excellent choice for data exchange, since through the the `@context` and the definition
76+
The full "normalized" form is an excellent choice for data exchange, since through the `@context` and the definition
7777
of JSON-LD keywords, machines are given all the tools to fully comprehend the payload format. Responses return the
7878
complete current state of each entity, with payloads all including sub-attributes such as Properties-of-Properties,
7979
Properties-of-Relationships and other standard metadata terms like `observedAt` and `unitCode`. Furthermore normalized
@@ -140,7 +140,7 @@ shorter and to the point, and not all information is returned by the request - s
140140
Open in [**JSON-LD Playground**](https://tinyurl.com/2p93h8p6)
141141

142142
This key-values payload matches the simple JSON-LD payload which can be seen on the front-page of the official
143-
[JSON-LD website](https://json-ld.org/)
143+
[JSON-LD site](https://json-ld.org/)
144144

145145
Both normalized and key-values NGSI-LD formats are valid JSON-LD, but since the key-values format is lossy, until
146146
recently, all updates to an NGSI-LD context broker must be made using the normalized format.

0 commit comments

Comments
 (0)