Skip to content

Commit c05d8ed

Browse files
Link methods for Rails::Engine [ci-skip]
1 parent 47b2f68 commit c05d8ed

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

railties/lib/rails/engine.rb

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ module Rails
1515
# feature and application sharing.
1616
#
1717
# 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
1920
# options that are available in railties can also be used in engines.
2021
#
2122
# == Creating an Engine
@@ -116,7 +117,7 @@ module Rails
116117
# An engine can also be a Rack application. It can be useful if you have a Rack application that
117118
# you would like to provide with some of the +Engine+'s features.
118119
#
119-
# To do that, use the +endpoint+ method:
120+
# To do that, use the ::endpoint method:
120121
#
121122
# module MyEngine
122123
# class Engine < Rails::Engine
@@ -197,7 +198,7 @@ module Rails
197198
# named routes from the application will be available to your engine's controllers as well.
198199
#
199200
# 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
201202
# you to pass a module where all your controllers, helpers, and models should be nested to:
202203
#
203204
# module MyEngine

0 commit comments

Comments
 (0)