diff --git a/docs/user/01-manager.md b/docs/user/01-manager.md
index 98ac4fb27..031b3822e 100644
--- a/docs/user/01-manager.md
+++ b/docs/user/01-manager.md
@@ -2,8 +2,8 @@
 
 ## Module lifecycle
 
-Kyma's Telemetry module on its own ships a single component only, namely Telemetry Manager. Telemetry Manager is a Kubernetes [operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that is described by a custom resource of type Telemetry. Telemetry Manager implements the Kubernetes controller pattern and manages the whole lifecycle of all other components relevant to the Telemetry module.
-Telemetry Manager looks out for the user-created Kubernetes resources: LogPipeline, TracePipeline, and, in the future, MetricPipeline. In these resources, you specify what data of a signal type to collect and where to ship it.
+Kyma's Telemetry module ships Telemetry Manager as its core component. Telemetry Manager is a Kubernetes [operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that is described by a custom resource of type Telemetry. Telemetry Manager implements the Kubernetes controller pattern and manages the whole lifecycle of all other components covered in the Telemetry module.
+Telemetry Manager watches for the user-created Kubernetes resources: LogPipeline, TracePipeline, and, in the future, MetricPipeline. In these resources, you specify what data of a signal type to collect and where to ship it.
 If Telemetry Manager detects a configuration, it rolls out the relevant components on demand.
 
 ![Manager](./assets/manager-lifecycle.drawio.svg)
diff --git a/docs/user/README.md b/docs/user/README.md
index 67472ed96..2a387b0bf 100644
--- a/docs/user/README.md
+++ b/docs/user/README.md
@@ -40,8 +40,8 @@ Currently, logs are based on the Fluent Bit protocol. If you're curious about th
 
 ### Telemetry Manager
 
-Kyma's Telemetry module ships Telemetry Manager as its core component. Telemetry Manager is a Kubernetes [operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that implements the Kubernetes controller pattern and manages the whole lifecycle of all other components covered in the module. The manager watches for LogPipeline, TracePipeline, and MetricPipeline resources created by the user. With these, the user describes in a declarative way what data of a signal type to collect and where to ship it.
-If the manager detects a configuration, it rolls out the relevant collector components on demand.
+Kyma's Telemetry module ships Telemetry Manager as its core component. Telemetry Manager is a Kubernetes [operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) that implements the Kubernetes controller pattern and manages the whole lifecycle of all other components covered in the Telemetry module. Telemetry Manager watches for the user-created Kubernetes resources: LogPipeline, TracePipeline, and, in the future, MetricPipeline. In these resources, you specify what data of a signal type to collect and where to ship it.
+If Telemetry Manager detects a configuration, it rolls out the relevant components on demand.
 
 For more information, see [Telemetry Manager](/docs/user/01-manager.md).