From ae5d0712f876ce53c7fe60facd9754977ae08123 Mon Sep 17 00:00:00 2001
From: Cedric Beust <cedric@beust.com>
Date: Sat, 20 Feb 2016 11:29:43 -0800
Subject: [PATCH] Style.

---
 documentation/index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/documentation/index.html b/documentation/index.html
index 86eed20..3f45bd7 100644
--- a/documentation/index.html
+++ b/documentation/index.html
@@ -288,7 +288,7 @@ Build this project with `./kobaltw assemble`</pre>
     Kobalt just generated a full project that will create a simple Kobalt plug-in. This plug-in adds
     a simple task to Kobalt, so let's build it and test it:
 </p>
-    <pre class="brush:plain">
+<pre class="brush:plain">
 $ ./kobaltw assemble
 ----- kobalt-line-count:compile
 ----- kobalt-line-count:assemble
@@ -301,7 +301,7 @@ BUILD SUCCESSFUL (5 seconds)</pre>
     We can test this plug-in with another useful command line parameter: <code>--pluginJarFiles</code>. You give this parameter a comma-separated list of jar files, each of which is expected to be a Kobalt plug-in. Let's invoke
     Kobalt with it and ask for a list of available tasks (some of the output was elided):
 </p>
-<pre>
+<pre class="brush:plain">
 $ ./kobaltw --pluginJarFiles kobaltBuild/libs/kobalt-line-count-0.18.jar --tasks
 ...
   ===== kobalt-line-count =====
@@ -613,7 +613,7 @@ test {
   configuration will create an additional task named <code>"test"</code> followed by the name of
   that configuration. For example:
 </p>
-<pre>
+<pre class="brush:java">
 test {
     args("-excludegroups", "broken", "src/test/resources/testng.xml")
 }