Skip to content

Spelling changes #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 17, 2018
Merged

Spelling changes #63

merged 2 commits into from
Feb 17, 2018

Conversation

fridzema
Copy link
Contributor

@fridzema fridzema commented Feb 9, 2018

No description provided.

@coveralls
Copy link

coveralls commented Feb 9, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 85fdd5d on fridzema:patch-1 into a36ca31 on GeneaLabs:master.

@@ -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
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comma here was intentional.

README.md Outdated
@@ -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
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the is unnecessary here.

README.md Outdated
@@ -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
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the comma here is correct grammar

README.md Outdated
@@ -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
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps a comma is called for here instead: good design and development practices, to help ensure

Copy link
Owner

@mikebronner mikebronner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @fridzema thanks for the PR to try to keep my spelling adventures in check :) I made a few comments, if you could revert and update those as indicated, that would be great :) Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants