From 5d1eb803b39f81bb7b69795cb47287a0fb449a9b Mon Sep 17 00:00:00 2001
From: Matt Murphy <63432827+mattmurph9@users.noreply.github.com>
Date: Thu, 12 Mar 2026 12:56:11 +0100
Subject: [PATCH] Fix typo in 'isComponent' reference

---
 docs/modules/Blocks.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/modules/Blocks.md b/docs/modules/Blocks.md
index a0bf00100..3b18abffe 100644
--- a/docs/modules/Blocks.md
+++ b/docs/modules/Blocks.md
@@ -139,7 +139,7 @@ Using HTML strings as `content` is not wrong, in some cases you don't need the f
 
 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.
 
-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`.
+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`.
 
 ```js
 // Your component