diff --git a/releasenotes/notes/reduce-cadvisor-cardinality-1213854b9fe0c828.yaml b/releasenotes/notes/reduce-cadvisor-cardinality-1213854b9fe0c828.yaml
index a76a33a741..aa2e115ad4 100644
--- a/releasenotes/notes/reduce-cadvisor-cardinality-1213854b9fe0c828.yaml
+++ b/releasenotes/notes/reduce-cadvisor-cardinality-1213854b9fe0c828.yaml
@@ -13,7 +13,7 @@ upgrade:
   - |
     cAdvisor has now reduced number of Prometheus metrics and labels
     exported by default. This means that corresponding timeseries will
-    no longer be created. If existing setup relies on these, eg. for
+    no longer be created. If existing setup relies on these, e.g. for
     visualisation or alerting, they could be explicitly enabled prior to
     upgrading with the ``prometheus_cadvisor_cmdline_extras`` new variable.
     Reference for the possible options: `<https://github.com/google/cadvisor/blob/master/docs/runtime_options.md#metrics>`_.
diff --git a/releasenotes/notes/remove-prometheus-v1-8fa9c74c3dda568e.yaml b/releasenotes/notes/remove-prometheus-v1-8fa9c74c3dda568e.yaml
index 9b04dba85f..d56e6af969 100644
--- a/releasenotes/notes/remove-prometheus-v1-8fa9c74c3dda568e.yaml
+++ b/releasenotes/notes/remove-prometheus-v1-8fa9c74c3dda568e.yaml
@@ -2,6 +2,6 @@
 upgrade:
   - |
     Removes support for Prometheus v1 deployment. Any previously deployed
-    Prometheus v1 instances will create a conflict during an upgrade thus
+    Prometheus v1 instances will create a conflict during an upgrade. They
     should be either manually stopped/removed or Prometheus v2 deployment
     should be disabled by setting ``enable_prometheus`` to ``no``.