From f90344005e5dcf1dec2bb477c8cd6ddb29d909db Mon Sep 17 00:00:00 2001
From: Dimo Dimov <961014+dimodi@users.noreply.github.com>
Date: Fri, 20 Jun 2025 11:49:39 +0300
Subject: [PATCH] Update
 common-extend-inherit-wrap-reuse-telerik-blazor-components.md

---
 ...ommon-extend-inherit-wrap-reuse-telerik-blazor-components.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/knowledge-base/common-extend-inherit-wrap-reuse-telerik-blazor-components.md b/knowledge-base/common-extend-inherit-wrap-reuse-telerik-blazor-components.md
index 182760906e..a172e335e9 100644
--- a/knowledge-base/common-extend-inherit-wrap-reuse-telerik-blazor-components.md
+++ b/knowledge-base/common-extend-inherit-wrap-reuse-telerik-blazor-components.md
@@ -45,6 +45,8 @@ On the other hand, neither option allows changing the internal HTML rendering of
 
 > Using both options at the same time is not possible and will lead to runtime exceptions, because such a setup will nest a Telerik component in itself. The following JavaScript error will likely occur: `Cannot read properties of null (reading addEventListener)`.
 
+> The development tasks discussed in this article fall outside the Telerik support scope.
+
 ### Wrap Telerik Components
 
 This approach allows you to add additional markup or other components next to the Telerik component.