From c4210b570cde6b92720234d9d49e03fef12aefa2 Mon Sep 17 00:00:00 2001
From: Nico Esteves <git@hamstah.com>
Date: Tue, 26 Jun 2018 13:31:56 +0200
Subject: [PATCH] Updated iam-auth-proxy README

---
 iam/auth-proxy/README.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/iam/auth-proxy/README.md b/iam/auth-proxy/README.md
index 0492b8f..f035dfb 100644
--- a/iam/auth-proxy/README.md
+++ b/iam/auth-proxy/README.md
@@ -31,7 +31,7 @@ You want to use IAM as your identity provider for a service as you already use I
 
 ## Comparison to other AWS Solutions
 
-* Cognito: Cognito let's you use give IAM access to Cognito users but uses its own pool of users
+* Cognito: Cognito lets you use give IAM access to Cognito users but uses its own pool of users, it's the opposite
 * AWS SSO: Is not globally available
 
 # Authentication Flow
@@ -176,16 +176,16 @@ You need to add a trust relationship between the KMS key in the central account
    }
   ```
 * User policy
-```
-{
-   "Sid": "UserCanEncrypt",
-   "Effect": "Allow",
-   "Action": [
-     "kms:Encrypt"
-   ],
-   "Resource": "<key arn>"
- }
-```
+  ```
+  {
+     "Sid": "UserCanEncrypt",
+     "Effect": "Allow",
+     "Action": [
+       "kms:Encrypt"
+     ],
+     "Resource": "<key arn>"
+   }
+  ```
 
 ## STS