From 0c14ad01178e7c143bd7b80440fccbd10df8a7f0 Mon Sep 17 00:00:00 2001
From: Ersin Ertan <ersin-ertan@users.noreply.github.com>
Date: Thu, 24 Mar 2016 18:51:01 -0400
Subject: [PATCH] Add java to java-less '''

---
 README.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 31556f1..364ab92 100644
--- a/README.md
+++ b/README.md
@@ -365,7 +365,7 @@ shouldn’t need this `@JsonQualifier`, but it’s very handy for those that do.
 Some models declare fields that shouldn’t be included in JSON. For example, suppose our blackjack
 hand has a `total` field with the sum of the cards:
 
-```
+```java
 public final class BlackjackHand {
   private int total;
 
@@ -376,7 +376,7 @@ public final class BlackjackHand {
 By default, all fields are emitted when encoding JSON, and all fields are accepted when decoding
 JSON. Prevent a field from being included by adding Java’s `transient` keyword:
 
-```
+```java
 public final class BlackjackHand {
   private transient int total;
 
@@ -397,7 +397,7 @@ If the class has a no-arguments constructor, Moshi will call that constructor an
 it assigns will be used. For example, because this class has a no-arguments constructor the `total`
 field is initialized to `-1`.
 
-```
+```java
 public final class BlackjackHand {
   private int total = -1;
   ...
@@ -416,7 +416,7 @@ If the class doesn’t have a no-arguments constructor, Moshi can’t assign the
 numbers, `false` for booleans, and `null` for references. In this example, the default value of
 `total` is `0`!
 
-```
+```java
 public final class BlackjackHand {
   private int total = -1;
   ...
@@ -431,7 +431,7 @@ This is surprising and is a potential source of bugs! For this reason consider d
 no-arguments constructor in classes that you use with Moshi, using `@SuppressWarnings("unused")` to
 prevent it from being inadvertently deleted later:
 
-```
+```java
 public final class BlackjackHand {
   private int total = -1;
   ...