diff --git a/docs/cloud-native-security/kspm-get-started.asciidoc b/docs/cloud-native-security/kspm-get-started.asciidoc
index 9ef78eb193..7f05da0d61 100644
--- a/docs/cloud-native-security/kspm-get-started.asciidoc
+++ b/docs/cloud-native-security/kspm-get-started.asciidoc
@@ -128,14 +128,14 @@ If you are using the AWS visual editor to create and modify your IAM Policies, y
 
 Follow AWS's https://aws.github.io/aws-eks-best-practices/security/docs/iam/#iam-roles-for-service-accounts-irsa[EKS Best Practices] documentation to use the https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html[IAM Role to Kubernetes Service-Account] (IRSA) feature to get temporary credentials and scoped permissions.
 
-During setup, do not fill in any option in the "Setup Access" section. Instead click *Save and continue*.
+IMPORTANT: During setup, do not fill in any option in the "Setup Access" section. Click *Save and continue*.
 
 [discrete]
 [[kspm-use-instance-role]]
 ==== Option 2 - Use default instance role
 Follow AWS's https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html[IAM roles for Amazon EC2] documentation to create an IAM role using the IAM console, which automatically generates an instance profile.
 
-During setup, do not fill in any option in the "Setup Access" section. Click *Save and continue*.
+IMPORTANT: During setup, do not fill in any option in the "Setup Access" section. Click *Save and continue*.
 
 [discrete]
 [[kspm-use-keys-directly]]