Fixed a few grammar issues.

2 files changed, 2 insertions, 2 deletions

diff --git a/guides/source/caching_with_rails.md b/guides/source/caching_with_rails.md
index 9a56233e4a..1ae3c4918d 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 an md5 hash computed based on the contents of the
+template tree digest. It is a 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 729d1cc661..f14b546c1b 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 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 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).
 
 ```
 $ cat config/database.yml