From 7732402b1b27f21c204b778af7de9cd886c4c104 Mon Sep 17 00:00:00 2001
From: "Roland Edwards, AOE GmbH" <39269273+raedwards@users.noreply.github.com>
Date: Wed, 16 May 2018 16:55:25 +0200
Subject: [PATCH] Update helm-terraform.md

---
 radar/2017-10-01/helm-terraform.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/radar/2017-10-01/helm-terraform.md b/radar/2017-10-01/helm-terraform.md
index 04bc9a4..9f71e3b 100644
--- a/radar/2017-10-01/helm-terraform.md
+++ b/radar/2017-10-01/helm-terraform.md
@@ -5,9 +5,9 @@ quadrant:   tools
 
 ---
 
-For our OM3 projects infrastructure we run multiple Kubernetes clusters, and to orchestrate the infrastructure provisioning decided quite fast to go with Terraform.
+For the infrastructure of our OM3 projects we run multiple Kubernetes clusters, and to orchestrate the infrastructure provisioning we quickly decided to go with Terraform.
 Terraform allows us to easily manage our infrastructure, from AWS EC2 instances to RabbitMQ message queues.
-Also the Kops installer for Kubernetes on AWS uses terraform as it's main building brick, and we can trigger Kops via Terraform.
+Also, the Kops installer for Kubernetes on AWS uses Terraform as its main building brick, and we can trigger Kops via Terraform.
 
 For managing deployments within Kubernetes we use Helm, which makes templating Kubernetes configuration files super easy (also known as Helm charts).