Merge pull request #26163 from olivierlacan/clarify-autoloading-disabled

Clarify and fix typos in autoloading disabled section

1 files changed, 12 insertions, 12 deletions

diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md
index 2ac5a2188b..e3b0f42a95 100644
--- a/guides/source/upgrading_ruby_on_rails.md
+++ b/guides/source/upgrading_ruby_on_rails.md
@@ -147,18 +147,18 @@ documentation.
 
 ### Autoloading is Disabled After Booting in the Production Environment
 
-Autoloading is now disabled after booting in the production environment by
-default.
-
-Eager loading the application is part of the boot process, so top-level
-constants are fine and are still autoloaded, no need to require their files.
-
-Constants in deeper places only executed at runtime, like regular method bodies,
-are also fine because the file defining them will have been eager loaded while booting.
-
-For the vast majority of applications this change needs no action. But in the
-very rare event that your application needs autoloading while running in
-production mode, set `Rails.application.config.enable_dependency_loading` to
+Autoloading of paths in `config.autoload_paths` is now disabled after booting in
+the production environment by default. Eager loading the application is part of
+the boot process. Top-level constants should still work as they are still
+autoloaded, meaning you don't need to manually require them.
+
+Constants in deeper places are only executed at runtime, like regular method
+bodies. These should also still work because their Ruby definition files will be
+eager loaded during the boot process as well.
+
+For the vast majority of applications this change requires no action. But in the
+rare situation where your application needs autoloading in the production
+environment, you can set `Rails.application.config.enable_dependency_loading` to
 true.
 
 ### XML Serialization