diff --git a/doc/upgrading.textile b/doc/upgrading.textile
index ba19f75d..efb85ced 100644
--- a/doc/upgrading.textile
+++ b/doc/upgrading.textile
@@ -8,10 +8,10 @@ That said. To upgrade:
 # Back up your existing database and installation of Tracks
 # Install Tracks 2.3devel in a new directory. Or you can create a separate installation of 2.3 for testing purposes.
 # Copy over the configuration from your previous Tracks installation. If using SQLite3, copy the old database into the new Tracks 2.3devel directory.
-# Check that you have all dependencies installed: @bundle install --without development test@ Or leave out the @--without development test@ part if you intent to test or develop on this tree.
+# Check that you have all dependencies installed: @bundle install --without development test@ Or leave out the @--without development test@ part if you intend to test or develop on this tree.
 # Run @bundle exec rake db:migrate RAILS_ENV=production@ to update your old database to the new schema. This is the point of no return. Make sure you have backups!
 # Precompile your static assets (css, javascript, etc.) by running @bundle exec rake assets:precompile@.
-# Run @bundle exec rails server -e production@ inside your Tracks 2.3devel directory to start up Tracks. Or use @-e development@ if you intent to try your changes and get more log info.
+# Run @bundle exec rails server -e production@ inside your Tracks 2.3devel directory to start up Tracks. Or use @-e development@ if you intend to try your changes and get more log info.
 
 Please note that if you intend to use Tracks with the built in webserver called WEBrick for production, you'll need to change @config.serve_static_assets@ to @true@ in @config/environments/production.rb@ in order for the images, stylesheets, and javascript files to be served correctly.