Update Java documentation to version 1.1.3

RELEASING.md

@@ -71,7 +71,7 @@ NOTE: If you don't want to save your username and password in plaintext, [this v
 
 ### Pusing to Maven Central
 
-1. Edit `clients/java/pom.xml` with the new version number.  Keep the "-SNAPSHOT" tag.
+1. Ensure that `clients/java/pom.xml` has the new version number, with the "-SNAPSHOT" suffix.  If necessary, change the version number and commit.
 2. Make sure that your working copy is clean.  Commit or stash any lingering changes.
 3. Run `mvn release:prepare` from the `clients/java` directory.  Choose the default for the first and third questions Maven will ask you.  On the second question, use the tag name but add a `+java` to the end of it (for example, `v1.1.0+java`); this is to distringuish tags for releases in different client languages.  This command is a black box that does a lot of work, including making commits to Github with the new version tag.
 4. Confirm that there are two new commits on master, both prefixed with "[maven-release-plugin]".  If you don't see these commits, you may need to update the plugin; see https://stackoverflow.com/a/20657721/1407170

clients/java/README.md

@@ -14,7 +14,7 @@ allprojects {
 }
 
 dependencies {
-    compile 'com.google.myanmartools:myanmar-tools:1.1.2'
+    compile 'com.google.myanmartools:myanmar-tools:1.1.3'
 }
 ```
 
@@ -26,7 +26,7 @@ If you are using a pom.xml:
 <dependency>
   <groupId>com.google.myanmartools</groupId>
   <artifactId>myanmar-tools</artifactId>
-  <version>1.1.2</version>
+  <version>1.1.3</version>
 </dependency>
 ```