Merge pull request #23629 from prathamesh-sonpatki/fix-numbers

Fix numbers of steps to upgrade Rails [ci skip]
rails · Feb 12, 2016 · 8925e37 · 8925e37
2 parents 737b718 + 2c89123
commit 8925e37
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md
@@ -23,9 +23,9 @@ When changing Rails versions, it's best to move slowly, one minor version at a t
 The process should go as follows:
 
 1. Write tests and make sure they pass
-1. Move to the latest patch version after your current version
-1. Fix tests and deprecated features
-1. Move to the latest patch version of the next minor version
+2. Move to the latest patch version after your current version
+3. Fix tests and deprecated features
+4. Move to the latest patch version of the next minor version
 
 Repeat this process until you reach your target Rails version. Each time you move versions, you will need to change the Rails version number in the Gemfile (and possibly other gem versions) and run `bundle update`. Then run the Update rake task mentioned below to update configuration files, then run your tests.