Additional explanation about cache implementations

1 files changed, 7 insertions, 1 deletions

diff --git a/guides/source/caching_with_rails.md b/guides/source/caching_with_rails.md
index aa79f59e4f..798fea9f30 100644
--- a/guides/source/caching_with_rails.md
+++ b/guides/source/caching_with_rails.md
@@ -387,6 +387,11 @@ store is not appropriate for large application deployments. However, it can
 work well for small, low traffic sites with only a couple of server processes,
 as well as development and test environments.
 
+New Rails projects will be configured to use this implementation in the
+development environment by default. (Note that, because processes will not share
+cache data, if using `:memory_store` it will not be possible to manually read,
+write or expire the cache via the Rails console.)
+
 ### ActiveSupport::Cache::FileStore
 
 This cache store uses the file system to store entries. The path to the directory where the store files will be stored must be specified when initializing the cache.
@@ -403,7 +408,8 @@ share a cache by using a shared file system, but that setup is not recommended.
 As the cache will grow until the disk is full, it is recommended to
 periodically clear out old entries.
 
-This is the default cache store implementation.
+This is the default cache store implementation (at `"#{root}/tmp/cache/"`) if
+no explicit `config.cache_store` is supplied.
 
 ### ActiveSupport::Cache::MemCacheStore