Auto merge of #4336 - sonalkr132:man, r=segiddins

Small fixes in man pages

Sorry about cosmetic PR. I just wanted to contributing something. :smile:

3 files changed, 11 insertions, 11 deletions

diff --git a/man/bundle-install.ronn b/man/bundle-install.ronn
index 4f960f4948..b756ae2f7d 100644
--- a/man/bundle-install.ronn
+++ b/man/bundle-install.ronn
@@ -174,7 +174,7 @@ will cause an error when the Gemfile(5) is modified.
 3. Gems are installed to `vendor/bundle` not your default system location
 
    In development, it's convenient to share the gems used in your
-   application with other applications and other scripts run on
+   application with other applications and other scripts that run on
    the system.
 
    In deployment, isolation is a more important default. In addition,
@@ -195,7 +195,7 @@ that case, Bundler will stage everything in a temporary directory,
 then ask you for your `sudo` password in order to copy the gems into
 their system location.
 
-From your perspective, this is identical to installing them gems
+From your perspective, this is identical to installing the gems
 directly into the system.
 
 You should never use `sudo bundle install`. This is because several
@@ -390,7 +390,7 @@ which other gems in the Gemfile(5) still depend on, run
 
 `Summary`: In general, after making a change to the Gemfile(5) , you
 should first try to run `bundle install`, which will guarantee that no
-other gems in the Gemfile(5) are impacted by the change. If that
+other gem in the Gemfile(5) is impacted by the change. If that
 does not work, run [bundle update(1)][bundle-update].
 
 ## SEE ALSO
diff --git a/man/bundle.ronn b/man/bundle.ronn
index f81af972d3..bd01276ff0 100644
--- a/man/bundle.ronn
+++ b/man/bundle.ronn
@@ -16,10 +16,10 @@ started, and Gemfile(5) for more information on the `Gemfile` format.
 ## OPTIONS
 
 * `--no-color`:
-  Prints all output without color
+  Print all output without color
 
 * `--verbose`:
-  Prints out additional logging information
+  Print out additional logging information
 
 ## BUNDLE COMMANDS
 
@@ -44,7 +44,7 @@ We divide `bundle` subcommands into primary commands and utilities.
   Specify and read configuration options for bundler
 
 * `bundle help(1)`:
-  Displays detailed help for each subcommand
+  Display detailed help for each subcommand
 
 ## UTILITIES
 
@@ -80,10 +80,10 @@ We divide `bundle` subcommands into primary commands and utilities.
   Create a simple gem, suitable for development with bundler
 
 * [bundle platform(1)][bundle-platform]:
-  Displays platform compatibility information
+  Display platform compatibility information
 
 * `bundle clean(1)`:
-  Cleans up unused gems in your bundler directory
+  Clean up unused gems in your bundler directory
 
 ## PLUGINS
 
diff --git a/man/gemfile.5.ronn b/man/gemfile.5.ronn
index be580d9c90..dc1a6b5acb 100644
--- a/man/gemfile.5.ronn
+++ b/man/gemfile.5.ronn
@@ -35,9 +35,9 @@ this warning, by using the [`:source` option](#SOURCE-source-) or a
 
 ### CREDENTIALS (#credentials)
 
-Some gem sources require a username and password. Use `bundle config` to set
-the username and password for any sources that need it. The command must be run
-once on each computer that will install the Gemfile, but this keeps the
+Some gem sources require a username and password. Use [bundle config(1)][bundle-config] to set
+the username and password for any of the sources that need it. The command must
+be run once on each computer that will install the Gemfile, but this keeps the
 credentials from being stored in plain text in version control.
 
     bundle config gems.example.com user:password