Remove a broken link.

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>
 <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="id3">Native Client (NaCl)</a></li>
 <li><a class="reference internal" href="#portable-native-client-pnacl" id="id4">Portable Native Client (PNaCl)</a></li>
 <li><a class="reference internal" href="#when-to-use-pnacl" id="id5">When to use PNaCl</a></li>
 <li><a class="reference internal" href="#when-to-use-nacl" id="id6">When to use NaCl</a></li>
 </ul>
 
 </div><h2 id="native-client-nacl">Native Client (NaCl)</h2>
 <p>Native Client enables the execution of native code securely inside web
-applications through the use of advanced <a class="reference external" href="/native-client/community/talks#research">Software Fault Isolation (SFI)
-techniques</a>.  Since its launch in
-2011, Native Client has provided developers with the ability to harness a
-client machine&#8217;s computational power to a much fuller extent than traditional
-web technologies, by running compiled C and C++ code at near-native speeds and
-taking advantage of multiple cores with shared memory.</p>
+applications through the use of advanced Software Fault Isolation (SFI)
+techniques.  Since its launch in 2011, Native Client has provided developers
+with the ability to harness a client machine&#8217;s computational power to a much
+fuller extent than traditional web technologies, by running compiled C and C++
+code at near-native speeds and taking advantage of multiple cores with shared
+memory.</p>
 <p>While Native Client provides operating system independence, it requires
 developers to generate architecture-specific executable
 (<strong>nexe</strong>) modules for each hardware platform. This is not only inconvenient
 for developers, but architecture-specific machine code is not portable and thus
 not well-suited for the open web. The traditional method of application
 distribution on the web is through a self-contained bundle of HTML, CSS,
 JavaScript, and other resources (images, etc.) that can be hosted on a server
 and run inside a web browser.  With this type of distribution, a website
 created today should still work years later, on all platforms.
 Architecture-specific executables are clearly not a good fit for distribution
@@ skipping 58 matching lines @@
 C standard library (the Native Client SDK provides a PNaCl port of
 <code>newlib</code>). Dynamic linking and <code>glibc</code> are not yet supported.
 Work is under way to enable dynamic linking in future versions of PNaCl.</li>
 <li>PNaCl does not support some GNU extensions
 like taking the address of a label for computed <code>goto</code>, or nested
 functions.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}