aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorJon Atack <jon@atack.com>2014-12-15 19:24:15 +0100
committerJon Atack <jonnyatack@gmail.com>2014-12-15 20:31:40 +0100
commit401b4aa956942764811e2c4787a6a2d931beecd6 (patch)
treea8f51c9d4c0e8f642381de4d242c83d2c0ed7a02 /guides
parent72a815c3fdd288c1e94953712b7540b582adfab7 (diff)
downloadrails-401b4aa956942764811e2c4787a6a2d931beecd6.tar.gz
rails-401b4aa956942764811e2c4787a6a2d931beecd6.tar.bz2
rails-401b4aa956942764811e2c4787a6a2d931beecd6.zip
Update constant_autoloading_and_reloading.md
[skip ci] Follow-up to previous commit [skip ci] Fix previous merge [skip ci]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/constant_autoloading_and_reloading.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/guides/source/constant_autoloading_and_reloading.md b/guides/source/constant_autoloading_and_reloading.md
index 9c0f9f58fc..df90c09ebe 100644
--- a/guides/source/constant_autoloading_and_reloading.md
+++ b/guides/source/constant_autoloading_and_reloading.md
@@ -7,7 +7,7 @@ After reading this guide, you will know:
* Key aspects of Ruby constants
-* What is `autoload_paths`
+* The purpose of `autoload_paths`
* How constant autoloading works
@@ -15,7 +15,7 @@ After reading this guide, you will know:
* How constant reloading works
-* That autoloading is not based on `Module#autoload`
+* Why autoloading is not based on `Module#autoload`
* Solutions to common autoloading gotchas
@@ -227,13 +227,13 @@ constants on the fly.
### Constants are Stored in Modules
Constants belong to modules in a very literal sense. Classes and modules have
-a constant table, think of it as a hash table.
+a constant table; think of it as a hash table.
-Let's analyze an example to really understand what that means. While in a
-casual setting some abuses of language are customary, the exposition is going
-to be exact here for didactic purposes.
+Let's analyze an example to really understand what that means. While figurative
+language may be customary in a casual setting, for didactic purposes we will
+be literal and precise.
-Let's consider the following module definition:
+Consider the following module definition:
```ruby
module Colors
@@ -649,7 +649,7 @@ trigger the heuristic is defined in the conflicting place.
When a module acts as a namespace, Rails does not require the application to
defines a file for it, a directory matching the namespace is enough.
-Suppose an application has a backoffice whose controllers are stored in
+Suppose an application has a back office whose controllers are stored in
`app/controllers/admin`. If the `Admin` module is not yet loaded when
`Admin::UsersController` is hit, Rails needs first to autoload the constant
`Admin`.