[NaCl SDK] docs: Remove references to obsolete debugging env vars.

native_client_sdk/doc_generated/faq.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="frequently-asked-questions">
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#what-is-native-client-good-for" id="id1">What is Native Client Good For?</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-did-google-build-native-client" id="id2">Why did Google build Native Client?</a></li>
 <li><a class="reference internal" href="#when-should-i-use-portable-native-client-instead-of-native-client" id="id3">When should I use Portable Native Client instead of Native Client?</a></li>
@@ skipping 208 matching lines @@
 the code and Makefiles for the SDK examples to understand how the
 examples are built and run.</p>
 <p>You&#8217;ll need to learn how to use some tools (like GCC, LLVM, make, Eclipse,
 Visual Studio, or Xcode) before you can get very far with the SDK. Try seaching
 for an <a class="reference external" href="https://www.google.com/search?q=gcc+introduction">introduction to GCC</a>.</p>
 </section></section><section id="openness-and-supported-architectures-and-languages">
 <h2 id="openness-and-supported-architectures-and-languages">Openness, and Supported Architectures and Languages</h2>
 <section id="is-native-client-open-is-it-a-standard">
 <h3 id="is-native-client-open-is-it-a-standard">Is Native Client open? Is it a standard?</h3>
 <p>Native Client is completely open: the executable format is open and the
-<a class="reference external" href="nacl_project_">source code is open</a>. Right
+<a class="reference external" href="https://code.google.com/p/nativeclient/">source code is open</a>. Right
 now the Native Client project is in its early stages, so it&#8217;s premature
 to consider Native Client for standardization.</p>
 <p>We consistenly try to document our design and implementation and hope to
 standardize Portable Native Client when it gains more traction. A good
 example is our <a class="reference internal" href="/native-client/reference/pnacl-bitcode-abi.html"><em>PNaCl bitcode reference manual</em></a>.</p>
 </section><section id="what-are-the-supported-instruction-set-architectures">
 <h3 id="what-are-the-supported-instruction-set-architectures">What are the supported instruction set architectures?</h3>
 <p>Portable Native Client uses an architecture-independent format (the
 <code>.pexe</code>) which can currently be translated to execute on processors
 with the x86-32, x86-64, and ARM instruction set architectures, as well
@@ skipping 271 matching lines @@
 you&#8217;re loading the correct <code>.nexe</code> file by building a separate
 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest file to
 let the browser select the correct <code>.nexe</code> file. Note: the need to
 select a processor-specific <code>.nexe</code> goes away with Portable Native
 Client.</li>
 <li>If things still aren&#8217;t working, <a class="reference internal" href="/native-client/help.html"><em>ask for help</em></a>!</li>
 </ul>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}