From cf7928aabc09a6619315fa87510b113b7ea3ea35 Mon Sep 17 00:00:00 2001 From: OMKAR MAKHARE Date: Thu, 19 Oct 2023 12:07:27 +0530 Subject: [PATCH] doc(README): remove typo Corrected "suite" to "suit" in the README.md file. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 96b4ee29ca4..9f86ba2dc9c 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ Wrangle your application's data management with scalable patterns for developer The `Store` is a **coordinator**. When using a `Store` you configure what cache to use, how cache data should be presented to the UI, and where it should look for requested data when it is not available in the cache. -This coordination is handled opaquely to the nature of the requests issued and the format of the data being handled. This approach gives applications broad flexibility to configure *Ember***Data** to best suite their needs. This makes *Ember***Data** a powerful solution for applications regardless of their size and complexity. +This coordination is handled opaquely to the nature of the requests issued and the format of the data being handled. This approach gives applications broad flexibility to configure *Ember***Data** to best suit their needs. This makes *Ember***Data** a powerful solution for applications regardless of their size and complexity. *Ember***Data** is designed to scale, with a religious focus on performance and asset-size to keep its footprint small but speedy while still being able to handle large complex APIs in huge data-driven applications with no additional code and no added application complexity. It's goal is to prevent applications from writing code to manage data that is difficult to maintain or reason about.