From f45328de2167a14f1a5dfcb4424fe0cd5ed92d21 Mon Sep 17 00:00:00 2001
From: Robert Fridzema <fridzema@gmail.com>
Date: Fri, 9 Feb 2018 19:10:24 +0100
Subject: [PATCH 1/2] Spelling changes

---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index c48d1fc..20627b2 100644
--- a/README.md
+++ b/README.md
@@ -10,11 +10,11 @@
 [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/GeneaLabs/laravel-model-caching/master/LICENSE)
 
 ## Impetus
-I created this package in response to a client project that had complex, nested
+I created this package in response to a client project that had complex and nested
 forms with many `<select>`'s that resulted in over 700 database queries on one
 page. I needed a package that abstracted the caching process out of the model
 for me, and one that would let me cache custom queries, as well as cache model
-relationships. This package is the attempt to address those requirements.
+relationships. This package is an attempt to address those requirements.
 
 ## Features
 -   automatic, self-invalidating relationship (both eager- and lazy-loaded) caching.
@@ -36,7 +36,7 @@ composer require genealabs/laravel-model-caching
 If you would like to use a different cache store than the default one used by
 your Laravel application, you may do so by setting the `MODEL_CACHE_STORE`
 environment variable in your `.env` file to the name of a cache store configured
-in `config/cache.php` (you can define any custom cache store base on your
+in `config/cache.php` (you can define any custom cache store based on your
 specific needs there). For example:
 ```
 MODEL_CACHE_STORE=redis
@@ -48,7 +48,7 @@ memcached). While this is optional, using a non-taggable cache provider will
 mean that the entire cache is cleared each time a model is created, saved,
 updated, or deleted.
 
-For ease of maintenance, I would recommend adding a `BaseModel` model that
+For the ease of maintenance, I would recommend adding a `BaseModel` model that
 extends `CachedModel`, from which all your other models are extended. If you
 don't want to do that, simply extend your models directly from `CachedModel`.
 
@@ -66,7 +66,7 @@ abstract class BaseModel extends CachedModel
 ```
 
 ### Exception: User Model
-I would not recommend caching the user model, as it is a special case, since it
+I would not recommend caching the user model, as it is a special case since it
 extends `Illuminate\Foundation\Auth\User`. Overriding that would break functionality.
 Not only that, but it probably isn't a good idea to cache the user model anyway,
 since you always want to pull the most up-to-date info on it.
@@ -100,7 +100,7 @@ you should see somewhere around 100% performance increase.
 
 ## Commitment to Quality
 During package development I try as best as possible to embrace good design and
-development practices to try to ensure that this package is as good as it can
+development practices trying to ensure that this package is as good as it can
 be. My checklist for package development includes:
 
 -   ✅ Achieve as close to 100% code coverage as possible using unit tests.

From 85fdd5d79bebf939f206850bcfc5570a71bd5d7d Mon Sep 17 00:00:00 2001
From: Robert Fridzema <fridzema@gmail.com>
Date: Fri, 9 Feb 2018 22:14:26 +0100
Subject: [PATCH 2/2] Update

---
 README.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 20627b2..d46d098 100644
--- a/README.md
+++ b/README.md
@@ -48,7 +48,7 @@ memcached). While this is optional, using a non-taggable cache provider will
 mean that the entire cache is cleared each time a model is created, saved,
 updated, or deleted.
 
-For the ease of maintenance, I would recommend adding a `BaseModel` model that
+For ease of maintenance, I would recommend adding a `BaseModel` model that
 extends `CachedModel`, from which all your other models are extended. If you
 don't want to do that, simply extend your models directly from `CachedModel`.
 
@@ -66,7 +66,7 @@ abstract class BaseModel extends CachedModel
 ```
 
 ### Exception: User Model
-I would not recommend caching the user model, as it is a special case since it
+I would not recommend caching the user model, as it is a special case, since it
 extends `Illuminate\Foundation\Auth\User`. Overriding that would break functionality.
 Not only that, but it probably isn't a good idea to cache the user model anyway,
 since you always want to pull the most up-to-date info on it.
@@ -99,8 +99,7 @@ In testing this has optimized performance on some pages up to 900%! Most often
 you should see somewhere around 100% performance increase.
 
 ## Commitment to Quality
-During package development I try as best as possible to embrace good design and
-development practices trying to ensure that this package is as good as it can
+During package development I try as best as possible to embrace good design and development practices, to help ensure that this package is as good as it can
 be. My checklist for package development includes:
 
 -   ✅ Achieve as close to 100% code coverage as possible using unit tests.