Add migration to WebAssembly information to PNaCl / NaCl docs.

native_client_sdk/doc_generated/nacl-and-pnacl.html

 {{+bindTo:partials.standard_nacl_article}}
 
-<section id="nacl-and-pnacl">
-<span id="id1"></span><h1 id="nacl-and-pnacl"><span id="id1"></span>NaCl and PNaCl</h1>
+<b><font color="#cc0000">
+NOTE:
+Deprecation of the technologies described here has been announced
+for platforms other than ChromeOS.<br/>
+Please visit our
+<a href="/native-client/migration">migration guide</a>
+for details.
+</font></b>
+<hr/><section id="id1">
+<h1 id="id1">NaCl and PNaCl</h1>
 <p>This document describes the differences between <strong>Native Client</strong> and
 <strong>Portable Native Client</strong>, and provides recommendations for when to use each.</p>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#native-client-nacl" id="id6">Native Client (NaCl)</a></li>
 <li><a class="reference internal" href="#portable-native-client-pnacl" id="id7">Portable Native Client (PNaCl)</a></li>
 <li><a class="reference internal" href="#when-to-use-pnacl" id="id8">When to use PNaCl</a></li>
 <li><a class="reference internal" href="#when-to-use-nacl" id="id9">When to use NaCl</a></li>
 </ul>
 
@@ skipping 67 matching lines @@
 with a PNaCl port of the <code>newlib</code> C standard library. Dynamic linking and
 <code>glibc</code> are not yet supported in PNaCl. Work is under way to enable dynamic
 linking in future versions of PNaCl.</li>
 <li>Your application uses certain GNU extensions not supported by PNaCl&#8217;s LLVM
 toolchain, like taking the address of a label for computed <code>goto</code>, or nested
 functions.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}