--- a/spec/latest/json-ld-syntax/index.html Fri Jun 22 22:38:00 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html Fri Jun 22 22:41:19 2012 -0400
@@ -532,7 +532,7 @@
<p>Note that the definition for <tref>Linked Data</tref> above is silent on the
topic of unlabeled nodes. Nevertheless, this specification allows for the expression
-of unlabled nodes, as most graph-based data sets on the Web contain a number
+of unlabeled nodes, as most graph-based data sets on the Web contain a number
of associated nodes that are not named and thus are not directly
de-referenceable.
</p>
@@ -626,7 +626,7 @@
give them an unambiguous identifier. That is, it is useful for <tref>term</tref>s to expand to IRIs so that
developers don't accidentally step on each other's <tdef>vocabulary</tdef> terms. Furthermore, developers, and
machines, are able to use this <tref>IRI</tref> (by plugging it directly into a web browser, for instance) to go to
- the term and get a definition of what the term means. This mechanism is analogousto the way we can use
+ the term and get a definition of what the term means. This mechanism is analogous to the way we can use
<a href="http://wordnet.princeton.edu/">WordNet</a> today to see the definition of words in the English language.
Developers and machines need the same sort of definition of terms. <tref title="IRI">IRIs</tref> provide a way to
ensure that these terms are unambiguous. For example, the term <code>name</code> may
@@ -684,7 +684,7 @@
terms map to <tref title="IRI">IRIs</tref>.
Mapping those keys to IRIs gives the data global context. If two
developers use the same IRI to describe a property, they are more than likely
-expressing the same concept. This allows both developers to re-use each others
+expressing the same concept. This allows both developers to re-use each others'
data without having to agree to how their data will interoperate on a
site-by-site basis. Contexts may also contain type information
for certain <tref>term</tref>s as well as other processing instructions for