From 589d1b2f6018a6d7364512839f07bce0fee61cfe Mon Sep 17 00:00:00 2001 From: fr-miguel <44176609+fr-miguel@users.noreply.github.com> Date: Fri, 10 Jul 2020 16:52:40 -0400 Subject: [PATCH] Fix grammar This change fixes some grammar errors in the Define new storage section. --- docs/modules/Storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/Storage.md b/docs/modules/Storage.md index 36586bdaa..1aa3d4fa2 100644 --- a/docs/modules/Storage.md +++ b/docs/modules/Storage.md @@ -157,7 +157,7 @@ The Storage module has also its own [set of API](https://github.com/artf/grapesj ### Define new storage One of the most useful methods of API is the possibility to add new storages. You might think, we have the `local` and `remote` storages, what else do we need, right? Well, let's take as an example the `local` one. As you already know, it relies on [localStorage API] which is really cool and easy to use but one of his specs might be a big limit, by default it has a limited amount of MB to use per site (something around 5MB-10MB, depends on the browser implementation). As an alternative, we can make use of [IndexedDB] which is also quite [well supported](https://caniuse.com/#search=indexedDB) and allows more space usage (each browser implements its own rules, for a better understanding on how browser storage limits work, check [here](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Browser_storage_limits_and_eviction_criteria)). -[IndexedDB configuration](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB) might be too much verbose for this guide so we decided to create the [grapesjs-indexeddb] plugin, so you can check its source and see how it's implemented. For this guide we gonna see something more simpler but with the same flow, it'll be just a simple javascript object which stores key-value data, not persistent at all but the concept is the same. +[IndexedDB configuration](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Using_IndexedDB) might be too much verbose for this guide so we decided to create the [grapesjs-indexeddb] plugin, so you can check its source and see how it's implemented. For this guide we are going to see something much simpler but with the same flow, it'll be just a simple javascript object which stores key-value data, not persistent at all but the concept is the same. ```js const editor = grapesjs.init({