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

native_client_sdk/src/doc/devguide/devcycle/vs-addin.rst

 .. _devcycle-vs-addin:
 
 ############################
 Debugging with Visual Studio
 ############################
 
 
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
@@ skipping 467 matching lines @@
 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.
 
 NaCl32 and NaClARM executables (.nexe files) cannot be run or debugged from
 Visual Studio.
 
 NaCl64 executables (.nexe files) are compiled using one of the Native Client
 toolchains in the SDK, which create an `ELF-formatted
-<`http://en.wikipedia.org/wiki/Executable_and_Linkable_Format>`_ executable. To
+<http://en.wikipedia.org/wiki/Executable_and_Linkable_Format>`_ 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.
 
 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
@@ skipping 100 matching lines @@
   functional code that is running is the same as STEP5.
 
 NaCl64 Platform
 ^^^^^^^^^^^^^^^
 
 Run the Native Client Module in the NaCl64 platform
   You are still running the STEP6 code, but as a Native Client module rather
   than a Pepper plugin.
 
 .. TODO(sbc): port reference section?