Apply suggestions from code review

Co-authored-by: Marc Vincent Vista <marcvincent.vista@hcl.com>

Author: 2 people

docs/deployment/install/container/helm_deployment/preparation/optional_tasks/optional_install_new_search.md

@@ -203,7 +203,7 @@ configuration:
 
 ### Common fields mapping for fallback  
 
-Common field mappings are the default mappings for WCM, DAM, JCR, PORTAL and PEOPLE in the `documentObject`. You can find appropriate mappings for each field in the `documentObject`. Use an empty string if none of the mappings apply. For more information about `documentObject`, see [Indexed documents](../../../../../manage/container_configuration/configure_opensearch/architectural_overview.md#indexed-documents). 
+Common field mappings are the default mappings for WCM, DAM, JCR, PORTAL, and PEOPLE in the `documentObject` parameter. You can find appropriate mappings for each field in this parameter. Use an empty string if none of the mappings apply. For more information about the `documentObject` parameter, see [Indexed documents](../../../../../manage/container_configuration/configure_opensearch/architectural_overview.md#indexed-documents).
 
 ```yaml
 commonFieldMappings:
@@ -241,10 +241,10 @@ commonFieldMappings:
 
 Refer to the following list for more information about the fields:
 
-- `wcm`, `dam`, `jcr`, `portal` and `people` are the types of content source currently supported.  
+- `wcm`, `dam`, `jcr`, `portal`, and `people` are the types of content source currently supported.  
 - Names of common field mappings such as `title`, `description`, `type`, and `tags` cannot be changed.  
 - Apart from `title`, `description`, `type` and `tags`, additional common fields are not allowed.  
-- There are default values defined to map different content sources such as `wcm`, `dam`, `jcr` and `portal` to different common fields such as `title`, `description`, `type` and `tags`. You can change these default mapping values.
+- There are default values defined to map different content sources such as `wcm`, `dam`, `jcr`, and `portal` to different common fields such as `title`, `description`, `type` and `tags`. You can change these default mapping values.
 
 ### Persistent Volume size requests  
 

docs/extend_dx/integration/people_service/api/index.md

@@ -1,25 +1,25 @@
 # API documentation
 
-In this section, you will learn about the available APIs in People Service and how to interact with them. This section serves as a reference for developers and administrators looking to leverage People Service APIs to enhance their platforms. It includes details on the available APIs such as OpenAPI, Swagger Explorer and [Experience API documentation](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/) to help users understand and work with People Service APIs effectively.
+In this section, you will learn about the available APIs in People Service and how to interact with them. This section serves as a reference for developers and administrators looking to leverage People Service APIs to enhance their platforms. It includes details on the available APIs such as OpenAPI, Swagger Explorer, and [Experience API documentation](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/){target="_blank"} to help users understand and work with People Service APIs effectively.
 
 ## Working with APIs
 
 People Service APIs are designed to provide developers and administrators with the necessary tools to interact with the service and enhance their platforms. The APIs are RESTful and follow standard conventions, making them easy to work with and integrate into existing systems. The following sections provide an overview of the available APIs and how to interact with them effectively.
 
 People Service APIs are categorized into the following sections:
 
-- [Authentication](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/authentication): APIs related to user authentication and session management.
-- [Profiles](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/profiles): APIs related to managing user profiles, including creating, updating, and deleting profiles.
-- [Schema](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/schema): APIs related to managing profile attributes and schema definitions.
-- [Custom Fields](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/custom-fields): APIs related to managing custom fields for user profiles.
-- [Images and Media](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/images-and-media): APIs related to managing profile images and media content.
-- [Tags](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/tags): APIs related to managing tags for user profiles.
-- [Search](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search): APIs related to searching for user profiles based on specific criteria.
-- [Privacy](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/privacy): APIs related to managing user privacy settings and data protection.
-- [Federation and User Directories](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/federation-and-user-directories): APIs related to integrating with external user directories and federated identity providers.
-- [Utils](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/utils): Utility APIs for common tasks and operations.
-- [Probes](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/probes): Health check APIs for monitoring the service status and availability.
-- [Search Re-Index](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search-re-index): APIs related to retrying full or partial re-indexing for all or pending user profiles.
+- [Authentication](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/authentication){target="_blank"}: APIs related to user authentication and session management.
+- [Profiles](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/profiles){target="_blank"}: APIs related to managing user profiles, including creating, updating, and deleting profiles.
+- [Schema](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/schema){target="_blank"}: APIs related to managing profile attributes and schema definitions.
+- [Custom Fields](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/custom-fields){target="_blank"}: APIs related to managing custom fields for user profiles.
+- [Images and Media](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/images-and-media){target="_blank"}: APIs related to managing profile images and media content.
+- [Tags](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/tags){target="_blank"}: APIs related to managing tags for user profiles.
+- [Search](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search){target="_blank"}: APIs related to searching for user profiles based on specific criteria.
+- [Privacy](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/privacy){target="_blank"}: APIs related to managing user privacy settings and data protection.
+- [Federation and User Directories](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/federation-and-user-directories){target="_blank"}: APIs related to integrating with external user directories and federated identity providers.
+- [Utils](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/utils){target="_blank"}: Utility APIs for common tasks and operations.
+- [Probes](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/probes){target="_blank"}: Health check APIs for monitoring the service status and availability.
+- [Search Re-Index](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search-re-index){target="_blank"}: APIs related to retrying full or partial re-indexing for all or pending user profiles.
 
 ## OpenAPI and Swagger Explorer
 
@@ -37,4 +37,4 @@ Use the following URLs to access the Swagger Explorer for People Service APIs an
 
 Ensure to replace `<HOSTNAME>` with the correct value.
 
-For more information on the People Service API schema, refer to the [HCL Experience API Documentation](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/).
+For more information on the People Service API schema, refer to the [HCL Experience API Documentation](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/){target="_blank"}.

docs/extend_dx/integration/people_service/integration/people_service_search_v2_integration.md

@@ -26,25 +26,25 @@ People Service automatically indexes data when changes occur. However, it does n
 
 When creating and mutating users using the API or provisioning users through [User synchronization](../administration/user_provisioning/user_synchronization.md), the user data is indexed as needed as part of the creation or mutation process.
 
-- [People Profile API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/profiles)
+- [People Profile API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/profiles){target="_blank"}
 
     - To create new user profile and index, trigger the `POST` endpoint named `/dx/api/people/v1/people`.
     - To update existing user profile and indexing, trigger the `PUT` endpoint named `/dx/api/people/v1/people/{id}`.
     - To delete existing user profile and indexing, trigger the `DELETE` endpoint named `/dx/api/people/v1/people/{id}`.
 
-- [User Synchronization API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/federation-and-user-directories)
+- [User Synchronization API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/federation-and-user-directories){target="_blank"}
 
-    - To start user synchronization and indexing , trigger the `POST` endpoint named `/dx/api/people/v1/user-directories/sync`
+    - To start user synchronization and indexing, trigger the `POST` endpoint named `/dx/api/people/v1/user-directories/sync`.
 
 ### On-demand indexing
 
-If immediate processing is required, the People Service provides an indexing API that fully resynchronizes the index with the People Service user data.
+If immediate processing is required, People Service provides an indexing API that fully resynchronizes the index with the People Service user data.
 
-- [Search Indexing API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search-re-index)
+- [Search Indexing API endpoint](https://opensource.hcltechsw.com/experience-api-documentation/people-service-api/#tag/search-re-index){target="_blank"}
 
     - To get details of all pending and failed user index operations, trigger the `GET` endpoint named `/dx/api/people/v1/search/index/pending`.
-    - To retry pending and failed user index operations, trigger the `POST` endpoint named `/dx/api/people/v1/search/index/pending`
-    - To start full indexing for all users available in the people database., trigger the `POST` endpoint named `/dx/api/people/v1/search/index`
+    - To retry pending and failed user index operations, trigger the `POST` endpoint named `/dx/api/people/v1/search/index/pending`.
+    - To start full indexing for all users available in the people database, trigger the `POST` endpoint named `/dx/api/people/v1/search/index`.
 
 ### Upgrading to CF226 or later