diff --git a/docs/features/github/index.mdx b/docs/features/github/index.mdx
index 5b6146162..e4a6cceed 100644
--- a/docs/features/github/index.mdx
+++ b/docs/features/github/index.mdx
@@ -27,6 +27,6 @@ To learn how to leverage Otterize's continuous monitoring of your cluster's acce
 
 ### How does Otterize work with GitHub?
 
-After installing Otterize in your cluster, it immediately begins monitoring both incoming and outgoing network traffic to your pods and the public internet via the network mapper feature (see Network Mapper for more details). Additionally, Otterize can track activity across various resources, including Postgres, AWS, Kafka, and more. This tracking helps Otterize create a detailed map of interactions and relationships.
+After installing Otterize in your cluster, it immediately begins monitoring both incoming and outgoing network traffic to your pods and the public internet via the network mapper feature (see Network Mapper for more details). Otterize can also track activity across various resources, including PostgreSQL, AWS, Kafka, and more. Through this tracking, Otterize creates a detailed map of interactions between workloads, as well as between workloads and resources.
 
 By leveraging ClientIntents, Otterize simplifies the application and enforcement of access rights, thereby enhancing cluster security. Once ClientIntents are defined and stored in a GitHub repository, Otterize compares these intended access patterns against actual usage within the cluster. Discrepancies trigger a pull request to update the ClientIntent definitions to reflect current usage. This process enables development teams to either accept the suggested changes or adjust them based on newly observed behaviors.
\ No newline at end of file