aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorRobin Dupret <robin.dupret@gmail.com>2019-01-26 18:13:58 +0100
committerRobin Dupret <robin.dupret@gmail.com>2019-01-26 18:13:58 +0100
commitde0c705516cf8f15f70b47e35e4117bb9d4d537c (patch)
treeac2e33a2104d5c74e026569a7517f2f893b39276 /guides
parent5a8f0c7226b2b16c9cf1b6ef5478fe5603348e17 (diff)
downloadrails-de0c705516cf8f15f70b47e35e4117bb9d4d537c.tar.gz
rails-de0c705516cf8f15f70b47e35e4117bb9d4d537c.tar.bz2
rails-de0c705516cf8f15f70b47e35e4117bb9d4d537c.zip
Fix a tiny typo [ci skip]
Follow-up to #35055.
Diffstat (limited to 'guides')
-rw-r--r--guides/source/configuring.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/configuring.md b/guides/source/configuring.md
index a329deb710..2911b1f7c3 100644
--- a/guides/source/configuring.md
+++ b/guides/source/configuring.md
@@ -1239,7 +1239,7 @@ Using Initializer Files
After loading the framework and any gems in your application, Rails turns to loading initializers. An initializer is any Ruby file stored under `config/initializers` in your application. You can use initializers to hold configuration settings that should be made after all of the frameworks and gems are loaded, such as options to configure settings for these parts.
-NOTE: There is no guarantee that your initializers will run after all the gem initilizers, so any initialization code that depends on a given gem having been initialized should go into a `config.after_initilize` block.
+NOTE: There is no guarantee that your initializers will run after all the gem initializers, so any initialization code that depends on a given gem having been initialized should go into a `config.after_initialize` block.
NOTE: You can use subfolders to organize your initializers if you like, because Rails will look into the whole file hierarchy from the initializers folder on down.