142
142
< p >
143
143
Comments regarding this document by the W3C Advisory Committee are welcome
144
144
before January 14th 2021, but readers should be aware that the comment period
145
- regarding the rest of this document has ended and the Working Group is unlikley
145
+ regarding the rest of this document has ended and the Working Group is unlikely
146
146
to make substantive modifications to the specification at this stage.
147
147
Please file issues directly on
148
148
< a href ="https://github.com/w3c/vc-data-model/issues/ "> GitHub</ a > ,
@@ -1819,7 +1819,7 @@ <h3>Expiration</h3>
1819
1819
< p class ="note ">
1820
1820
It is expected that the next version of this specification will add the
1821
1821
< code > validUntil</ code > < a > property</ a > in a way that deprecates, but
1822
- preserves backwards compatability with the < code > expirationDate</ code >
1822
+ preserves backwards compatibility with the < code > expirationDate</ code >
1823
1823
< a > property</ a > . Implementers are advised that the < code > validUntil</ code >
1824
1824
< a > property</ a > is reserved and its use for any other purpose is discouraged.
1825
1825
</ p >
@@ -2100,7 +2100,7 @@ <h3>Lifecycle Details</h3>
2100
2100
</ p >
2101
2101
2102
2102
< p >
2103
- The most comon sequence of actions is envisioned to be:
2103
+ The most common sequence of actions is envisioned to be:
2104
2104
</ p >
2105
2105
2106
2106
< ol >
@@ -2116,7 +2116,7 @@ <h3>Lifecycle Details</h3>
2116
2116
</ ol >
2117
2117
2118
2118
< p >
2119
- This specification does not define any protocol for transfering
2119
+ This specification does not define any protocol for transferring
2120
2120
< a > verifiable credentials</ a > or < a > verifiable presentations</ a > , but assuming
2121
2121
other specifications do specify how they are transferred between entities, then
2122
2122
this Verifiable Credential Data Model is directly applicable.
@@ -3325,7 +3325,7 @@ <h3>JSON</h3>
3325
3325
3326
3326
< p >
3327
3327
The data model, as described in Section < a href ="#core-data-model "> </ a > , can be
3328
- encoded in Javascript Object Notation (JSON) [[!RFC8259]] by mapping property
3328
+ encoded in JavaScript Object Notation (JSON) [[!RFC8259]] by mapping property
3329
3329
values to JSON types as follows:
3330
3330
</ p >
3331
3331
@@ -5018,7 +5018,7 @@ <h3>Language and Base Direction</h3>
5018
5018
</ pre >
5019
5019
5020
5020
< p class ="note ">
5021
- The text above would most likley be rendered incorrectly as left-to-right
5021
+ The text above would most likely be rendered incorrectly as left-to-right
5022
5022
without the explicit expression of language and direction because many systems
5023
5023
use the first character of a text string to determine text direction.
5024
5024
</ p >
0 commit comments