Apply suggestions from code review

Co-authored-by: ldecarvalho-doc <[email protected]>

Author: SamyOubouaziz

pages/opensearch/how-to/create-opensearch-deployment.mdx

@@ -41,7 +41,7 @@ This page explains how to create an OpenSearch deployment using the Scaleway con
 
 10. Enter a name for your deployment, or keep the automatically generated one.
 
-11. Review the estimated cost for your cluster, then click **Create deployment** to  finish.
+11. Review the estimated cost for your cluster, then click **Create deployment** to finish.
 
 You are directed to the **Overview** tab of your deployment.
 

pages/opensearch/how-to/manage-opensearch-deployment.mdx

@@ -23,7 +23,7 @@ This page explains how to manage an OpenSearch deployment using the Scaleway con
 
 2. Click the name of the OpenSearch deployment you want to manage. Its **Overview** page displays.
 
-3. From here, you can:
+3. From the Overview, you can:
 
     - Access the dashboard of your deployment
     - View and manage the users of your deployment

pages/opensearch/how-to/manage-users-opensearch-deployment.mdx

@@ -1,5 +1,5 @@
 ---
-title: How to manages the users of a Cloud Essentials for OpenSearch deployment
+title: How to manage the users of a Cloud Essentials for OpenSearch deployment
 description: This page provides detailed information on how to manage the users of a Cloud Essentials for OpenSearch deployment using the Scaleway console.
 tags:
 dates:
@@ -18,7 +18,7 @@ This page explains how to manage the users of an OpenSearch deployment using the
 - [Created an OpenSearch deployment](/opensearch/how-to/create-opensearch-deployment/)
 
 <Message type="note">
-During private beta, only one user is allowed per deployment. Its credentials are defined during deployment creation.
+During private beta, only one user is allowed per deployment. Their credentials are defined during deployment creation.
 </Message>
 
 ## How to change a user's password

pages/opensearch/index.mdx

@@ -8,7 +8,7 @@ description: Dive into Scaleway Cloud Essentials for OpenSearch with our quickst
    productLogo="openSearch"
    description="Cloud Essentials for OpenSearch is designed to help users in their reporting and data analysis tasks for business intelligence."
    url="/opensearch/quickstart"
-   label=" Cloud Essentials for OpenSearch Quickstart"
+   label="Cloud Essentials for OpenSearch Quickstart"
 />
 
 ## Getting Started

pages/opensearch/quickstart.mdx

@@ -9,7 +9,7 @@ dates:
 
 import Requirements from '@macros/iam/requirements.mdx'
 
-Apache OpenSearch allows to research, analyze, and visualize all your unstructured data with an open-source search and analytics suite. It provides a fully-managed NoSQL database service to perform full-text searches and visualize results.
+Apache OpenSearch allows you to research, analyze, and visualize all your unstructured data with an open-source search and analytics suite. It provides a fully-managed NoSQL database service to perform full-text searches and visualize results.
 
 Cloud Essentials for OpenSearch is a managed solution to quickly deploy a robust database search engine that can be distributed across several nodes for enhanced performance and high availability.
 

pages/opensearch/reference-content/shared-vs-dedicated-resources.mdx

@@ -9,7 +9,7 @@ dates:
 
 When creating a Cloud Essentials for OpenSearch deployment, selecting the appropriate node type is crucial for optimizing performance and cost. Two types of CPU provisioning are available: **shared** and **dedicated** vCPUs.
 
-Understanding the difference between these two techniques is key to create a deployment adapted to your needs.
+Understanding the difference between these two techniques is the key to creating a deployment adapted to your needs.
 
 ## Comparison of shared and dedicated offers
 
@@ -31,7 +31,7 @@ Nodes with shared vCPU are cost-effective computational units in which CPU resou
 
 As a result, deployments share physical CPU time, and during peak demand from other resources on the same host machine, your workloads might temporarily slow down due to CPU contention (also known as "CPU steal").
 
-While physical CPU threads are shared between deployments, vCPUs are dedicated to each deployments, and no data can be shared or accessed between resources through this setup.
+While physical CPU threads are shared between deployments, vCPUs are dedicated to each deployment, and no data can be shared or accessed between resources through this setup.
 
 ### Typical use cases