Remove a broken link.

native_client_sdk/doc_generated/nacl-and-pnacl.html

Index: native_client_sdk/doc_generated/nacl-and-pnacl.html
diff --git a/native_client_sdk/doc_generated/nacl-and-pnacl.html b/native_client_sdk/doc_generated/nacl-and-pnacl.html
index ec83b1a38c504f15991659c327610e4d8dfd89cc..333b3fc7880483851fd06f1b6a4b71bc01280d88 100644
--- a/native_client_sdk/doc_generated/nacl-and-pnacl.html
+++ b/native_client_sdk/doc_generated/nacl-and-pnacl.html
@@ -14,12 +14,12 @@
 
 </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