Remove atrisk notes.

For w3c/json-ld-wg#150.

Author: gkellogg

index.html

@@ -4778,14 +4778,6 @@ <h3>Algorithm</h3>
     <p class="changed">If the {{JsonLdOptions/rdfDirection}} option is not `null`, then special processing is used to
       convert from an `i18n-datatype` or `compound-literal` form.</p>
 
-    <p class="issue atrisk">The support for both `i18n-datatype` and `compound-literal`
-      algorithm steps are non-normative, and are AT RISK for JSON-LD 1.1.
-      They may be replaced with normative algorithm steps in a future version.
-      Either or both of these transformation methods may be removed prior to
-      JSON-LD 1.1 being finalized.
-      The JSON-LD Working Group solicits feedback from the community on the
-      usefulness of these transformations.</p>
-
     <p class="changed">Implementations MUST generate only <dfn>well-formed</dfn>
       <a>triples</a> and <a>graph names</a>:</p>
     <ul>
@@ -5156,14 +5148,6 @@ <h3>Overview</h3>
 
       <p class="changed">If the {{JsonLdOptions/rdfDirection}} option is not `null`, then special processing is used to
         convert from an `i18n-datatype` or `compound-literal` form.</p>
-
-      <p class="issue atrisk">The support for both `i18n-datatype` and `compound-literal`
-        algorithm steps are non-normative, and are AT RISK for JSON-LD 1.1.
-        They may be replaced with normative algorithm steps in a future version.
-        Either or both of these transformation methods may be removed prior to
-        JSON-LD 1.1 being finalized.
-        The JSON-LD Working Group solicits feedback from the community on the
-        usefulness of these transformations.</p>
     </section>
 
     <section>