From 0ad4eeeca9f6021b3036976465de4cc50664b8ef Mon Sep 17 00:00:00 2001 From: Malepati Bala Siva Sai Akhil Date: Thu, 17 Aug 2017 03:29:26 +0530 Subject: [PATCH] Fix minor typos in Prerequisites --- examples/PREREQUISITES.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/PREREQUISITES.md b/examples/PREREQUISITES.md index a2c12ad2a..03f9f74a4 100644 --- a/examples/PREREQUISITES.md +++ b/examples/PREREQUISITES.md @@ -40,7 +40,7 @@ secret "tls-secret" created You can act as your very own CA, or use an existing one. As an exercise / learning, we're going to generate our own CA, and also generate a client certificate. -These instructions are based in CoreOS OpenSSL [instructions](https://coreos.com/kubernetes/docs/latest/openssl.html) +These instructions are based on CoreOS OpenSSL [instructions](https://coreos.com/kubernetes/docs/latest/openssl.html) ### Generating a CA @@ -72,7 +72,7 @@ This will generate two files: A private key (ca.key) and a public key (ca.crt). The ca.crt can be used later in the step of creation of CA authentication secret. ### Generating the client certificate -The following steps generates a client certificate signed by the CA generated above. This client can be +The following steps generate a client certificate signed by the CA generated above. This client can be used to authenticate in a tls-auth configured ingress. First, we need to generate an 'openssl.cnf' file that will be used while signing the keys: