diff --git a/enhancements/monitoring/restart-metrics.md b/enhancements/monitoring/restart-metrics.md
index 6d3810fb634..f3bde6b07cd 100644
--- a/enhancements/monitoring/restart-metrics.md
+++ b/enhancements/monitoring/restart-metrics.md
@@ -30,9 +30,9 @@ superseded-by:
 
 There is not any insight with systemd units restarting. Metrics of this sort are
 important to know if Kubelet, crio, or other system services are crashing and
-restarting. Metrics of this type are even more important, because the Kubelet is
-going to be changed to exit on a crash, thus restarting. Previous behavior of
-the Kubelet is to recover() from the crash and not exit.
+restarting. Restart metrics are going to be extremely important since the
+Kubelet is going to be changed to exit on a crash, thus restarting. Previous
+behavior of the Kubelet is to recover() from the crash and not exit.
 
 ## Motivation
 
@@ -54,7 +54,7 @@ node_exporter is running in a non-privileged container - as user `nobody` - and
 cannot connect to the DBUS socket to communicate with systemd. Monitoring has
 concerns the underlying [systemd
 collector](https://github.com/prometheus/node_exporter/blob/master/collector/systemd_linux.go)
-is not performance enough.
+is not performant enough.
 
 ## Proposal