API spec updates (editorial) based on Zhe Wu's review
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Mon, 01 Apr 2013 15:38:30 +0200
changeset 1511 ab677a490da7
parent 1510 9b230d75277d
child 1512 257739503f1e
API spec updates (editorial) based on Zhe Wu's review

This addresses #236.
spec/latest/json-ld-api/index.html
--- a/spec/latest/json-ld-api/index.html	Fri Mar 29 16:42:57 2013 +0100
+++ b/spec/latest/json-ld-api/index.html	Mon Apr 01 15:38:30 2013 +0200
@@ -196,8 +196,8 @@
 <section class="informative">
   <h1>Features</h1>
 
-  <p>The JSON-LD Syntax specification [[!JSON-LD]] outlines a syntax that may be
-    used to express Linked Data in JSON. Because there is more than one way to
+  <p>The JSON-LD Syntax specification [[!JSON-LD]] defines a syntax to
+    express Linked Data in JSON. Because there is more than one way to
     express Linked Data using this syntax, it is often useful to be able to
     transform JSON-LD documents so that they may be more easily consumed by
     specific applications.</p>
@@ -254,11 +254,11 @@
     </pre>
 
     <p>The next input example uses one <tref>IRI</tref> to express a property
-    and <tref title="array">array</tref> to encapsulate another, but
+    and an <tref title="array">array</tref> to encapsulate another, but
     leaves the rest of the information untouched.</p>
 
     <pre class="example" data-transform="updateExample"
-         title="Sample JSON-LD document using a IRI instead of a term to express a property">
+         title="Sample JSON-LD document using an IRI instead of a term to express a property">
     <!--
     {
       "@context": {
@@ -287,7 +287,7 @@
       information from the document is instead stored locally with each value.
       Running the <a href="#expansion-algorithm">Expansion algorithm</a>
       (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-expand-void-object-object---DOMString-input-JsonLdCallback-callback-JsonLdOptions-options">expand</a></code>
-      operation) against the examples provided above results in the following output:</p>
+      operation) against the above examples results in the following output:</p>
 
     <pre class="example" data-transform="updateExample"
          title="Expanded sample document">
@@ -732,7 +732,7 @@
     <dd>A <tref>term</tref> is a short word defined in a context that may be expanded to
       an <tref>IRI</tref></dd>
     <dt><tdef>compact IRI</tdef></dt>
-    <dd>A compact IRI is has the form of <tdef>prefix</tdef>:<em>suffix</em> and is used as a way
+    <dd>A compact IRI has the form of <tdef>prefix</tdef>:<em>suffix</em> and is used as a way
       of expressing an IRI without needing to define separate <tref>term</tref> definitions for
       each IRI contained within a common vocabulary identified by <tref>prefix</tref>.</dd>
     <dt><tdef>node object</tdef></dt>
@@ -814,7 +814,7 @@
       <h3>General Solution</h3>
 
       <p>First we prepare a new <tref>active context</tref> <i>result</i> by cloning
-        the current <tref>active context</tref>. Then we normalize the form the passed
+        the current <tref>active context</tref>. Then we normalize the form of the passed
         <tref>local context</tref> to an <tref>array</tref>.
         <tref title="local context">Local contexts</tref> may be in the form of a
         <tref>JSON object</tref>, a <tref>string</tref>, or an <tref>array</tref> containing
@@ -1736,7 +1736,7 @@
       <p>If <tref>active property</tref> has a <tref>type mapping</tref> in the
         <tref>active context</tref> set to <code>@id</code> or <code>@vocab</code>,
         a <tref>JSON object</tref> with a single member <code>@id</code> whose
-        values is the result of using the
+        value is the result of using the
         <a href="#iri-expansion">IRI Expansion algorithm</a> on <i>value</i>
         is returned.</p>
 
@@ -3835,9 +3835,9 @@
         <a>JsonLdProcessor</a> methods.</p>
       <dl title="dictionary JsonLdOptions" class="idl">
         <dt>DOMString base</dt>
-        <dd>The Base IRI to use when expanding or compacting the document. This overrides the value of
-          <em>input</em> if it is a <a>IRI</a>. If not specified and <em>input</em> is not
-          an <a>IRI</a>, the base IRI defaults to the current document IRI if in a browser context,
+        <dd>The base IRI to use when expanding or compacting the document. This overrides the value of
+          <em>input</em> if it is an IRI. If not specified and <em>input</em> is not
+          an IRI, the base IRI defaults to the current document IRI if in a browser context,
           or the empty string if there is no document context.
           <p class="issue atrisk" title="Feature at risk" data-number="223">The default value of this option
             implies that all IRIs that cannot be compacted otherwise are transformed to relative IRIs