Merge branch 'dev' of https://github.com/artf/grapesjs into dev

docs/modules/Assets.md

@@ -211,7 +211,7 @@ If you need to manage your assets programmatically you have to use its [APIs][AP
 const am = editor.AssetManager;
 ```
 
-First of all, it's worth nothing that Asset Manager keeps 2 collections of assets:
+First of all, it's worth noting that Asset Manager keeps 2 collections of assets:
 * **global** - which is just the one with all available assets, you can get it with `am.getAll()`
 * **visible** - this is the collection which is currently rendered by the Asset Manager, you get it with `am.getAllVisible()`
 
@@ -590,4 +590,4 @@ am.addType('image', {
 For a complete list of available events, you can check it [here](/api/assets.html#available-events).
 
 
-[API-Asset-Manager]: </api/assets.html>
+[API-Asset-Manager]: </api/assets.html>

docs/modules/Style-manager.md

@@ -57,7 +57,7 @@ grapesjs.init({
 It makes sense to show the Style Manager UI only when you have at least one component selected, so by default the Style Manager is hidden if there are no selected components.
 :::
 
-### Sector defintions
+### Sector definitions
 
 Each sector is identified by its `name` and a list of `properties` to display. You can also specify the `id` in order to access the sector via API (if not indicated it will be generated from the `name`) and the default `open` state.
 
@@ -82,7 +82,7 @@ grapesjs.init({
 });
 ```
 
-### Property defintions
+### Property definitions
 
 Once you have defined your sector you can start adding property definitions inside `properties`. Each property has a common set of options (`label`, `default`, etc.) and others specific by their `type`.
 
@@ -867,4 +867,4 @@ For a complete list of available events, you can check it [here](/api/style_mana
 
 [Components]: <Components.html>
 [I18n]: <I18n.html>
-[Style Manager API]: </api/style_manager.html>
+[Style Manager API]: </api/style_manager.html>