AWS singlesignon documentation change
Summary
Minor grammatical updates including contraction replacements (e.g. 'you can't' → 'you cannot') and possessive form corrections
Security assessment
Changes are purely grammatical/typographical with no security context. No security implications identified in username reminders or password setup process modifications.
Diff
diff --git a/singlesignon/latest/userguide/quick-start-default-idc.md b/singlesignon/latest/userguide/quick-start-default-idc.md index 715ca5ebd..9ff9d81b4 100644 --- a//singlesignon/latest/userguide/quick-start-default-idc.md +++ b//singlesignon/latest/userguide/quick-start-default-idc.md @@ -7 +7 @@ -When you enable IAM Identity Center for the first time, it's automatically configured with an Identity Center directory as your default identity source, so you don't need to choose an identity source. If your organization uses another identity provider such as Microsoft Active Directory, Microsoft Entra ID, or Okta consider integrating that identity source with IAM Identity Center instead of using the default configuration. +When you enable IAM Identity Center for the first time, it is automatically configured with an Identity Center directory as your default identity source, so you do not need to choose an identity source. If your organization uses another identity provider such as Microsoft Active Directory, Microsoft Entra ID, or Okta consider integrating that identity source with IAM Identity Center instead of using the default configuration. @@ -51 +51 @@ The following prerequisites are needed to complete this tutorial: -When creating users, choose usernames that are easy to remember. Your users must remember the username to sign in to the AWS access portal and you can't change it later. +When creating users, choose usernames that are easy to remember. Your users must remember the username to sign in to the AWS access portal and you cannot change it later. @@ -145 +145 @@ In the next portion of this tutorial you'll test `Nikki's` access by signing in -Now that `Nikki Wolf` is a user in your organization, they can sign in and access the resources to which they're granted permission according to their permission set. To verify that the user is correctly configured, in this next step you'll use `Nikki's` credentials to sign in and set up their password. When you added the user `Nikki Wolf` in Step 1 you chose to have `Nikki` receive an email with password setup instructions. It's time to open that email and do the following: +Now that `Nikki Wolf` is a user in your organization, they can sign in and access the resources to which they are granted permission according to their permission set. To verify that the user is correctly configured, in this next step you'll use `Nikki's` credentials to sign in and set up their password. When you added the user `Nikki Wolf` in Step 1 you chose to have `Nikki` receive an email with password setup instructions. It's time to open that email and do the following: @@ -191 +191 @@ You can assign multiple permission sets to the same user. To follow the best pra -After your users [ accept their invitation](./howtoactivateaccount.html) to activate their account and they sign into the AWS access portal, the only items that appear in the portal are for the AWS accounts, roles, and applications to which they're assigned. +After your users [ accept their invitation](./howtoactivateaccount.html) to activate their account and they sign into the AWS access portal, the only items that appear in the portal are for the AWS accounts, roles, and applications to which they are assigned.