Following proper naming conventions while referring to Rails, Bundler

1 files changed, 4 insertions, 4 deletions

diff --git a/railties/guides/source/plugins.textile b/railties/guides/source/plugins.textile
index 842b538bc8..b71cd0c89d 100644
--- a/railties/guides/source/plugins.textile
+++ b/railties/guides/source/plugins.textile
@@ -25,14 +25,14 @@ endprologue.
 
 h3. Setup
 
-Before you continue, take a moment to decide if your new plugin will be potentially shared across different rails applications.
+Before you continue, take a moment to decide if your new plugin will be potentially shared across different Rails applications.
 
 * If your plugin is specific to your application, your new plugin will be a _vendored plugin_.
 * If you think your plugin may be used across applications, build it as a _gemified plugin_.
 
 h4. Either generate a vendored plugin...
 
-Use the +rails generate plugin+ command in your rails root directory
+Use the +rails generate plugin+ command in your Rails root directory
  to create a new plugin that will live in the +vendor/plugins+
  directory. See usage and options by asking for help:
 
@@ -42,9 +42,9 @@ $ rails generate plugin new --help
 
 h4. Or generate a gemified plugin.
 
-Writing your rails plugin as a gem, rather than as a vendored plugin,
+Writing your Rails plugin as a gem, rather than as a vendored plugin,
  lets you share your plugin across different rails applications using
- rubygems and bundler.
+ RubyGems and Bundler.
 
 Rails 3.1 ships with a +rails plugin new+ command which creates a
  skeleton for developing any kind of Rails extension with the ability