Typo corrections

Author: fabanc

README.md

@@ -13,23 +13,23 @@ This tool is a side effect of a project I have done for work. I have explored di
 
 This tool is developed and tested for ArcGIS Pro. I have tested for ArcGIS Pro 2.7.
 
-Your python environment must be of 3.x (tested with 3.7, but I assume it work with 3.6 too). 
+Your python environment must be of 3.x (tested with 3.7, but I assume it works with 3.6 too). 
 
 The open location code library for Python must be installed in your python environment. In short
 `pip install openlocationcode`. For detailed instructions: https://github.com/google/open-location-code/tree/master/python
 
 # How to use
 
-Use the tool box in ArcGIS Pro. There is built in help in the tool metadata, and the tool is configured to guide you and minimize input errors.
+Use the tool box in ArcGIS Pro. There is built-in help in the tool metadata, and the tool is configured to guide you and minimize input errors.
 
 # How to contribute
 
 This tool has been done in rush. Though is works, it does not match my standards or the industry standards in terms of unit testing or documentation.
-If you want to help, or have any suggestion, log an issue, and a pull request if you feel bold enough.
+If you want to help, or have any suggestion, log an issue, and a pull request if you feel bold enough. Just remember to be nice.
 
 # Data Considerations
 
 Your input feature class must be using Lat / Long, on the spheroid WGS84. The wkid associated with that spatial reference system is 4326. The tool will send you a friendly error message otherwise.
 
-The tool expect a field to populate in your input feature class. That field must be of type string. Its length must be longer than the number of characters request for the plus length + 1. This is because Plus Code will add an extra character '+' after the 8th character. The minimum field length must be 9. This is because even if you ask for a Plus Code encoded on 4 characters, the API still returns 9 characters: for example `86JW0000+`. I have not figured out if that's good or bad yet. 
+The tool expects a field to populate in your input feature class. That field must be of type string. Its length must be longer than the number of characters request for the plus length + 1. This is because Plus Code will add an extra character '+' after the 8th character. The minimum field length must be 9. This is because even if you ask for a Plus Code encoded on 4 characters, the API still returns 9 characters: for example `86JW0000+`. I have not figured out if that's good or bad yet.