Skip to content

Commit ccda39e

Browse files
authored
Merge pull request #568 from MelvinLoos/patch-1
Fixed some grammatical errors and/or typos.
2 parents 431742a + fea0876 commit ccda39e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

core/design.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,10 @@ For [Rapid Application Development](https://en.wikipedia.org/wiki/Rapid_applicat
3333
ORM's data provider and persister implementations shipped with API Platform.
3434

3535
In this case, the public (`@ApiResource`) and internal (Doctrine entity) data model are shared. Then, API Platform will
36-
be able to query, filter, paginate and persist automatically data.
37-
This is approach is super-convenient and efficient, but is probably **not a good idea** for non-[CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
36+
be able to query, filter, paginate and persist data automatically.
37+
This approach is super-convenient and efficient, but is probably **not a good idea** for non-[CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete)
3838
and/or large systems.
39-
Again, it's up to the developers to use, or to not use those built-in data providers/persisters depending of the business
39+
Again, it's up to the developers to use, or to not use those built-in data providers/persisters depending on the business
4040
they are dealing with. API Platform makes it easy to create custom data providers and persisters, and to implement appropriate
4141
patterns such as [CQS](https://www.martinfowler.com/bliki/CommandQuerySeparation.html) or [CQRS](https://martinfowler.com/bliki/CQRS.html).
4242

0 commit comments

Comments
 (0)