diff --git a/ej2-javascript-toc.html b/ej2-javascript-toc.html
index e1b797246..05b2d9e54 100644
--- a/ej2-javascript-toc.html
+++ b/ej2-javascript-toc.html
@@ -2963,7 +2963,7 @@
Release Notes
- - 2024 Volume 2 - 26.*
- 2024 Volume 1 - 25.*
+ - 2024 Volume 2 - 26.*
- 2024 Volume 1 - 25.*
- 2023 Volume 4 - 24.*
- 2023 Volume 3 - 23.*
- 2023 Volume 2 - 22.*
diff --git a/ej2-javascript/Release-notes/26.2.9.md b/ej2-javascript/Release-notes/26.2.9.md
new file mode 100644
index 000000000..b3644ab89
--- /dev/null
+++ b/ej2-javascript/Release-notes/26.2.9.md
@@ -0,0 +1,16 @@
+---
+title: Essential Studio for ##Platform_Name## Weekly Release Release Notes
+description: Essential Studio for ##Platform_Name## Weekly Release Release Notes
+platform: ej2-javascript
+documentation: ug
+---
+
+# Essential Studio for ##Platform_Name## Release Notes
+
+{% include release-info.html date="August 13, 2024" version="v26.2.9" %}
+
+{% directory path: _includes/release-notes/v26.2.9 %}
+
+{% include {{file.url}} %}
+
+{% enddirectory %}
\ No newline at end of file
diff --git a/ej2-javascript/code-snippet/common/getting-started-cs2/js/index.html b/ej2-javascript/code-snippet/common/getting-started-cs2/js/index.html
index bae340193..380e47a81 100644
--- a/ej2-javascript/code-snippet/common/getting-started-cs2/js/index.html
+++ b/ej2-javascript/code-snippet/common/getting-started-cs2/js/index.html
@@ -12,6 +12,7 @@
+
diff --git a/ej2-javascript/js/licensing/licensing-troubleshoot.md b/ej2-javascript/js/licensing/licensing-troubleshoot.md
index afc92611e..3ce33cbfb 100644
--- a/ej2-javascript/js/licensing/licensing-troubleshoot.md
+++ b/ej2-javascript/js/licensing/licensing-troubleshoot.md
@@ -67,11 +67,14 @@ No, the Syncfusion license keys won't expire for a particular version and you ca
## When to generate new license key while upgrading
-You don't have to generate and change license keys for minor version upgrades. If you upgrade from one major version and another major version, you have to generate new license keys and register in the application.
+You don't need to generate and change license keys for minor version upgrades. However, when upgrading from one major version to another major version, you must generate a new license key and update it in your application.
For example,
-* If you upgrade to weekly releases or the SP release in the same major version, you don't have to change license such as if you upgrade from the `20.1.47` version to `20.1.*` you don't have to change the license keys.
-* If you upgrade from one major version to another major version, you have to generate new license keys for the latest version and change in the application, such as if you upgrade from the `20.1.*` version to `20.2.*,` you have to generate new license keys for the latest version and change in the application.
+* If you are using a version like `25.1.X`, it is important to use the same version for all Syncfusion components in your application. The license key generated for version `25.X.XX` can be used. This key can be used across all minor versions within that major version, `v25`. This means you can upgrade all packages to `25.2.X` while still using the same license key.
+
+* However, if you upgrade from one major version to another—such as from `25.1.X` to `26.1.X`—you will need to generate a new license key for the latest version and update it in your application.
+
+>Note: The above-mentioned guidelines are not applicable to our packages on version `20.X.XX`, where `20.1` denotes one major version and `20.2` another major version. However, starting with our release version 21, we have adjusted the pattern. So if you are using `20.1.X`, when you upgrade to `20.2.X`, you have to generate new license keys for `20.2.X` and change in the application. Therefore, these guidelines apply to versions `21` and later.
## License registration for multiple developers on your project
diff --git a/ej2-javascript/ts/licensing/licensing-troubleshoot.md b/ej2-javascript/ts/licensing/licensing-troubleshoot.md
index 1204a1e90..eb344600f 100644
--- a/ej2-javascript/ts/licensing/licensing-troubleshoot.md
+++ b/ej2-javascript/ts/licensing/licensing-troubleshoot.md
@@ -9,7 +9,7 @@ documentation: ug
domainurl: ##DomainURL##
---
-# Licensing FAQ
+# Licensing troubleshoot in ##Platform_Name## Licensing control
## Is an internet connection required for license validation
@@ -67,11 +67,14 @@ No, the Syncfusion license keys won't expire for a particular version and you ca
## When to generate new license key while upgrading
-You don't have to generate and change license keys for minor version upgrades. If you upgrade from one major version and another major version, you have to generate new license keys and register in the application.
+You don't need to generate and change license keys for minor version upgrades. However, when upgrading from one major version to another major version, you must generate a new license key and update it in your application.
For example,
-* If you upgrade to weekly releases or the SP release in the same major version, you don't have to change license such as if you upgrade from the `20.1.47` version to `20.1.*` you don't have to change the license keys.
-* If you upgrade from one major version to another major version, you have to generate new license keys for the latest version and change in the application, such as if you upgrade from the `20.1.*` version to `20.2.*,` you have to generate new license keys for the latest version and change in the application.
+* If you are using a version like `25.1.X`, it is important to use the same version for all Syncfusion components in your application. The license key generated for version `25.X.XX` can be used. This key can be used across all minor versions within that major version, `v25`. This means you can upgrade all packages to `25.2.X` while still using the same license key.
+
+* However, if you upgrade from one major version to another—such as from `25.1.X` to `26.1.X`—you will need to generate a new license key for the latest version and update it in your application.
+
+>Note: The above-mentioned guidelines are not applicable to our packages on version `20.X.XX`, where `20.1` denotes one major version and `20.2` another major version. However, starting with our release version 21, we have adjusted the pattern. So if you are using `20.1.X`, when you upgrade to `20.2.X`, you have to generate new license keys for `20.2.X` and change in the application. Therefore, these guidelines apply to versions `21` and later.
## License registration for multiple developers on your project
diff --git a/ej2-typescript-toc.html b/ej2-typescript-toc.html
index bbe20abb9..db08ec1cf 100644
--- a/ej2-typescript-toc.html
+++ b/ej2-typescript-toc.html
@@ -2966,7 +2966,7 @@
Release Notes
- - 2024 Volume 2 - 26.*
- 2024 Volume 1 - 25.*
+ - 2024 Volume 2 - 26.*
- 2024 Volume 1 - 25.*