[RF-DOCS ] Update Upgrading Rails Guide [ci-skip]

guides/source/3_1_release_notes.md

@@ -20,7 +20,7 @@ repository on GitHub.
 Upgrading to Rails 3.1
 ----------------------
 
-If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3 in case you haven't and make sure your application still runs as expected before attempting to update to Rails 3.1. Then take heed of the following changes:
+If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3 in case you haven't and make sure your application still runs as expected before attempting to update to Rails 3.1. A list of things to watch out for when upgrading is available in the [Upgrading from Rails 3.0 to Rails 3.1](upgrading_from_rails_3.0_to_3.1.html) guide.
 
 ### Rails 3.1 requires at least Ruby 1.8.7
 

guides/source/3_2_release_notes.md

@@ -20,7 +20,7 @@ repository on GitHub.
 Upgrading to Rails 3.2
 ----------------------
 
-If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3.1 in case you haven't and make sure your application still runs as expected before attempting an update to Rails 3.2. Then take heed of the following changes:
+If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3.1 in case you haven't and make sure your application still runs as expected before attempting an update to Rails 3.2. A list of things to watch out for when upgrading is available in the [Upgrading from Rails 3.1 to Rails 3.2](upgrading_from_rails_3.1_to_3.2.html) guide.
 
 ### Rails 3.2 requires at least Ruby 1.8.7
 

guides/source/4_0_release_notes.md

@@ -20,7 +20,7 @@ repository on GitHub.
 Upgrading to Rails 4.0
 ----------------------
 
-If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3.2 in case you haven't and make sure your application still runs as expected before attempting an update to Rails 4.0. A list of things to watch out for when upgrading is available in the [Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0) guide.
+If you're upgrading an existing application, it's a great idea to have good test coverage before going in. You should also first upgrade to Rails 3.2 in case you haven't and make sure your application still runs as expected before attempting an update to Rails 4.0. A list of things to watch out for when upgrading is available in the [Upgrading from Rails 3.2 to Rails 4.0](upgrading_from_rails_3.2_to_4.0.html) guide.
 
 
 Creating a Rails 4.0 application

guides/source/4_1_release_notes.md

@@ -25,7 +25,7 @@ coverage before going in. You should also first upgrade to Rails 4.0 in case you
 haven't and make sure your application still runs as expected before attempting
 an update to Rails 4.1. A list of things to watch out for when upgrading is
 available in the
-[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-4-0-to-rails-4-1)
+[Upgrading from Rails 4.0 to Rails 4.1](upgrading_from_rails_4.0_to_4.1.html)
 guide.
 
 

guides/source/4_2_release_notes.md

@@ -25,8 +25,7 @@ If you're upgrading an existing application, it's a great idea to have good test
 coverage before going in. You should also first upgrade to Rails 4.1 in case you
 haven't and make sure your application still runs as expected before attempting
 to upgrade to Rails 4.2. A list of things to watch out for when upgrading is
-available in the guide [Upgrading Ruby on
-Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-4-1-to-rails-4-2).
+available in the [Upgrading from Rails 4.1 to Rails 4.2](upgrading_from_rails_4.1_to_4.2.html) guide.
 
 
 Major Features

guides/source/5_0_release_notes.md

@@ -29,7 +29,7 @@ coverage before going in. You should also first upgrade to Rails 4.2 in case you
 haven't and make sure your application still runs as expected before attempting
 an update to Rails 5.0. A list of things to watch out for when upgrading is
 available in the
-[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0)
+[Upgrading from Rails 4.2 to Rails 5.0](upgrading_from_rails_4.2_to_5.0.html)
 guide.
 
 

guides/source/5_1_release_notes.md

@@ -29,7 +29,7 @@ coverage before going in. You should also first upgrade to Rails 5.0 in case you
 haven't and make sure your application still runs as expected before attempting
 an update to Rails 5.1. A list of things to watch out for when upgrading is
 available in the
-[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-5-0-to-rails-5-1)
+[Upgrading from Rails 5.0 to Rails 5.1](upgrading_from_rails_5.0_to_5.1.html)
 guide.
 
 

guides/source/5_2_release_notes.md

@@ -26,7 +26,7 @@ coverage before going in. You should also first upgrade to Rails 5.1 in case you
 haven't and make sure your application still runs as expected before attempting
 an update to Rails 5.2. A list of things to watch out for when upgrading is
 available in the
-[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-5-1-to-rails-5-2)
+[Upgrading from Rails 5.1 to Rails 5.2](upgrading_from_rails_5.1_to_5.2.html)
 guide.
 
 Major Features