update readme for 0.7.2

README.md

@@ -35,18 +35,18 @@ shows you how to depend on Jawn for your project:
 
 ```scala
 // use this if you just want jawn's parser, and will implement your own facade
-libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.7.1"
+libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.7.2"
 
 // use this if you want to use jawn's parser and ast
-libraryDependencies += "org.spire-math" %% "jawn-ast" % "0.7.1"
+libraryDependencies += "org.spire-math" %% "jawn-ast" % "0.7.2"
 ```
 
 If you want to use Jawn's parser with another project's AST, see the
 "Supporting external ASTs with Jawn" section. For example, with Spray
 you would say:
 
 ```scala
-libraryDependencies += "org.spire-math" %% "spray-support" % "0.7.1"
+libraryDependencies += "org.spire-math" %% "spray-support" % "0.7.2"
 ```
 
 There are a few reasons you might want to do this:
@@ -132,7 +132,7 @@ For the following snippets, `XYZ` is one of (`argonaut`, `json4s`,
 This is how you would include the subproject in build.sbt:
 
 ```scala
-libraryDependencies += "org.spire-math" %% "XYZ-support" % "0.7.1"
+libraryDependencies += "org.spire-math" %% "XYZ-support" % "0.7.2"
 ```
 
 This is an example of how you might use the parser into your code:
@@ -154,7 +154,7 @@ To include Jawn's parser in your project, add the following
 snippet to your `build.sbt` file:
 
 ```scala
-libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.7.1"
+libraryDependencies += "org.spire-math" %% "jawn-parser" % "0.7.2"
 ```
 
 To support your AST of choice, you'll want to define a