Clean up language and spacing.

README.md

@@ -742,14 +742,15 @@ Known Issue
 
 You cannot use the `near` scope with another scope that provides an `includes` option because the `SELECT` clause generated by `near` will overwrite it (or vice versa). 
 
-Instead of using `includes` to reduce the number of database queries, try using `joins` with either the `:select` option or a call to `preload`. Both choices are demonstrated below:
+Instead of using `includes` to reduce the number of database queries, try using `joins` with either the `:select` option or a call to `preload`. For example:
 
     # Pass a :select option to the near scope to get the columns you want.
     # Instead of City.near(...).includes(:venues), try:
     City.near("Omaha, NE", 20, :select => "cities.*, venues.*").joins(:venues)
-    
-    # This preload call will normally trigger 2 queries regardless of the number of results; one query 
-    # on hotels, and one query on administrators.  Instead of Hotel.near(...).includes(:administrator), try:
+
+    # This preload call will normally trigger two queries regardless of the
+    # number of results; one query on hotels, and one query on administrators.
+    # Instead of Hotel.near(...).includes(:administrator), try:
     Hotel.near("London, UK", 50).joins(:administrator).preload(:administrator)
 
 If anyone has a more elegant solution to this problem I am very interested in seeing it.