diff --git a/docs/deployment/helm.md b/docs/deployment/helm.md
index fa0531ed8..0a5217840 100644
--- a/docs/deployment/helm.md
+++ b/docs/deployment/helm.md
@@ -86,8 +86,8 @@ deletes the release.
 
 ## Chart parameters
 
-In order to tailor the deployment of the Node Feature Discovery to your cluster needs
-We have introduced the following Chart parameters.
+To tailor the deployment of the Node Feature Discovery to your needs following
+Chart parameters are available.
 
 ### General parameters
 
diff --git a/docs/deployment/metrics.md b/docs/deployment/metrics.md
index a8ddc1956..6d12d18bb 100644
--- a/docs/deployment/metrics.md
+++ b/docs/deployment/metrics.md
@@ -48,7 +48,7 @@ to scrape metrics from NFD, you need to pass the following values to Helm:
 
 For more info on Helm deployment, see [Helm](helm.md).
 
-We recommend setting
+It is recommended to specify
 `--set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues=false`
 when deploying prometheus-operator via Helm to enable the prometheus-operator
 to scrape metrics from any PodMonitor.
diff --git a/docs/usage/customization-guide.md b/docs/usage/customization-guide.md
index a42a4769f..7903fbee8 100644
--- a/docs/usage/customization-guide.md
+++ b/docs/usage/customization-guide.md
@@ -316,7 +316,7 @@ vendor.io/feature4=featureValue4
 After processing the above file, only `vendor.io/feature2` and
 `vendor.io/feature3` would be included in the list of accepted features.
 
-> **NOTE:** The time format that we are supporting is RFC3339. Also, the `expiry-time`
+> **NOTE:** The time format supported is RFC3339. Also, the `expiry-time`
 > tag is only evaluated in each re-discovery period, and the expiration of
 > node labels is not tracked.