one day i will bother to look at the markdown rendering

BUG=skia:

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

diff --git a/site/dev/contrib/c++11.md b/site/dev/contrib/c++11.md
index f8506a3..cad2efa 100644 (file)
--- a/site/dev/contrib/c++11.md
+++ b/site/dev/contrib/c++11.md
@@ -9,7 +9,6 @@ document is not concerned with C++11 policy in Skia, only its technical
 feasibility.  This is about what we can use, a superset of what we may use.
 
 The gist:
-
 -   C++11 the language as supported by GCC 4.4 or later is probably usable.
 -   If you break a bot, that feature is not usable.
 -   The C++11 standard library can't generally be used.
@@ -60,12 +59,12 @@ Chrome's toolchains (see above).  I'm not exactly sure what our Chrome OS bots
 are using, but they've never been a problem.
 
 A few miscellaneous compile-only bots are actually our current overall weak link:
-    - Our NaCl builds use an old non-PNaCl toolchain, which is based on GCC
-      4.4.  GCC 4.4 has some support for C++11, but it's not nearly complete.
-      There is no upgrade path except PNaCl; even the very latest NaCl toolchain
-      is GCC 4.4, while PNaCl is based on Clang 3.4 (with complete C++11 support).
-    - Our iOS builds are driven from a Mac 10.7 machine using some unknown old Clang.
-      Who knows how old that is or what it supports?  It's probably due for an update.
+-   Our NaCl builds use an old non-PNaCl toolchain, which is based on GCC
+    4.4.  GCC 4.4 has some support for C++11, but it's not nearly complete.
+    There is no upgrade path except PNaCl; even the very latest NaCl toolchain
+    is GCC 4.4, while PNaCl is based on Clang 3.4 (with complete C++11 support).
+-   Our iOS builds are driven from a Mac 10.7 machine using some unknown old Clang.
+    Who knows how old that is or what it supports?  It's probably due for an update.
 
 If we were to eliminate the problems of the NaCl and iOS bots, our ability to
 use C++11 would match Mozilla's list nearly identically.