Permalink
Browse files

Editing the railties/../railtie.rb and engine.rb docs

  • Loading branch information...
1 parent b9e5263 commit de0753d2ae351db834d8d476caeceafb044fa6f9 @mikel mikel committed Feb 8, 2010
Showing with 7 additions and 9 deletions.
  1. +3 −4 railties/lib/rails/engine.rb
  2. +4 −5 railties/lib/rails/railtie.rb
@@ -3,9 +3,8 @@
module Rails
# Rails::Engine allows you to wrap a specific Rails application and share it accross
- # different applications. Since Rails 3.0, your Rails::Application is nothing
- # more than an Engine, thus your engines will behave much more closer to an application
- # since then.
+ # different applications. Since Rails 3.0, every Rails::Application is nothing
+ # more than an Engine, allowing you to share it very easily.
#
# Any Rails::Engine is also a Rails::Railtie, so the same methods (like rake_tasks and
# generators) and configuration available in the latter can also be used in the former.
@@ -47,7 +46,7 @@ module Rails
#
# == Paths
#
- # Since Rails 3.0, both your Application and Engines does not have hardcoded paths.
+ # Since Rails 3.0, both your Application and Engines do not have hardcoded paths.
# This means that you are not required to place your controllers at "app/controllers",
# but in any place which you find convenient.
#
@@ -8,12 +8,11 @@ module Rails
# Every major component of Rails (Action Mailer, Action Controller,
# Action View, Active Record and Active Resource) are all Railties, so each of
# them is responsible to set their own initialization. This makes, for example,
- # Rails absent of any ActiveRecord hook, allowing any other ORM to hook in.
+ # Rails absent of any ActiveRecord hook, allowing any other ORM framework to hook in.
#
- # Developing a Rails extension does not _require_ any implementation of
- # Railtie, but if you need to interact with the Rails framework
- # during boot, or after boot, then Railtie is what you need to do that
- # interaction.
+ # Developing a Rails extension does _not_ require any implementation of
+ # Railtie, but if you need to interact with the Rails framework during
+ # or after boot, then Railtie is what you need to do that interaction.
#
# For example, the following would need you to implement Railtie in your
# plugin:

0 comments on commit de0753d

Please sign in to comment.