From d1dc32aadbaac58c2c6fbbbf752256b8f47d92e5 Mon Sep 17 00:00:00 2001
From: Matteo <matteo@pop-os.localdomain>
Date: Wed, 23 Oct 2019 16:17:16 +0200
Subject: [PATCH] Format README

---
 2019-edition/README.md | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/2019-edition/README.md b/2019-edition/README.md
index acbe878..db44b9a 100644
--- a/2019-edition/README.md
+++ b/2019-edition/README.md
@@ -1,22 +1,25 @@
-# Deploying application with Helm
+# Deploying applications with Helm
 
-## Configure tiller inside the kube-system namespace 
-
-Source: https://docs.bitnami.com/kubernetes/how-to/configure-rbac-in-your-kubernetes-cluster/
+## Configure Tiller server inside the kube-system namespace 
 
 1. kubectl --namespace kube-system create sa tiller
+
 2. kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
 
-Now create the tiller pod in the kube-system namespace
+Now create the tiller pod inside the kube-system namespace
 
 ```
 helm init --service-account tiller --override spec.selector.matchLabels.'name'='tiller',spec.selector.matchLabels.'app'='helm' --output yaml | sed 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' | kubectl apply -f -
 ```
 
+Source: https://docs.bitnami.com/kubernetes/how-to/configure-rbac-in-your-kubernetes-cluster/
+
 ---
 **NOTE**
 
-Helm init currently creates a deployment.yaml for Tiller with deprecated extensions/v1beta1 API. This is the current behaviour of helm 2.15 with kubernetes v.1.16 and simply executing helm --init doesn't deploy the tiller server. 
+Helm init currently creates a deployment.yaml for Tiller with deprecated extensions/v1beta1 API. 
+
+This is the current behaviour of helm 2.15 with kubernetes v.1.16 and simply executing helm --init doesn't deploy the tiller server. 
 
 This command is a workaround until helm will fully supports k8s v 1.16.
 
@@ -64,8 +67,8 @@ kubectl delete clusterrolebinding tiller
 ---
 **NOTE**
 
-We install tiller in the kube-system namespace and give it admin access to entire cluster.
+We install Tiller inside the kube-system namespace and give it admin access to the entire cluster.
 
-However, we can also deploy tiller in a specific namespace and restrict tiller to deploy resources only in that namespace.
+However, we can also deploy Tiller inside a specific namespace and restrict Tiller to deploy resources only in that namespace.
 
 See: https://helm.sh/docs/using_helm/#role-based-access-control
\ No newline at end of file
-- 
GitLab