Gemfile(5) not Gemfile(7)

1 files changed, 11 insertions, 11 deletions

diff --git a/man/bundle-update.ronn b/man/bundle-update.ronn
index 5e66c45b80..c701a36dfa 100644
--- a/man/bundle-update.ronn
+++ b/man/bundle-update.ronn
@@ -18,7 +18,7 @@ gem.
 ## OPTIONS
 
 * `--source=<name>`:
-  The name of a `:git` or `:path` source used in the `Gemfile`. For
+  The name of a `:git` or `:path` source used in the Gemfile(5). For
   instance, with a `:git` source of `http://github.com/rails/rails.git`,
   you would call `bundle update --source rails`
 
@@ -28,7 +28,7 @@ If you run `bundle update` with no parameters, bundler will ignore
 any previously installed gems and resolve all dependencies again
 based on the latest versions of all gems available in the sources.
 
-Consider the following `Gemfile`:
+Consider the following Gemfile(5):
 
     source "http://rubygems.org"
 
@@ -67,7 +67,7 @@ all of the dependencies, all the way down, and install what you need:
 
     Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
 
-As you can see, even though you have just two gems in the `Gemfile(7)`, your application
+As you can see, even though you have just two gems in the Gemfile(5), your application
 actually needs 25 different gems in order to run. Bundler remembers the exact versions
 it installed in `Gemfile.lock`. The next time you run `bundle install(1)`, bundler skips
 the dependency resolution and installs the same gems as it installed last time.
@@ -78,7 +78,7 @@ last time. You don't need to worry that a new release of `erubis` or `mail` chan
 the gems you use.
 
 However, from time to time, you might want to update the gems you are using to the
-newest versions that still match the gems in your `Gemfile(7)`.
+newest versions that still match the gems in your Gemfile(5).
 
 To do this, run `bundle update`, which will ignore the `Gemfile.lock`, and resolve
 all the dependencies again. Keep in mind that this process can result in a significantly
@@ -87,7 +87,7 @@ authors released since the last time you ran `bundle update`.
 
 ## UPDATING A LIST OF GEMS
 
-Sometimes, you want to update a single gem in the `Gemfile(7)`, and leave the rest of the
+Sometimes, you want to update a single gem in the Gemfile(5), and leave the rest of the
 gems that you specified locked to the versions in the `Gemfile.lock`.
 
 For instance, in the scenario above, imagine that `nokogiri` releases version `1.4.4`, and
@@ -99,7 +99,7 @@ its dependencies.
 
 ## OVERLAPPING DEPENDENCIES
 
-Sometimes, multiple gems declared in your `Gemfile(1)` are satisfied by the same
+Sometimes, multiple gems declared in your Gemfile(5) are satisfied by the same
 second-level dependency. For instance, consider the case of `thin` and
 `rack-perftools-profiler`.
 
@@ -131,7 +131,7 @@ In this case, the two gems have their own set of dependencies, but they share
 `In short`, when you update a gem using `bundle update`, bundler will update all
 dependencies of that gem, including those that are also dependencies of another gem.
 
-In this scenario, updating the `thin` version manually in the `Gemfile(7)`,
+In this scenario, updating the `thin` version manually in the Gemfile(5),
 and then running `bundle install(1)` will only update `daemons` and `eventmachine`,
 but not `rack`. For more information, see the `CONSERVATIVE UPDATING` section
 of `bundle install(1)`.
@@ -141,7 +141,7 @@ of `bundle install(1)`.
 In general, when working with an application managed with bundler, you should
 use the following workflow:
 
-* After you create your `Gemfile` for the first time, run
+* After you create your Gemfile(5) for the first time, run
 
     $ bundle install
 
@@ -157,7 +157,7 @@ use the following workflow:
 
     $ bundle install --deployment
 
-* After changing the `Gemfile(7)` to reflect a new or update dependency, run
+* After changing the Gemfile(5) to reflect a new or update dependency, run
 
     $ bundle install
 
@@ -166,11 +166,11 @@ use the following workflow:
     $ git add Gemfile.lock
 
 * If `bundle install(1)` reports a conflict, manually update the specific
-  gems that you changed in the `Gemfile(7)`
+  gems that you changed in the Gemfile(5)
 
     $ bundle update rails thin
 
 * If you want to update all the gems to the latest possible versions that
-  still match the gems listed in the `Gemfile(7)`, run
+  still match the gems listed in the Gemfile(5), run
 
     $ bundle update