From 0951183d64a0b4858c8f2b1d9fd6605684717ae3 Mon Sep 17 00:00:00 2001 From: XsWack Date: Mon, 7 Aug 2017 09:30:42 +0800 Subject: [PATCH] Update managing-tls-in-a-cluster.md fix typo --- docs/tasks/tls/managing-tls-in-a-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/tls/managing-tls-in-a-cluster.md b/docs/tasks/tls/managing-tls-in-a-cluster.md index ce149f5735..bae41b6c90 100644 --- a/docs/tasks/tls/managing-tls-in-a-cluster.md +++ b/docs/tasks/tls/managing-tls-in-a-cluster.md @@ -191,7 +191,7 @@ the CSR and otherwise should deny the CSR. The ability to approve CSRs decides who trusts who within the cluster. This includes who the Kubernetes API trusts. The ability to approve CSRs should not be granted broadly or lightly. The requirements of the challenge -noted in the previous section and the reprecussions of issuing a specific +noted in the previous section and the repercussions of issuing a specific certificate should be fully understood before granting this permission. See [here](/docs/admin/authentication#x509-client-certs) for information on how certificates interact with authentication.