diff options
| author | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2015-11-18 13:47:45 -0200 |
|---|---|---|
| committer | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2015-11-18 13:47:45 -0200 |
| commit | a951d5b0933a4a043619bc1bccb561d499b04633 (patch) | |
| tree | 937bac9e5ac56fd98b5a18c36850348b502e590a /guides | |
| parent | ce37df9cc1f2c3cdc63dc677645bdfec05c787fe (diff) | |
| download | rails-a951d5b0933a4a043619bc1bccb561d499b04633.tar.gz rails-a951d5b0933a4a043619bc1bccb561d499b04633.tar.bz2 rails-a951d5b0933a4a043619bc1bccb561d499b04633.zip | |
Revert "Fixed a few grammar issues."
This reverts commit 16ce41b7f4449d6df15df30d69aef18da6510f36.
Reason: See
https://github.com/rails/rails/commit/16ce41b7f4449d6df15df30d69aef18da6510f36#commitcomment-14475125
Diffstat (limited to 'guides')
| -rw-r--r-- | guides/source/caching_with_rails.md | 2 | ||||
| -rw-r--r-- | guides/source/configuring.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/caching_with_rails.md b/guides/source/caching_with_rails.md index 1ae3c4918d..9a56233e4a 100644 --- a/guides/source/caching_with_rails.md +++ b/guides/source/caching_with_rails.md @@ -100,7 +100,7 @@ called key-based expiration. Cache fragments will also be expired when the view fragment changes (e.g., the HTML in the view changes). The string of characters at the end of the key is a -template tree digest. It is a md5 hash computed based on the contents of the +template tree digest. It is an md5 hash computed based on the contents of the view fragment you are caching. If you change the view fragment, the md5 hash will change, expiring the existing file. diff --git a/guides/source/configuring.md b/guides/source/configuring.md index f14b546c1b..729d1cc661 100644 --- a/guides/source/configuring.md +++ b/guides/source/configuring.md @@ -723,7 +723,7 @@ $ bin/rails runner 'puts ActiveRecord::Base.configurations' Here the connection information in `ENV['DATABASE_URL']` is ignored, note the different adapter and database name. -Since it is possible to embed ERB in your `config/database.yml` it is the best practice to explicitly show you are using the `ENV['DATABASE_URL']` to connect to your database. This is especially useful in production since you should not commit secrets like your database password into your source control (such as Git). +Since it is possible to embed ERB in your `config/database.yml` it is best practice to explicitly show you are using the `ENV['DATABASE_URL']` to connect to your database. This is especially useful in production since you should not commit secrets like your database password into your source control (such as Git). ``` $ cat config/database.yml |