From 708611203f6cd34a0234dffbd9a247ac9b30f94c Mon Sep 17 00:00:00 2001 From: Max Williams Date: Mon, 12 Nov 2018 10:50:30 +0100 Subject: [PATCH] Some small grammar changes Signed-off-by: Max Williams --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 85272eeb..e3eed3e8 100644 --- a/README.md +++ b/README.md @@ -117,7 +117,10 @@ The easiest way to install node-problem-detector into your cluster is to use the helm install stable/node-problem-detector ``` -Alternatively you can edit [node-problem-detector.yaml](deployment/node-problem-detector.yaml) to fit your environment. Set `log` volume to your system log directory (used by SystemLogMonitor). For Kubernetes versions older than 1.9 use [node-problem-detector-old.yaml](deployment/node-problem-detector-old.yaml). Create the DaemonSet with `kubectl create -f deployment/node-problem-detector.yaml`. If needed, you can use a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) to overwrite the `config` directory inside the pod. +Alternatively, you can edit [node-problem-detector.yaml](deployment/node-problem-detector.yaml) to fit your environment. Set `log` volume to your system log directory (used by SystemLogMonitor). For Kubernetes versions older than 1.9, use [node-problem-detector-old.yaml](deployment/node-problem-detector-old.yaml). + +- Create the DaemonSet with `kubectl create -f deployment/node-problem-detector.yaml`. +- If needed, you can use a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) to overwrite the `config` directory inside the pod. ## Start Standalone