Skip to content

Commit 292b756

Browse files
authored
Fix typo in 'isComponent' reference (#6727)
1 parent 69d24e9 commit 292b756

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/modules/Blocks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ Using HTML strings as `content` is not wrong, in some cases you don't need the f
139139

140140
In such a case, all rendered elements will be converted to the best suited default component (eg. `.el-Y` elements will be treated like `text` components). The user will be able to style and drag them with no particular restrictions.
141141

142-
Thanks to Components' [isComponet](Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
142+
Thanks to Components' [isComponent](Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
143143

144144
```js
145145
// Your component

0 commit comments

Comments
 (0)