NaCl docs: acquire/release/acq_rel C++11 memory order in Chrome 43 SDK

R= bradnelson@chromium.org
BUG= none

Review URL: https://codereview.chromium.org/971493004

Cr-Commit-Position: refs/heads/master@{#318820}

native_client_sdk/doc_generated/sitemap.html

@@ -42,6 +42,7 @@
 </ul>
 </li>
 <li class="toctree-l1"><a class="reference internal" href="/native-client/sdk/release-notes.html">Release Notes</a><ul class="small-gap">
+<li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-43-03-april-2015">Chrome/Pepper 43 (03 April 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-42-20-february-2015">Chrome/Pepper 42 (20 February 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-41-09-january-2015">Chrome/Pepper 41 (09 January 2015)</a></li>
 <li class="toctree-l2"><a class="reference internal" href="/native-client/sdk/release-notes.html#chrome-pepper-40-november-07-2014">Chrome/Pepper 40 (November 07 2014)</a></li>

native_client_sdk/src/doc/sdk/release-notes.rst

@@ -8,15 +8,15 @@ The dates in the following release notes denote when Chrome and the NaCl SDK
 reached canary status. The stable release is typically 6 weeks later.
 
 
-.. Chrome/Pepper 43 (03 April 2015)
-.. ===================================
-..
-.. PNaCl
-.. -----
-..
-.. * The C11/C++11 `acquire`, `release`, and `acq_rel` memory orders are now
-   generated by default. The in-browser Chrome 42 translator supports them, the
-   SDK can therefore generate them.
+Chrome/Pepper 43 (03 April 2015)
+================================
+
+PNaCl
+-----
+
+* The C11/C++11 ``acquire``, ``release``, and ``acq_rel`` memory orders are now
+  generated by default. The in-browser Chrome 42 translator supports them, the
+  SDK can therefore generate them.
 
 Chrome/Pepper 42 (20 February 2015)
 ===================================
@@ -34,18 +34,18 @@ NaCl
 ----
 
 * The x86 NaCl validators accept instructions from the FMA3 extensions, as well
-  as AVX2 instructions (except `VGATHER`).
+  as AVX2 instructions (except ``VGATHER``).
 
 PNaCl
 -----
 
-* PNaCl supports C11/C++11 memory orders `acquire`, `release`, and `acq_rel`. It
-  used to upgrade all accesses to `seq_cst`. It still upgrades `consume` to
-  `acquire` (no compiler currently implements `consume`), and `relaxed` to
-  `seq_cst` (to conservatively avoid platform differences due to out-of-thin-air
-  problems). This is currently disabled by default in the SDK so that the
-  in-browser translator installed on users' machines has time to gain this
-  support. Developers can turn it on by passing the
+* PNaCl supports C11/C++11 memory orders ``acquire``, ``release``, and
+  ``acq_rel``. It used to upgrade all accesses to ``seq_cst``. It still upgrades
+  ``consume`` to ``acquire`` (no compiler currently implements ``consume``), and
+  ``relaxed`` to ``seq_cst`` (to conservatively avoid platform differences due
+  to out-of-thin-air problems). This is currently disabled by default in the SDK
+  so that the in-browser translator installed on users' machines has time to
+  gain this support. Developers can turn it on by passing the
   ``-pnacl-memory-order-seq-cst-only=false`` flag to ``opt``.
 * PNaCl handles nested struct type expansion, which allows it to better support
   non-C languages such as Rust.