From 2cda0936bc8332c4e5d30ea330408369660d0e15 Mon Sep 17 00:00:00 2001
From: Nsikan <20339399+noce2@users.noreply.github.com>
Date: Mon, 14 Mar 2022 10:29:19 +0000
Subject: [PATCH] Update website/docs/language/settings/backends/s3.mdx

Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>
---
 website/docs/language/settings/backends/s3.mdx | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/website/docs/language/settings/backends/s3.mdx b/website/docs/language/settings/backends/s3.mdx
index a36ea51c9d..c0d050414c 100644
--- a/website/docs/language/settings/backends/s3.mdx
+++ b/website/docs/language/settings/backends/s3.mdx
@@ -415,9 +415,8 @@ table used for locking. During a `terraform plan`, when the state lock is put in
 Terraform stores the full statefile as a document with its partition key set 
 as the s3 object key. After the state lock is released, a digest of the updated
 statefile is placed in DynamoDB with a key similar to that of the original 
-statefile but suffixed with `-md5`. A simple IAM policy that would allow the 
-role assumed for backend operations to perform the aforementioned operations is 
-shown below:
+statefile but suffixed with `-md5`. The example below shows an IAM policy that would allow the 
+role assumed for backend operations to perform these operations. 
 
 ```json
 {