diff --git a/docs/features/mysql/index.mdx b/docs/features/mysql/index.mdx
index d39cf0b85..87edbaf43 100644
--- a/docs/features/mysql/index.mdx
+++ b/docs/features/mysql/index.mdx
@@ -16,7 +16,7 @@ export const mysql_tutorials = [
 
 # MySQL
 
-Otterize is able to create just-in-time username-and-password pairs for your service, providing them as a Kubernetes Secret that can be mounted to file or mapped to environment variables, as well as `GRANT`ing access to databases and tables, based on `ClientIntents` ([Intents-Based Access Control](/overview/intent-based-access-control)) declarations.
+Otterize is able to create just-in-time username-and-password pairs for your service, providing them as a Kubernetes Secret that can be mounted to file or mapped to environment variables, as well as `GRANT`ing access to databases and tables, based on `ClientIntents` ([Intent-Based Access Control](/overview/intent-based-access-control)) declarations.
 
 ### Tutorials
 
diff --git a/docs/features/postgresql/index.mdx b/docs/features/postgresql/index.mdx
index 494066693..f57a8df69 100644
--- a/docs/features/postgresql/index.mdx
+++ b/docs/features/postgresql/index.mdx
@@ -21,7 +21,7 @@ export const postgres_tutorials = [
 
 # PostgreSQL
 
-Otterize is able to create just-in-time username-and-password pairs for your service, providing them as a Kubernetes Secret that can be mounted to file or mapped to environment variables, as well as `GRANT`ing access to databases and tables, based on `ClientIntents` ([Intents-Based Access Control](/overview/intent-based-access-control)) declarations.
+Otterize is able to create just-in-time username-and-password pairs for your service, providing them as a Kubernetes Secret that can be mounted to file or mapped to environment variables, as well as `GRANT`ing access to databases and tables, based on `ClientIntents` ([Intent-Based Access Control](/overview/intent-based-access-control)) declarations.
 In addition, Otterize can map the access to your PostgreSQL database, showing you which service is accessing which database, table and which operation it's performing. This can be used to automatically generate the `ClientIntents` declarations.
 
 ### Tutorials
diff --git a/docs/overview/otterize-cloud/README.mdx b/docs/overview/otterize-cloud/README.mdx
index 6aba3b4e7..fae41a366 100644
--- a/docs/overview/otterize-cloud/README.mdx
+++ b/docs/overview/otterize-cloud/README.mdx
@@ -2,7 +2,7 @@
 title: Otterize Cloud
 ---
 
-Otterize Cloud provides a cloud-based control plane for deploying and managing [intents-based access control (IBAC)](/overview/intent-based-access-control).
+Otterize Cloud provides a cloud-based control plane for deploying and managing [intent-based access control (IBAC)](/overview/intent-based-access-control).
 
 It currently supports IBAC within Kubernetes clusters, configuring access between pods and access to Kafka nodes using network policies and Kafka ACLs.
 Soon, Otterize Cloud will also support IBAC across clusters and non-Kubernetes services and resources (e.g. standalone and managed Kafka, RDS, etc.).
diff --git a/docs/reference/IBAC-Overview.mdx b/docs/reference/IBAC-Overview.mdx
index 721bc2720..c37d16a31 100644
--- a/docs/reference/IBAC-Overview.mdx
+++ b/docs/reference/IBAC-Overview.mdx
@@ -55,7 +55,7 @@ the **enforced access layer**.
 
 <img src="/img/access-graph.png" />
 
-To implement IBAC across heterogeneous environments, IBAC must also solve for the problem of heterogeneous service identities. (Intents-based access control incorporates identity-based access control.) Since IBAC does not require developers to know about identity mechanisms any more than about authorization mechanisms, there is the requirement to **bridge the identity** of the client service to identities recognized by the target service’s infrastructures and enforcement mechanisms. Otterize builds in identity bridging mechanisms into all its integrations.
+To implement IBAC across heterogeneous environments, IBAC must also solve for the problem of heterogeneous service identities. (Intent-based access control incorporates identity-based access control.) Since IBAC does not require developers to know about identity mechanisms any more than about authorization mechanisms, there is the requirement to **bridge the identity** of the client service to identities recognized by the target service’s infrastructures and enforcement mechanisms. Otterize builds in identity bridging mechanisms into all its integrations.
 
 ### IBAC and security