update

Definitely-not-AWS-Workshops · Sep 27, 2024 · 3d5d08f · 3d5d08f
1 parent 363437c
commit 3d5d08f
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 16 deletions.
diff --git a/content/17-Test-AWS-RDS-Failover/_index.md b/content/17-Test-AWS-RDS-Failover/_index.md
@@ -14,7 +14,7 @@ Let’s put your database servers to the test by initiating a reboot to simulate
 
 - Click **Databases**.
 - Select **awsome-books** database.
-- Expand **Actions**.
+- Expand the **Actions** dropdown.
 - Click **Reboot**.
 
 ![0001](/images/17/0001.svg?featherlight=false&width=100pc)
@@ -26,7 +26,7 @@ Let’s put your database servers to the test by initiating a reboot to simulate
 
 ![0002](/images/17/0002.svg?featherlight=false&width=100pc)
 
-You might notice that your database server is in **Rebooting** status. Its current AZ should be **us-east-1a**.
+You might notice that your primary database server is in **Rebooting** status. Its current AZ should be **us-east-1a**.
 
 ![0003](/images/17/0003.svg?featherlight=false&width=100pc)
 

diff --git a/content/19-Clean-Up/_index.md b/content/19-Clean-Up/_index.md
@@ -171,67 +171,67 @@ Congratulations on completing the workshop and smoothly running your pipelines a
 
 **28.** Go to [AWS Chatbot console](https://console.aws.amazon.com/chatbot).
 
-**30.** In the left sidebar,
+**29.** In the left sidebar,
 
 - Select **Configured clients**.
 - Select **Slack - fcj**.
 
 ![00022](/images/19/00022.svg?featherlight=false&width=100pc)
 
-**31.** In the Slack workspace details page,
+**30.** In the Slack workspace details page,
 
 - Select **fcj-slack** channel.
 - Click **Delete**.
 
 ![00023](/images/19/00023.svg?featherlight=false&width=100pc)
 
-**32.** Click **Delete**.
+**31.** Click **Delete**.
 
 ![00024](/images/19/00024.svg?featherlight=false&width=100pc)
 
-**33.** Click **Remove workspace configuration**.
+**32.** Click **Remove workspace configuration**.
 
 ![00025](/images/19/00025.svg?featherlight=false&width=100pc)
 
-**34.**
+**33.**
 
 - Enter your **Workspace ID**.
 - Click **Remove workspace configuration**.
 
 ![00026](/images/19/00026.svg?featherlight=false&width=100pc)
 
-**35.** Go to [AWS IAM console](https://console.aws.amazon.com/iam).
+**34.** Go to [AWS IAM console](https://console.aws.amazon.com/iam).
 
-**36.** In the left sidebar,
+**35.** In the left sidebar,
 
 - Select **Roles**.
 - Select **chatbot-role**, **ecsCodeDeployRole**, **ecsTaskExecutionRole**, **ecsTaskRole**, and **gha-role** roles.
 - Click **Delete**.
 
 ![00027](/images/19/00027.svg?featherlight=false&width=100pc)
 
-**37.**
+**36.**
 
 - Enter `delete`.
 - Click **Delete**.
 
 ![00028](/images/19/00028.svg?featherlight=false&width=100pc)
 
-**38.** In the left sidebar,
+**37.** In the left sidebar,
 
 - Select **Policies**.
 - Filter with value `ecsTaskRolePolicy`.
-- For **Filter by Type**, select **Customer managed** .
-- For **Policy name**, select **ecsTaskRolePolicy**.
+- For **Filter by Type**, select **Customer managed**.
+-  Select **ecsTaskRolePolicy** policy.
 - Click **Delete**.
 
 ![00029](/images/19/00029.svg?featherlight=false&width=100pc)
 
-**39.**
+**38.**
 
 - Enter `ecsTaskRolePolicy`.
 - Click **Delete**.
 
 ![00030](/images/19/00030.svg?featherlight=false&width=100pc)
 
-**40.** Repeat the step **38** and **39** but with `gha-policy` value instead.
+**39.** Repeat the step **37** and **38** but with `gha-policy` value instead.
diff --git a/content/20-Further-Improvements/_index.md b/content/20-Further-Improvements/_index.md
@@ -10,7 +10,7 @@ By setting up AWS API Gateway with the REST APIs type, you now have access to ad
 
 - Your AWS API Gateway is now accessible to anyone with internet access. To enhance security, consider integrating [AWS Cognito](https://docs.aws.amazon.com/cognito/) with a user pool as an authorizer.
 
-- Your AWS API Gateway is using the default endpoint. For enhanced security and branding, consider setting up a custom domain with SSL/TLS encryption through [AWS Route 53](https://docs.aws.amazon.com/route53/) and [AWS Certificate Manager](https://docs.aws.amazon.com/acm//).
+- Your AWS API Gateway is using the default endpoint. For enhanced security and branding, consider setting up a custom domain with SSL/TLS encryption through [AWS Route 53](https://docs.aws.amazon.com/route53/) and [AWS Certificate Manager](https://docs.aws.amazon.com/acm/).
 
 <!-- Your AWS architecture would then look like this: