From 5be2a146efd88bbb53f3ed9c35077a967825023e Mon Sep 17 00:00:00 2001
From: gurkenhabicht <info@intheopen.org>
Date: Thu, 8 Feb 2024 23:10:46 +0100
Subject: [PATCH] typos

---
 Enumeration/AWS.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Enumeration/AWS.md b/Enumeration/AWS.md
index 7cb100f..99ae850 100644
--- a/Enumeration/AWS.md
+++ b/Enumeration/AWS.md
@@ -56,7 +56,7 @@ If the ACL is set to
 Permissions are granted directly through user accounts or indirectly through
 roles the user has joined.
 
-<img src="./include/iam-intro-users-and-groups.diagram.png" alt="Policy evaluation" width="100%" height="auto">
+<img src="./include/iam-intro-users-and-groups.diagram.png" alt="Policy evaluation" width="auto" height="auto">
 
 Gaining access to important roles like maintenance opens the door to higher permissions.
 An always unique AWS Account ID has a length of 12 digits.
@@ -91,7 +91,7 @@ Policy evaluation can be found in the [AWS docs](https://docs.aws.amazon.com/IAM
 The following graph is taken from the documentation, it shows the evaluation
 logic inside an account
 
-<img src="./include/PolicyEvaluationHorizontal111621.png" alt="Policy evaluation" width="100%" height="auto">
+<img src="./include/PolicyEvaluationHorizontal111621.png" alt="Policy evaluation" width="80%" height="auto">
 
 Policies like `assume-role` and `switch-role` can lead to the gain of roles
 with higher permissions