--- a/spec/latest/json-ld-api/index.html Mon Jun 25 11:25:06 2012 -0700
+++ b/spec/latest/json-ld-api/index.html Mon Jun 25 12:54:20 2012 -0700
@@ -661,7 +661,7 @@
</dd>
<dt><tdef>number</tdef></dt>
<dd>
- A number is is similar to that used in most programming languages, except
+ A number is similar to that used in most programming languages, except
that the octal and hexadecimal formats are not used and that leading
zeros are not allowed.</dd>
<dt><tdef>true</tdef> and <tdef>false</tdef></dt><dd>
@@ -788,7 +788,7 @@
<code>context</code> according to the steps in the
<a href="#compaction-algorithm">Compaction Algorithm</a>. The
<code>input</code> MUST be copied, compacted and returned if there are
- no errors. If the compaction fails, an appropirate exception MUST be
+ no errors. If the compaction fails, an appropriate exception MUST be
thrown.
<dl class="parameters">
@@ -938,7 +938,7 @@
<section>
<h3>JsonLdOptions</h3>
- <p>The <a>JsonLdOptions</a> type is used to convery a set of options to an interface method.</p>
+ <p>The <a>JsonLdOptions</a> type is used to convert a set of options to an interface method.</p>
<dl title="typedef object JsonLdOptions" class="idl">
<dt><a>URL</a> base</dt>
<dd>The Base IRI to use when expanding the document. This overrides the value of
@@ -1756,7 +1756,7 @@
</li>
<li>Otherwise, return <em>element</em> as the compacted <em>element</em>.
<div class="issue">Perhaps this should also call <a href="#value-compaction">Value Compaction</a> on
- native types and strings, which could consolodate potential transformation in one place.</div>
+ native types and strings, which could consolidate potential transformation in one place.</div>
</li>
</ol>
--- a/spec/latest/json-ld-framing/index.html Mon Jun 25 11:25:06 2012 -0700
+++ b/spec/latest/json-ld-framing/index.html Mon Jun 25 12:54:20 2012 -0700
@@ -335,7 +335,7 @@
</dd>
<dt><tdef>number</tdef></dt>
<dd>
- A number is is similar to that used in most programming languages, except that the octal and hexadecimal formats are not used and that leading zeros are not allowed.</dd>
+ A number is similar to that used in most programming languages, except that the octal and hexadecimal formats are not used and that leading zeros are not allowed.</dd>
<dt><tdef>true</tdef> and <tdef>false</tdef></dt><dd>
Boolean values.
</dd>
@@ -384,7 +384,7 @@
<li>A <tref>property</tref> SHOULD be an <tref>IRI</tref>. To be converted
to or from RDF, a <tref>property</tref> MUST be an <tref>IRI</tref></li>
<li>A <tdef>blank node</tdef> is a <tref>node</tref> which is neither an <tref>IRI</tref> nor a <tref>literal</tref>
- but representes an unknown <tref>node</tref>, which may be either an <tref>IRI</tref> or a <tref>literal</tref>.
+ but represents an unknown <tref>node</tref>, which may be either an <tref>IRI</tref> or a <tref>literal</tref>.
Within a document, a <tref>blank node</tref> may have an identifier used for intra-document reference
purposes only. See [[!RDF-CONCEPTS]] for a further description of
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#dfn-blank-node">blank nodes</a></cite>.</li>
@@ -529,7 +529,7 @@
<section>
<h3>JsonLdOptions</h3>
- <p>The <a>JsonLdOptions</a> type is used to convery a set of options to an interface method.</p>
+ <p>The <a>JsonLdOptions</a> type is used to convert a set of options to an interface method.</p>
<p>See <dtref>JsonLdOptions</dtref> definition in [[!JSON-LD-API]].</p>
<dl title="typedef object JsonLdOptions" class="idl">
<dt><a>URL</a> base</dt>
@@ -673,7 +673,7 @@
<section>
<h3>Generate Blank Node Identifier</h3>
-<p>This algorithm is used by the <a href="#framing-algorithm">Framing Algorithm</a> to deterministicly name
+<p>This algorithm is used by the <a href="#framing-algorithm">Framing Algorithm</a> to deterministically name
<tref>blank node</tref> identifiers. It uses a <em>identifier map</em> and <em>prefix</em>
and takes a possibly <tref>null</tref> identifier and returns a new identifier based on <em>prefix</em>.</p>
<p>The variable <em>next identifier</em> is initialized to <em>prefix</em> appended with <code>0</code>.</p>
@@ -914,7 +914,7 @@
<li>If <em>element</em> is not a <tref>JSON object</tref> or if it has a <code>@value</code> property,
then if <em>list</em> is not <tref>null</tref>, append <em>element</em> to <em>list</em> and return.</li>
<li>If the <code>@id</code> property exists and is an <tref>IRI</tref>, set <em>id</em> to its value, otherwise
- set it to a <tref>blank node</tref> identifer created by the
+ set it to a <tref>blank node</tref> identifier created by the
<a href="#generate-blank-node-identifier">Generate Blank Node Identifier</a> algorithm.</li>
<li>If <em>list</em> is not <tref>null</tref>, append a new <tref>subject reference</tref> to <em>list</em> using
<em>id</em> at the value for <code>@id</code>.</li>
--- a/spec/latest/json-ld-syntax/index.html Mon Jun 25 11:25:06 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html Mon Jun 25 12:54:20 2012 -0700
@@ -404,7 +404,7 @@
character is represented as a single character string.</dd>
<dt><tdef>number</tdef></dt>
<dd>
- A number is is similar to that used in most programming languages, except
+ A number is similar to that used in most programming languages, except
that the octal and hexadecimal formats are not used and that leading
zeros are not allowed.</dd>
<dt><tdef>true</tdef> and <tdef>false</tdef></dt><dd>
@@ -2338,7 +2338,7 @@
as well as the best mechanism to express these restrictions.
EBNF doesn't quite capture what these guidelines are attempting to do -
which is strongly express what constitutes a well-formed JSON-LD document.
-For the time being, a simple list of plain english guidelines are provided.
+For the time being, a simple list of plain English guidelines are provided.
</p>
<p class="issue">Per