From d03525acf50f5e82d2b9d0eb7aa80f418493c8c1 Mon Sep 17 00:00:00 2001
From: staleycyn <45440075+staleycyn@users.noreply.github.com>
Date: Tue, 13 Jun 2023 05:57:05 -0700
Subject: [PATCH] Update 02 - Administer Governance and Compliance.md

---
 ... - Administer Governance and Compliance.md | 28 ++++---------------
 1 file changed, 5 insertions(+), 23 deletions(-)

diff --git a/Instructions/Demos/02 - Administer Governance and Compliance.md b/Instructions/Demos/02 - Administer Governance and Compliance.md
index 51492648..2443a881 100644
--- a/Instructions/Demos/02 - Administer Governance and Compliance.md	
+++ b/Instructions/Demos/02 - Administer Governance and Compliance.md	
@@ -69,23 +69,7 @@ In this demonstration, we will work with Azure policies.
 
 3.  Review any remediation tasks that are listed.
 
-**Remove your policy and initiative (optional)**
-
-1.  Return to the Azure Policy service page.
-
-2.  Select **Assignments**.
-
-3.  Select your **Allowed locations** policy.
-
-4.  Click **Delete assignment**.
-
-5.  Return to the Azure Policy service page.
-
-6.  Select **Initiatives**.
-
-7.  Select your new initiative.
-
-8.  Click **Delete initiative**.
+4. As you have time, remove the policy and the initiative. 
 
 ## Configure Role-Based Access Control
 
@@ -117,14 +101,12 @@ In this demonstration, we will learn about role assignments.
 
 **Add a role assignment**
 
-1.  Create a user.
+1.  Create a user or select an existing user.
 
-1.  Select **Add role assignment** and pick a role. For exmaple, *owner*.
+1.  Select **Add role assignment** and select a role. For exmaple, *owner*.
 
 1.  Select **Check access**.
 
-1.  Select the user.
+1.  Review the user permissions.
 
-1.  Notice the user is part of the **Managers** group and is an **Owner**.
-
-1.  Notice that you can **Deny assignments**.
+1.  Note that you can **Deny assignments**.