Add review suggestions

Author: HasiniSama

en/identity-server/6.1.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -332,7 +332,7 @@ pooling for LDAPS connections at the time of starting your server:
 
 When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
 
-To optimize performance and prevent thread blocking issues, configure the max users returned per role:
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
 
 ```toml
 [pagination]
@@ -343,7 +343,7 @@ max_users_list_per_role = <NUMBER_OF_USERS>
 
 - **Default value**: 1000 users per role (when not configured)
 - **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
-- **Scope**: Applies to all roles, including the built-in "everyone" role
+- **Scope**: Applies to all roles, including the built-in `everyone` role
 - **Database dependency**: Adjust this value based on your database performance capabilities
 
 !!! tip

en/identity-server/7.0.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -241,7 +241,7 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
 
 When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
 
-To optimize performance and prevent thread blocking issues, configure the max users returned per role:
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
 
 ```toml
 [pagination]
@@ -252,7 +252,7 @@ max_users_list_per_role = <NUMBER_OF_USERS>
 
 - **Default value**: 1000 users per role (when not configured)
 - **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
-- **Scope**: Applies to all roles, including the built-in "everyone" role
+- **Scope**: Applies to all roles, including the built-in `everyone` role
 - **Database dependency**: Adjust this value based on your database performance capabilities
 
 !!! tip

en/identity-server/7.1.0/docs/deploy/performance/performance-tuning-recommendations.md

@@ -241,7 +241,7 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
 
 When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
 
-To optimize performance and prevent thread blocking issues, configure the max users returned per role:
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
 
 ```toml
 [pagination]
@@ -252,7 +252,7 @@ max_users_list_per_role = <NUMBER_OF_USERS>
 
 - **Default value**: 1000 users per role (when not configured)
 - **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
-- **Scope**: Applies to all roles, including the built-in "everyone" role
+- **Scope**: Applies to all roles, including the built-in `everyone` role
 - **Database dependency**: Adjust this value based on your database performance capabilities
 
 !!! tip

en/identity-server/next/docs/deploy/performance/performance-tuning-recommendations.md

@@ -241,7 +241,7 @@ Connection pooling does not apply to LDAPS connections (SSL-enabled LDAP connect
 
 When retrieving roles from the SCIM2/Roles endpoint, WSO2 Identity Server returns all users assigned to each role by default. For roles containing many users, this can lead to performance bottlenecks and block processing threads.
 
-To optimize performance and prevent thread blocking issues, configure the max users returned per role:
+To optimize performance and prevent thread blocking issues, configure the max users returned per role.
 
 ```toml
 [pagination]
@@ -252,7 +252,7 @@ max_users_list_per_role = <NUMBER_OF_USERS>
 
 - **Default value**: 1000 users per role (when not configured)
 - **Lowest value**: 1000 users (values below 1000 automatically default to 1000)
-- **Scope**: Applies to all roles, including the built-in "everyone" role
+- **Scope**: Applies to all roles, including the built-in `everyone` role
 - **Database dependency**: Adjust this value based on your database performance capabilities
 
 !!! tip

en/includes/guides/organization-management/try-a-b2b-use-case-pet-care.md

@@ -541,7 +541,7 @@ Follow the steps below to see how organization login works for a user in the **H
 
 3. Click **Sign In with SSO** to specify the organization to which you are signing in.
 
-{% if product_name != "Asgardeo" and (product_name == "WSO2 Identity Server" and is_version > "7.1.0") %}
+{% if product_name == "WSO2 Identity Server" and is_version > "7.1.0" %}
 4. Enter the **Organization Handle** of the organization and click **Submit**.
 {% else %}
 4. Enter **Happy Tails** as the organization name and click **Submit**.