docs: fix typos (#6147)

* fix typos

docs/Home.md

@@ -172,7 +172,7 @@ You could add other commands to enable interactions with blocks. Check [Built-in
 
 ## Style Manager
 
-Any HTML structure requires, at some point, a proper style, so to meet this need the Style Manager was added as a built-in feature in GrapesJS. Style manager is composed by sectors, which group inside different types of CSS properties. So you can add, for instance, a `Dimension` sector for `width` and `height`, and another one as `Typography` for `font-size` and `color`. So it's up to you decide how organize sectors.
+Any HTML structure requires, at some point, a proper style, so to meet this need the Style Manager was added as a built-in feature in GrapesJS. Style manager is composed by sectors, which group inside different types of CSS properties. So you can add, for instance, a `Dimension` sector for `width` and `height`, and another one as `Typography` for `font-size` and `color`. So it's up to you to decide how to organize sectors.
 
 To enable this module we rely on a built-in command `open-sm`, which shows up the Style Manager, which we gonna bind to another button in a separate panel
 
@@ -228,7 +228,7 @@ Selecting one of the component will show up the Style Manager with default secto
 
 [[img/default-sm.jpg]]
 
-As we exploring different configurations inside GrapesJS we gonna overwrite all the default sectors to create some custom one
+As we explore different configurations inside GrapesJS we gonna overwrite all the default sectors to create some custom one
 
 Let's put a few sectors with use of `buildProps` which helps us building common properties
 
@@ -356,7 +356,7 @@ styleManager : {
 ...
 ```
 
-As you can see using `buildProps` actually will save you a lot of work. You could also mix this techniques to obtain custom properties in less time. For example, let's see how can we setup the same width but with a different value of `min`:
+As you can see using `buildProps` actually will save you a lot of work. You could also mix these techniques to obtain custom properties in less time. For example, let's see how we can setup the same width but with a different value of `min`:
 
 ```js
 ...
@@ -402,7 +402,7 @@ var editor = grapesjs.init({
 ...
 ```
 
-Worth noting the defaut `id` parameter which adds a prefix for all keys to store. If you check the localStorage inside your DOM panel you'll see something like `{ 'gjs-components': '<div>....' ...}` in this way it prevents the risk of collisions, quite common with localStorage use in large applications.
+Worth noting the default `id` parameter which adds a prefix for all keys to store. If you check the localStorage inside your DOM panel you'll see something like `{ 'gjs-components': '<div>....' ...}` in this way it prevents the risk of collisions, quite common with localStorage use in large applications.
 
 Storing data locally it's easy and fast but useless in some common cases. In the next example we'll see how to setup a remote storage, which is not far from the previous one
 

docs/modules/Assets.md

@@ -78,7 +78,7 @@ editor.runCommand('open-assets');
 ```
 
 
-Worth nothing that by doing this you can't do much with assets (if you double click on them nothing happens) and this is because you've not indicated any target. Try just to select an image in your canvas and run this in console (you should first make the editor globally available `window.editor = editor;` in your script)
+Worth noting that by doing this you can't do much with assets (if you double click on them nothing happens) and this is because you've not indicated any target. Try just to select an image in your canvas and run this in console (you should first make the editor globally available `window.editor = editor;` in your script)
 
 ```js
 editor.runCommand('open-assets', {
@@ -225,7 +225,7 @@ am.getAll().length; // <- 3
 am.getAllVisible().length; // <- 3
 ```
 
-Ok, now let's show only assets form the first category
+Ok, now let's show only assets from the first category
 
 ```js
 const assets = am.getAll();
@@ -325,7 +325,7 @@ Here an example of using custom Asset Manager with a Vue component.
 The example above is the right way if you need to replace the default UI, but as you might notice we append the mounted element to the container `props.container.appendChild(this.$el);`.
 This is required as the Asset Manager, by default, is placed in the [Modal](/modules/Modal.html).
 
-How to approach the case when your Asset Manager is a completely independent/external module (eg. should be showed in its own custom modal)? Not a problem, you can bind the Asset Manager state via `assetManager.custom.open`.
+How to approach the case when your Asset Manager is a completely independent/external module (eg. should be shown in its own custom modal)? Not a problem, you can bind the Asset Manager state via `assetManager.custom.open`.
 
 ```js
 const editor = grapesjs.init({
@@ -339,7 +339,7 @@ const editor = grapesjs.init({
         // Init and open your external Asset Manager
         // ...
         // IMPORTANT:
-        // When the external library is closed you have to comunicate
+        // When the external library is closed you have to communicate
         // this state back to the editor, otherwise GrapesJS will think
         // the Asset Manager is still open.
         // example: myAssetManager.on('close', () => props.close())
@@ -357,10 +357,10 @@ It's important to declare also the `close` function, the editor should be able t
 <!--
 ### Define new Asset type
 
-Generally speaking, images aren't the only asset you'll use, it could be a `video`, `svg-icon`, or any other kind of `document`. Each type of asset is applied in our templates/pages differently. If you need to change the image of the Component all you need is another `url` in `src` attribute. However In case of a `svg-icon`, its not the same, you might want to replace the element with a new `<svg>` content. Besides this you also have to deal with the presentation/preview of the asset inside the panel/modal. For example, showing a thumbnail for big images or the possibility to preview videos.
+Generally speaking, images aren't the only asset you'll use, it could be a `video`, `svg-icon`, or any other kind of `document`. Each type of asset is applied in our templates/pages differently. If you need to change the image of the Component all you need is another `url` in `src` attribute. However In case of a `svg-icon`, it's not the same, you might want to replace the element with a new `<svg>` content. Besides this you also have to deal with the presentation/preview of the asset inside the panel/modal. For example, showing a thumbnail for big images or the possibility to preview videos.
 
 
-Defining a new asset it means we have to push on top of the 'Stack of Types' a new layer. This stack is iterated over by the editor at any addition of the asset and tries to associate the correct type.
+Defining a new asset means we have to push on top of the 'Stack of Types' a new layer. This stack is iterated over by the editor at any addition of the asset and tries to associate the correct type.
 
 ```js
 am.add('https://.../image.png');