CONTRIBUTING.md in uswds-rails-1.4.4.1 vs CONTRIBUTING.md in uswds-rails-1.4.5

@@ -14,13 +14,13 @@
 - [Making Changes](#making-changes)
 - [Code Style](#code-style)
 
 ## Getting Started
 
-uswds-rails is written in [Ruby](https://www.ruby-lang.org/en/) (version 2.4.2) and development dependencies are managed using the [Bundler](http://bundler.io/) gem. [Travis CI builds](https://travis-ci.org/jgarber623/uswds-rails) use Ruby 2.2.8, 2.3.5, and 2.4.2.
+uswds-rails is written in [Ruby](https://www.ruby-lang.org/en/) (version 2.5.0) and development dependencies are managed using the [Bundler](http://bundler.io/) gem. [Travis CI builds](https://travis-ci.org/jgarber623/uswds-rails) use Ruby 2.2.9, 2.3.6, 2.4.3, and 2.5.0.
 
-I manage Ruby versions with [rbenv](https://github.com/rbenv/rbenv). I'd recommend you do the same or use a similar Ruby version manager ([chruby](https://github.com/postmodern/chruby/) or [RVM](https://rvm.io/) come to mind). Once you've installed Ruby 2.4.2 using your method of choice, install the project's gems by running:
+I manage Ruby versions with [rbenv](https://github.com/rbenv/rbenv). I'd recommend you do the same or use a similar Ruby version manager ([chruby](https://github.com/postmodern/chruby/) or [RVM](https://rvm.io/) come to mind). Once you've installed Ruby 2.5.0 using your method of choice, install the project's gems by running:
 
 ```sh
 bundle install
 ```
 
@@ -31,10 +31,10 @@
 1. Fork and clone the project's repo.
 1. Install development dependencies as outlined above.
 1. Create a feature branch for the code changes you're looking to make: `git checkout -b your-descriptive-branch-name origin/master`.
 1. _Write some code!_
 1. Build (`bundle exec rake build`) and install (`bundle exec rake install`) your updated code.
-1. If your changes would benefit from testing, add the necessary tests and verify everything passes by running `bin/rake spec`.
+1. If your changes would benefit from testing, add the necessary tests and verify everything passes by running `bundle exec rake spec`.
 1. Commit your changes: `git commit -am 'Add some new feature or fix some issue'`. _(See [this excellent article](https://chris.beams.io/posts/git-commit/) for tips on writing useful Git commit messages.)_
 1. Push the branch to your fork: `git push -u origin your-descriptive-branch-name`.
 1. Create a new pull request and we'll review your changes.
 
 ## Code Style