diff --git a/ee/ucp/admin/configure/integrate-saml.md b/ee/ucp/admin/configure/integrate-saml.md
index 854ce3f852..6dec635620 100644
--- a/ee/ucp/admin/configure/integrate-saml.md
+++ b/ee/ucp/admin/configure/integrate-saml.md
@@ -25,47 +25,41 @@ is expected:
1. `Subject` includes a `NameID` that is identified as the UCP username.
In `AuthnRequest`, `NameIDFormat` is set to `urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified`.
This allows maximum compatibility for various Identity Providers.
- ```xml
+```xml
ry4nz
- ```
+```
2. Optional `Attribute` named `fullname` is mapped to the 'Full name' field
in the UCP account.
Note: UCP uses the value of the first occurrence of an `Attribute` with `Name="fullname"` as the 'Full name'.
- ```xml
-
- user.displayName
-
-
- ```
+```xml
+
+ user.displayName
+
+
+```
3. Optional `Attribute` named `member-of` is linked to the UCP team.
Values are set in the UCP team UI.
Note: UCP uses all `AttributeStatements` and `Attributes` in the `Assertion` with `Name="member-of"`.
- ```xml
-
- groupName
-
-
- ```
+```xml
+
+ groupName
+
+
+```
4. Optional `Attribute` named `is-admin` determines if the user is an administrator. The content in the `AttributeValue` is ignored.
- ```xml
-
- value_doe_not_matter
-
-
- ```
+```xml
+
+ value_does_not_matter
+
+
+```
#### Okta Configuration
Configuring with Okta is straightforward, as shown in the following examples:
