Make java_classpath flag non-experimental

--
MOS_MIGRATED_REVID=126310706

2 files changed, 49 insertions, 16 deletions

diff --git a/site/blog/_posts/2016-01-27-continuous-integration.md b/site/blog/_posts/2016-01-27-continuous-integration.md
index 7158bfcace..130e0d5a41 100644
--- a/site/blog/_posts/2016-01-27-continuous-integration.md
+++ b/site/blog/_posts/2016-01-27-continuous-integration.md
@@ -92,23 +92,56 @@ A final consideration when setting up a continuous integration system is getting
 the result from the build. Bazel has the following interesting exit codes when
 using `test` and `build` commands:
 
-- 0 - Success.
-- 1 - Build failed.
-- 2 - Command Line Problem, Bad or Illegal flags or command combination, or
-  Bad Environment Variables. Your command line must be modified.
-- 2 - Command line error.
-- 3 - Build OK, but some tests failed or timed out.
-- 4 - Build successful but no tests were found even though testing was
-      requested.
-- 8 - Build interrupted (by a Ctrl+C from the user for instance) but we
-  terminated with an orderly shutdown.
+<table class="table table-condensed table-striped">
+  <thead>
+    <tr>
+      <th>Exit Code</th>
+      <th>Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0</td>
+      <td>Success.</td>
+    </tr>
+    <tr>
+      <td>1</td>
+      <td>Build failed.</td>
+    </tr>
+    <tr>
+      <td>2</td>
+      <td>
+        Command Line Problem, Bad or Illegal flags or command combination, or
+        Bad Environment Variables. Your command line must be modified.
+      </td>
+    </tr>
+    <tr>
+      <td>3</td>
+      <td>Build OK, but some tests failed or timed out.</td>
+    </tr>
+    <tr>
+      <td>4</td>
+      <td>
+        Build successful but no tests were found even though testing was
+        requested.
+      </td>
+    </tr>
+    <tr>
+      <td>8</td>
+      <td>
+        Build interrupted (by a <kbd><kbd>Ctrl</kbd>+<kbd>C</kbd></kbd> from the
+        user for instance) but we terminated with an orderly shutdown.
+      </td>
+    </tr>
+  </tbody>
+</table>
 
 These return codes can be used to determine the reason for a failure
 (in [ci.bazel.io](http://ci.bazel.io), we mark builds that have exited with exit
 code 3 as unstable, and other non zero code as failed).
 
 You can also control how much information about test results Bazel prints out
-with the [--test_output flag](http://bazel.io/docs/bazel-user-manual.html#flag--test_output).
+with the [`--test_output` flag](http://bazel.io/docs/bazel-user-manual.html#flag--test_output).
 Generally, printing the output of test that fails with `--test_output=errors` is
 a good setting for a CI system.
 
diff --git a/site/blog/_posts/2016-06-10-ide-support.md b/site/blog/_posts/2016-06-10-ide-support.md
index dbe8e729b4..11dadc27d2 100644
--- a/site/blog/_posts/2016-06-10-ide-support.md
+++ b/site/blog/_posts/2016-06-10-ide-support.md
@@ -48,13 +48,13 @@ a look at a sample
 [Eclipse plugin for Bazel support, e4b](https://github.com/bazelbuild/e4b).
 
 e4b includes an aspect, defined in a file
-[e4b_aspect.bzl](https://github.com/bazelbuild/e4b/blob/master/com.google.devtools.bazel.e4b/resources/tools/must/be/unique/e4b_aspect.bzl),
+[`e4b_aspect.bzl`](https://github.com/bazelbuild/e4b/blob/master/com.google.devtools.bazel.e4b/resources/tools/must/be/unique/e4b_aspect.bzl),
 that when
 applied to a particular target, generates a small JSON file with information
 about that target relevant to Eclipse. Those JSON files are then consumed
 by the e4b plugin inside Eclipse to build [Eclipse's representation
 of a project](https://github.com/bazelbuild/e4b/blob/master/com.google.devtools.bazel.e4b/src/com/google/devtools/bazel/e4b/classpath/BazelClasspathContainer.java),
-[IClasspathContainer](http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fjdt%2Fcore%2FIClasspathContainer.html):
+[`IClasspathContainer`](http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.jdt.doc.isv%2Freference%2Fapi%2Forg%2Feclipse%2Fjdt%2Fcore%2FIClasspathContainer.html):
 
 ![e4bazel workflow](/assets/e4b-workflow.png)
 
@@ -72,8 +72,8 @@ bazel build //java/com/company/example:main \
 [e4b source](https://github.com/bazelbuild/e4b/blob/master/com.google.devtools.bazel.e4b/src/com/google/devtools/bazel/e4b/command/BazelCommand.java) for complete
 invocation)
 
-The "--aspects" flag directs Bazel to apply e4b_aspect, exported from
-e4bazel.bzl Skylark extension, to target //java/com/company/example:main.
+The `--aspects` flag directs Bazel to apply `e4b_aspect`, exported from
+`e4bazel.bzl` Skylark extension, to target `//java/com/company/example:main`.
 
 The aspect is then applied transitively to the dependencies of the specified
 targets, producing `.e4b-build.json` files for each target in the transitive
@@ -88,7 +88,7 @@ group (and hence only to the aspect) are built, and therefore that no
 unnecessary build steps are performed.
 
 The aspect uses the
-['java' provider](/docs/skylark/lib/JavaSkylarkApiProvider.html) on the targets
+[`java` provider](/docs/skylark/lib/JavaSkylarkApiProvider.html) on the targets
 it applies to to access a variety of information about Java targets.