From ffc76861fe2e97ec63f36575bb2b3898a8b3a11d Mon Sep 17 00:00:00 2001
From: Jonathan Hall <flimzy@flimzy.com>
Date: Sat, 10 Feb 2018 14:39:14 +0100
Subject: [PATCH] Fix bash example

---
 docs/securing_installation.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/securing_installation.md b/docs/securing_installation.md
index 2db2bcfb4..2233620af 100644
--- a/docs/securing_installation.md
+++ b/docs/securing_installation.md
@@ -91,13 +91,13 @@ The following guidelines reiterate the Best Practices for securing Helm and Till
 If these steps are followed, an example `helm init` command might look something like this: 
  
 ```bash
-$ helm init \ 
-–tiller-tls \ 
-–tiller-tls-verify \ 
-–tiller-tls-ca-cert=ca.pem \ 
-–tiller-tls-cert=cert.pem \ 
-–tiller-tls-key=key.pem \ 
-–service-account=accountname  
+$ helm init \
+--tiller-tls \
+--tiller-tls-verify \
+--tiller-tls-ca-cert=ca.pem \
+--tiller-tls-cert=cert.pem \
+--tiller-tls-key=key.pem \
+--service-account=accountname  
 ```
 
 This command will start Tiller with both strong authentication over gRPC, and a service account to which RBAC policies have been applied.