it's => its fixes.

Fixes #221 and fixes #223.

Author: gkellogg

common/terms.html

@@ -224,7 +224,7 @@
     and its keys are interpreted as <a>IRIs</a> representing
     the <code>@id</code> of the associated <a>node object</a>.
     If a value in the <a>id map</a> contains a key expanding to <code>@id</code>,
-    it's value MUST be equivalent to the referencing key in the <a>id map</a>.</dd>
+    its value MUST be equivalent to the referencing key in the <a>id map</a>.</dd>
   <dt><dfn data-cite="JSON-LD11#dfn-implicitly-named-graph">implicitly named graph</dfn></dt><dd>
     A <a>named graph</a> created from the value of a <a>map entry</a>
     having an <a>expanded term definition</a>
@@ -345,7 +345,7 @@
     representing the <code>@type</code> of the associated <a>node object</a>;
     the value MUST be a <a>node object</a>, or <a>array</a> of node objects.
     If the value contains a <a>term</a> expanding to <code>@type</code>,
-    it's values are merged with the map value when expanding.</dd>
+    its values are merged with the map value when expanding.</dd>
   <dt><dfn data-cite="JSON-LD11#dfn-typed-value" class="preserve">typed value</dfn></dt><dd>
     A <a>typed value</a> consists of a value,
     which is a <a>string</a>,

index.html

@@ -2947,7 +2947,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
 
   <p class="changed">In this case, the <em>property</em> term would not normally be usable as a prefix, both
     because it is defined with an <a>expanded term definition</a>, and because
-    it's <code>@id</code> does not end in a
+    its <code>@id</code> does not end in a
     <a data-cite="RFC3986#section-2.2">gen-delim</a> character. Adding
     <code>"@prefix": true</code> allows it to be used as the prefix portion of
     the <a>compact IRI</a> <em>property:One</em>.</p>
@@ -12056,7 +12056,7 @@ <h2>Id Maps</h2>
       or a <a>term</a> which expands to <code>@none</code>,
       and the values MUST be <a>node objects</a>.</p>
 
-    <p>If the value contains a property expanding to <code>@id</code>, it's value MUST
+    <p>If the value contains a property expanding to <code>@id</code>, its value MUST
       be equivalent to the referencing key. Otherwise, the property from the value is used as
       the <code>@id</code> of the <a>node object</a> value when expanding.</p>
 
@@ -12082,7 +12082,7 @@ <h2>Type Maps</h2>
       and the values MUST be <a>node objects</a>
       or <a>strings</a> which expand to <a>node objects</a>.</p>
 
-    <p>If the value contains a property expanding to <code>@type</code>, and it's value
+    <p>If the value contains a property expanding to <code>@type</code>, and its value
       is contains the referencing key after suitable expansion of both the referencing key
       and the value, then the <a>node object</a> already contains the type. Otherwise, the property from the value is
       added as a <code>@type</code> of the <a>node object</a> value when expanding.</p>