minor-fixes (#839)

hlxsites · Aug 15, 2024 · 6d9a425 · 6d9a425
1 parent 25dcb90
commit 6d9a425
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/...content-collections/administration/define-prisma-cloud-enterprise-settings.adoc b/...content-collections/administration/define-prisma-cloud-enterprise-settings.adoc
@@ -30,7 +30,7 @@ If you modify the timeout period, the new value is in effect for all administrat
 
 
 [#global-settings]
-=== Set Up Global Settings for Polices
+=== Set Up Global Settings for Policies
 
 Prisma Cloud policy settings apply to all policies. While some high severity policies such as *Critical* are enabled to provide the best security outcomes, by default, policies of medium or low severity are in a disabled state. When you select the checkbox to auto enable policies of a specific severity, you can either retroactively enable all policies that match the severity or only enable policies that are added to Prisma Cloud going forward.
 
@@ -128,7 +128,7 @@ Prisma Cloud generates Audit logs to help prepare your organization for regular
 
 [NOTE]
 ====
-To minimize "noise" and log flooding, Prisma Cloud does not forward "Successful login" type audit log messages to external integrations. All other audit log types can be sent to any supported external integration such as Webhook or SQS. For example, the following audit log message will not be forwarded. screen:['[email protected]'(with role 'System Admin':'System Admin') logged in via password]
+To minimize "noise" and log flooding, Prisma Cloud does not forward "Successful login" type audit log messages to external integrations. All other audit log types can be sent to any supported external integration such as Webhook or SQS. For example, the following audit log message will not be forwarded. '[email protected]'(with role 'System Admin':'System Admin') logged in via password.
 ====
 
 . Select *Settings > Enterprise Settings*.

diff --git a/...setup-sso-integration-on-prisma-cloud-for-microsoft-azure-active-directory.adoc b/...setup-sso-integration-on-prisma-cloud-for-microsoft-azure-active-directory.adoc
@@ -29,7 +29,7 @@ After you enable SSO, you must access Prisma Cloud from the Microsoft AAD portal
 
 .. Edit Basic SAML Configuration and enter previously copied Audience URI into *Identitifier (Entity ID)*.
 
-.. Depending on the location of your tenant, which is displayed in the login URL, copy and past the Prisma Cloud console URL into *Reply URL* (Assertion Consumer Service URL) field by replacing ‘app’ with ‘api’, and appending /saml at the end. For example: https://api2.prismacloud.io/saml for https://app2.prismacloud.io/[https://app2.prismacloud.io/] 
+.. Depending on the location of your tenant, which is displayed in the login URL, copy and paste the Prisma Cloud console URL into *Reply URL* (Assertion Consumer Service URL) field by replacing ‘app’ with ‘api’, and appending /saml at the end. For example: https://api2.prismacloud.io/saml for https://app2.prismacloud.io/[https://app2.prismacloud.io/] 
 
 .. Edit the User Attributes & Claims section. User Attributes captures information such as first and last name. Claims are key/value-pairs that relate to the user object, for instance a user's email address. Verify the following according to your environment. By default, claims should apply to any environment.
 +