From 25596c9578b78c2fa84bf6629878f7b803d50b34 Mon Sep 17 00:00:00 2001
From: stleary <stleary@gmail.com>
Date: Sat, 21 Mar 2015 13:34:04 -0500
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 4bd1e98..2993938 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,7 @@ When adding a new unit test, don't forget to update <b>JunitTestSuite.java</b>.
 
 The fundamental issues with JSON-Java testing are:
 * <b>JSONObjects</b> are unordered, making simple string comparison ineffective. 
-* Comparisons via equals() is not currently supported. Neither <b>JSONArray</b> nor <b>JSONObject</b> overrride <b>hashCode()</b> or <b>equals()</b>, so comparison defaults to the <b>Object</b> equals(), which is not useful.
+* Comparisons via **equals()** is not currently supported. Neither <b>JSONArray</b> nor <b>JSONObject</b> overrride <b>hashCode()</b> or <b>equals()</b>, so comparison defaults to the <b>Object</b> equals(), which is not useful.
 * Access to the <b>JSONArray</b> and <b>JSONObject</b> internal containers for comparison is not currently available.
 * <b>JSONObject</b> sometimes wraps entries in quotes, other times does not, complicating comparisons.