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

native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst

Index: native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
diff --git a/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst b/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
index c143e1df2bd48126f02a864beb4056345807b4e0..2324774fa8c20b4d393bc058155489d823d9f034 100644
--- a/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
+++ b/native_client_sdk/src/doc/reference/pnacl-c-cpp-language-support.rst
@@ -50,8 +50,8 @@ Memory Model for Concurrent Operations
 
 The memory model offered by PNaCl relies on the same coding guidelines
 as the C11/C++11 one: concurrent accesses must always occur through
-atomic primitives (offered by `atomic intrinsics
-<PNaClLangRef.html#atomicintrinsics>`_), and these accesses must always
+atomic primitives (offered by :ref:`atomic intrinsics 
+<bitcode_atomicintrinsics>`), and these accesses must always
 occur with the same size for the same memory location. Visibility of
 stores is provided on a happens-before basis that relates memory
 locations to each other as the C11/C++11 standards do.