Fix typos and enhance clarity in README.md

Corrected typos and improved clarity in README.

Author: erikw

README.md

@@ -31,13 +31,13 @@ Why use this plugin?
 
 
 ### !TL;DidRead
-There are multiple ways to [verify](https://support.google.com/webmasters/answer/9008080?hl=en) the ownership of your site. The two simpler ways, both suitable for Github Pages owners, are to add an `<meta> tag to your pages` or upload a special unique file to the root of the site. For adding the meta tag, there are excellent plugins making this very easy for example [jekyll-seo-tag](http://jekyll.github.io/jekyll-seo-tag/usage/). If you want to the meta tag, I recommend this plugin.
+There are multiple ways to [verify](https://support.google.com/webmasters/answer/9008080?hl=en) the ownership of your site. The two simpler ways, both suitable for GitHub Pages owners, are to add a `<meta> tag to your pages` or upload a special, unique file to the root of the site. For adding the meta tag, there are excellent plugins making this very easy, for example [jekyll-seo-tag](http://jekyll.github.io/jekyll-seo-tag/usage/). If you want the meta tag, I recommend this plugin.
 
-However if you feel that it's bloated to add this `<meta>` tag to the header all you pages, keeping file size and page load speed in mind, you may one to go for the file based verification method instead.
+However, if you feel that it's bloated to add this `<meta>` tag to the header of all your pages, keeping file size and page load speed in mind, you may one to go for the file-based verification method instead.
 
-So with the file based method, why not just add the file you downloaded from GSC to your source directory and let Jekyll put it in `_site/` on generation? As we're using a SSG (Static Site Generator), we should generate everything we can. It's verdantly nice to keep the source tree clean and make everything that can be a configuration that generates what is needed.
+So with the file-based method, why not just add the file you downloaded from GSC to your source directory and let Jekyll put it in `_site/` on generation? As we're using an SSG (Static Site Generator), we should generate everything we can. It's very nice to keep the source tree clean and make everything that can be a configuration that generates what is needed.
 
-Thus, this plugin exist to solve this problem. Give the plugin the unique code GSC provided you and it will generate the file for you in `_site/`!
+Thus, this plugin exists to solve this problem. Give the plugin the unique code GSC provided you, and it will generate the file for you in `_site/`!
 
 Note that if you do place a verification file in the root of the source tree, this will override the generation by this plugin.
 
@@ -60,27 +60,27 @@ Note that if you do place a verification file in the root of the source tree, th
    plugins:
      - jekyll-google_search_console_verification_file
    ```
-1. Get the GSC unique code for you website.
+1. Get the GSC unique code for your website.
    1. Register your website at [Google Search Console](https://search.google.com/search-console?resource_id=https://erikw.me/)
    1. From the main dashboard of your site at GSC: _Settings > Ownership Verification > HTML File_ and download the unique file
-   1. Instead of putting this file in our jekyll site, just copy the unique code from the HTML file name e.g. from `googlef47733b3288357e4.html` copy `f47733b3288357e4`.
+   1. Instead of putting this file in our Jekyll site, just copy the unique code from the HTML file name, e.g., from `googlef47733b3288357e4.html`, copy `f47733b3288357e4`.
 1. In your site's `_config.yml`, configure this plugin with the code from the previous step:
    ```yml
    google_search_console:
      verification_file_code: 47733b3288357e4
    ```
-1. Now just build your site and verify that the verification file now exist!
+1. Now, just build your site and verify that the verification file now exists!
    ```console
    $ bundle exec jekyll build
    $ ls _site/ | grep "google.*\.html"
    google47733b3288357e4.html
    ```
 
 # Development
-The structure of this plugin was inspired by [https://ayastreb.me/writing-a-jekyll-plugin/](https://ayastreb.me/writing-a-jekyll-plugin/), the plugin jekyll-sitemap and the [Bundler Gem tutorial](https://bundler.io/guides/creating_gem.html).
+The structure of this plugin was inspired by [https://ayastreb.me/writing-a-jekyll-plugin/](https://ayastreb.me/writing-a-jekyll-plugin/), the plugin jekyll-sitemap, and the [Bundler Gem tutorial](https://bundler.io/guides/creating_gem.html).
 
 After checking out the repo;
-1. Install [RVM](https://rvm.io/rvm/install) and install a supported ruby version (see .gemspec)
+1. Install [RVM](https://rvm.io/rvm/install) and install a supported Ruby version (see .gemspec)
 1. run `scripts/setup` to install dependencies
 1. run `scripts/test` to run the tests
 1.  You can also run `scripts/console` for an interactive prompt that will allow you to experiment.
@@ -89,7 +89,7 @@ To install this gem onto your local machine, run `bundle exec rake install`. To
 
 
 ## Local development
-Following the setup at [how-to-specify-local-ruby-gems-in-your-gemfile](https://rossta.net/blog/how-to-specify-local-ruby-gems-in-your-gemfile.html), these are the steps needed to build a jekyll site with a local clone of this plugin for local testing.
+Following the setup at [how-to-specify-local-ruby-gems-in-your-gemfile](https://rossta.net/blog/how-to-specify-local-ruby-gems-in-your-gemfile.html), these are the steps needed to build a Jekyll site with a local clone of this plugin for local testing.
 
 1. Clone this repo to your machine, say at `~/src/jekyll-google_search_console_verification_file`
 1. In your Jekyll project's `Gemfile`:
@@ -98,13 +98,13 @@ Following the setup at [how-to-specify-local-ruby-gems-in-your-gemfile](https://
 1. Configure bundler to use a local path for this gem in this project:
    - `$ bundle config --local local.jekyll-google_search_console_verification_file ~/src/jekyll-google_search_console_verification_file`
 1. Update the project: `$ bundle install`
-1. Now the project will build with the local clone of this plugin when issuing e.g. `bundle exec jekyll build`
+1. Now the project will build with the local clone of this plugin when issuing e.g., `bundle exec jekyll build`
 1. When you're done:
   - Remove the local override with: `$ bundle config --delete local.jekyll-google_search_console_verification_file`
-  - Optionally restore the original gem include in `Gemfile` or keep building from a branch in the github repo.
+  - Optionally restore the original gem included in `Gemfile` or keep building from a branch in the GitHub repo.
 
 ## Releasing
-Instructions for releasing on rubygems.org below. Optionally make a GitHub [release](https://github.com/erikw/jekyll-google_search_console_verification_file/releases) after this for the pushed git tag.
+Instructions for releasing on rubygems.org are below. Optionally make a GitHub [release](https://github.com/erikw/jekyll-google_search_console_verification_file/releases) after this for the pushed git tag.
 
 ## [manual] Using bundler/gem_tasks rake tasks
 Following instructions from [bundler.io](https://bundler.io/guides/creating_gem.html#releasing-the-gem):
@@ -129,7 +129,7 @@ gem bump --version minor --tag --push --release --sign
 For `--version`, use `major|minor|patch` as needed.
 
 ## Multi-versions
-* For ruby, just use RVM to switch between supported ruby version specified in `.gemspec`.
+* For Ruby, just use RVM to switch between supported Ruby versions specified in `.gemspec`.
 * To run with different jekyll versions, [Appraisal](https://github.com/thoughtbot/appraisal) is used with [`Appraisals`](Appraisals) to generate different [`gemfiles/`](gemfiles/)
    - To use a specific Gemfile, run like
       ```shell
@@ -156,7 +156,7 @@ To use the [travis cli client](https://github.com/travis-ci/travis.rb) (installe
    ```shell
    bundle exec travis endpoint --set-default --api-endpoint https://api.travis-ci.com/
    ```
-1. Login with the cli client
+1. Log in with the CLI client
    ```shell
    bundle exec travis login --github-token $GITHUB_TOKEN
    ```