aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorSam Bostock <sam.bostock@shopify.com>2018-12-18 16:24:13 -0500
committerSam Bostock <sam.bostock@shopify.com>2018-12-18 16:29:00 -0500
commit61854ac301cef07a23c8982e278bf8c0b1b4c16e (patch)
tree88808c58887ac86dc74fc3b07a3b975dcf0ee7de /guides
parent28dacff5ed188099bdf662426176eeb4ec4c4d73 (diff)
downloadrails-61854ac301cef07a23c8982e278bf8c0b1b4c16e.tar.gz
rails-61854ac301cef07a23c8982e278bf8c0b1b4c16e.tar.bz2
rails-61854ac301cef07a23c8982e278bf8c0b1b4c16e.zip
Single nest config in configuration guides
Double nesting of configuration is not supported (without using an intermediate object), even though the docs suggest it is. [ci-skip]
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 029ae1a5ff..ae1de3079f 100644
--- a/guides/source/configuring.md
+++ b/guides/source/configuring.md
@@ -1404,7 +1404,7 @@ Custom configuration
You can configure your own code through the Rails configuration object with
custom configuration under either the `config.x` namespace, or `config` directly.
The key difference between these two is that you should be using `config.x` if you
-are defining _nested_ configuration (ex: `config.x.nested.nested.hi`), and just
+are defining _nested_ configuration (ex: `config.x.nested.hi`), and just
`config` for _single level_ configuration (ex: `config.hello`).
```ruby