@@ -15,7 +15,8 @@ module Rails
15
15
# feature and application sharing.
16
16
#
17
17
# Any +Rails::Engine+ is also a Rails::Railtie, so the same
18
- # methods (like <tt>rake_tasks</tt> and +generators+) and configuration
18
+ # methods (like {rake_tasks}[rdoc-ref:Rails::Railtie::rake_tasks] and
19
+ # {generators}[rdoc-ref:Rails::Railtie::generators]) and configuration
19
20
# options that are available in railties can also be used in engines.
20
21
#
21
22
# == Creating an Engine
@@ -116,7 +117,7 @@ module Rails
116
117
# An engine can also be a Rack application. It can be useful if you have a Rack application that
117
118
# you would like to provide with some of the +Engine+'s features.
118
119
#
119
- # To do that, use the + endpoint+ method:
120
+ # To do that, use the :: endpoint method:
120
121
#
121
122
# module MyEngine
122
123
# class Engine < Rails::Engine
@@ -197,7 +198,7 @@ module Rails
197
198
# named routes from the application will be available to your engine's controllers as well.
198
199
#
199
200
# However, sometimes you want to isolate your engine from the application, especially if your engine
200
- # has its own router. To do that, you simply need to call + isolate_namespace+ . This method requires
201
+ # has its own router. To do that, you simply need to call :: isolate_namespace. This method requires
201
202
# you to pass a module where all your controllers, helpers, and models should be nested to:
202
203
#
203
204
# module MyEngine
0 commit comments