Permalink
Browse files

Following proper naming conventions while referring to Rails, Bundler

  • Loading branch information...
1 parent e368a34 commit 330fc8c48d91b8909985fd82d7fc3761b1242526 @mceachen mceachen committed May 22, 2011
Showing with 4 additions and 4 deletions.
  1. +4 −4 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

0 comments on commit 330fc8c

Please sign in to comment.