diff --git a/_data/components/filterexpressionmethods.yml b/_data/components/filterexpressionmethods.yml
index 88b8c1dc1..26b21651e 100644
--- a/_data/components/filterexpressionmethods.yml
+++ b/_data/components/filterexpressionmethods.yml
@@ -368,7 +368,7 @@ utilityMethods: [
   },
   {
     name: "instanceofBasicExpression",
-    description: "Evaluates if the the expression provided is an instance of `IBasicExpression`.",
+    description: "Evaluates if the expression provided is an instance of `IBasicExpression`.",
     params: [
       {
         name: "exp",
diff --git a/docs/addons/39-ontimize-web-ngx-jee-seed.md b/docs/addons/39-ontimize-web-ngx-jee-seed.md
index c40e4e35e..cd69dd114 100644
--- a/docs/addons/39-ontimize-web-ngx-jee-seed.md
+++ b/docs/addons/39-ontimize-web-ngx-jee-seed.md
@@ -11,7 +11,7 @@ nav_order: 5
 
 ## Introduction
 
-The The **Ontimize Web Java EE app seed** is a seed proyect created to start developing your [OntimizeWeb](https://github.com/OntimizeWeb/ontimize-web-ngx/tree/main.15.x){:target="_blank"} applications faster and easily.
+The **Ontimize Web Java EE app seed** is a seed proyect created to start developing your [OntimizeWeb](https://github.com/OntimizeWeb/ontimize-web-ngx/tree/main.15.x){:target="_blank"} applications faster and easily.
 
 ## Github
 Ontimize Web JEE application seed is stored in [github](https://github.com/OntimizeWeb/ontimize-web-ngx-jee-seed/tree/15.x.x){:target="_blank"} where you can also see/add todos, bugs or feature requests in the [issues](https://github.com/OntimizeWeb/ontimize-web-ngx-jee-seed/issues){:target="_blank"} section.
diff --git a/docs/components/input/00-overview.service-component.md b/docs/components/input/00-overview.service-component.md
index 56342974d..36125341e 100644
--- a/docs/components/input/00-overview.service-component.md
+++ b/docs/components/input/00-overview.service-component.md
@@ -39,7 +39,7 @@ Form service components extends this behaviour and go one step forward, they all
 </o-form>
 ```
 
-In this example there is a form for linking users and roles, the roles the user may be linked with depend on the type of the user. The user type is part of the user information queried in the first combo. Notice that the the parent keys attribute for the roles combo has an alias and a column defined for the alias. This will make the roles component to look for the value of its parent key in the component with attr `user` and it will take the `user_type` column value as its parent key value.
+In this example there is a form for linking users and roles, the roles the user may be linked with depend on the type of the user. The user type is part of the user information queried in the first combo. Notice that the parent keys attribute for the roles combo has an alias and a column defined for the alias. This will make the roles component to look for the value of its parent key in the component with attr `user` and it will take the `user_type` column value as its parent key value.
 
 The construction of dependant list-pickers is the same as done in the combo component. The first one is the selector of users, this will be the one that affects the second one.