Fix broken links on NaCl pages of developer.chrome.com.

native_client_sdk/doc_generated/devguide/devcycle/vs-addin.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="debugging-with-visual-studio">
 <span id="devcycle-vs-addin"></span><h1 id="debugging-with-visual-studio"><span id="devcycle-vs-addin"></span>Debugging with Visual Studio</h1>
 <div class="contents local" id="table-of-contents" style="display: none">
 <p class="topic-title first">Table Of Contents</p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
 <li><p class="first"><a class="reference internal" href="#platforms" id="id2">Platforms</a></p>
 <ul class="small-gap">
@@ skipping 399 matching lines @@
 glibc subfolders. For additional information about the parts of a Native Client
 application, see <a class="reference internal" href="/native-client/devguide/coding/application-structure.html"><em>Application Structure</em></a>.</p>
 <h3 id="using-the-debuggers">Using the debuggers</h3>
 <p>PPAPI plugins are built natively by Visual Studio’s compiler (MSBuild), and
 work with Visual Studio’s debugger in the usual way. You can set breakpoints in
 the Visual Studio source code files before you begin debugging, and on-the-fly
 while running the program.</p>
 <p>NaCl32 and NaClARM executables (.nexe files) cannot be run or debugged from
 Visual Studio.</p>
 <p>NaCl64 executables (.nexe files) are compiled using one of the Native Client
-toolchains in the SDK, which create an <a class="reference external" href="`http://en.wikipedia.org/wiki/Executable_and_Linkable_Format">ELF-formatted</a> executable. To
+toolchains in the SDK, which create an <a class="reference external" href="http://en.wikipedia.org/wiki/Executable_and_Linkable_Format">ELF-formatted</a> executable. To
 debug a running .nexe you must use nacl-gdb, which is a command line debugger
 that is not directly integrated with Visual Studio. When you start a debugging
 session running from a NaCl64 platform, Visual Studio automatically launches
 nacl-gdb for you and attaches it to the nexe. Breakpoints that you set in
 Visual Studio before you start debugging are transferred to nacl-gdb
 automatically. During a NaCl debugging session you can only use nacl-gdb
 commands.</p>
 <p>The PNaCl platform generates a .pexe file. When you run the debugger add-in
 translates the .pexe file to a .nexe file and runs the resulting binary with
 nacl-gdb attached.</p>
@@ skipping 77 matching lines @@
 </dl>
 <h4 id="nacl64-platform">NaCl64 Platform</h4>
 <dl class="docutils">
 <dt>Run the Native Client Module in the NaCl64 platform</dt>
 <dd>You are still running the STEP6 code, but as a Native Client module rather
 than a Pepper plugin.</dd>
 </dl>
 </section>
 
 {{/partials.standard_nacl_article}}