From e5a98772508b7424db89dc6a6eb0d36cf094d06d Mon Sep 17 00:00:00 2001
From: Adar Nimrod <nimrod@shore.co.il>
Date: Thu, 24 Nov 2016 17:24:12 +0200
Subject: [PATCH] - Correct entry.

---
 content/aws_change_own_password.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/aws_change_own_password.rst b/content/aws_change_own_password.rst
index 610a139..40d2d6c 100644
--- a/content/aws_change_own_password.rst
+++ b/content/aws_change_own_password.rst
@@ -5,12 +5,12 @@ Self service AWS IAM policy
 :summary: AWS IAM policy to allow users to change their own password and manage
           their own keys.
 
-A common practice for me a new member joins the team or when someone forgets
-his/ her AWS account password is to change the account password myself, send the
-new password over a unsecure channel (email, Slack) but force the account to
-change the password on first login. Also, I prefer to have users manage their
-own keys to AWS themselves. But without the correct IAM policy users aren't able
-to perform either action. Here's an IAM to allow both:
+A common practice for me when a new member joins the team or when someone
+forgets his/ her AWS account password is to change the account password myself,
+send the new password over an unsecure channel (email, Slack) but force the
+account to change the password on first login. Also, I prefer to have users
+manage their own keys to AWS themselves. But without the correct IAM policy
+users aren't able to perform either action. Here's an IAM to allow both:
 
 .. code:: json
 
-- 
GitLab