aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorZachary Scott <e@zzak.io>2014-09-22 16:18:19 +0900
committerZachary Scott <e@zzak.io>2014-09-22 16:18:19 +0900
commit5263f5e8474e5ccc5b36a245cb878d30e237b0fd (patch)
tree9f5086067f0a48c0c614953ff86cf3a0e57e0526 /guides
parent8060959d8a43be21f9f931dd816b5f4aa7475140 (diff)
downloadrails-5263f5e8474e5ccc5b36a245cb878d30e237b0fd.tar.gz
rails-5263f5e8474e5ccc5b36a245cb878d30e237b0fd.tar.bz2
rails-5263f5e8474e5ccc5b36a245cb878d30e237b0fd.zip
Wrap it up! :trollface: [ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/4_2_release_notes.md5
1 files changed, 2 insertions, 3 deletions
diff --git a/guides/source/4_2_release_notes.md b/guides/source/4_2_release_notes.md
index 6bbe1ccfc7..c59affea8f 100644
--- a/guides/source/4_2_release_notes.md
+++ b/guides/source/4_2_release_notes.md
@@ -25,9 +25,8 @@ 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
-[Upgrading Ruby on Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-4-1-to-rails-4-2)
-guide.
+available in the guide: [Upgrading Ruby on
+Rails](upgrading_ruby_on_rails.html#upgrading-from-rails-4-1-to-rails-4-2)
Major Features