Fixing formats and typos on several guides

Author: Y0Coss

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.de-de.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-asia.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-au.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-ca.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-gb.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-ie.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-sg.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.en-us.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.es-es.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.es-us.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.it-it.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.pl-pl.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/getting_started_roles_permission/guide.pt-pt.md

@@ -63,7 +63,7 @@ A user can use their usual Logs Data Platform account credentials on a different
 
 Role management can be automated by using the [OVHcloud API](https://api.ovh.com/console/#/dbaas/logs){.external}.
 
-Here are a few exemples of the role API calls you can use:
+Here are a few examples of the role API calls you can use:
 
 ### Listing available services
 

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.de-de.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-asia.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-au.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-ca.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-gb.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-ie.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-sg.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.en-us.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.es-es.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.es-us.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.it-it.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.pl-pl.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/manage_and_operate/observability/logs_data_platform/opensearch_index/guide.pt-pt.md

@@ -476,7 +476,7 @@ Logs Data Platform supports your custom templates. As for indices and aliases, t
 - The prefix of the indices involved in the template MUST start by **`<username>-i-`**, the "\*" character must be after this prefix
 - The alias attached to your template must follow the usual convention: **`<username>-a-<suffix>`**
 
-Here is an exemple of a template for a user **logs-ab-12345**:
+Here is an example of a template for a user **logs-ab-12345**:
 
 ```shell-session
 $ curl -u <username>:<password> -XPUT -H 'Content-Type: application/json' 'https://gra2.logs.ovh.com:9200/_template/template_for_logs-ab-12345_indices' -d '

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.de-de.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-asia.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-au.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-ca.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-gb.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-ie.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-sg.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)
 

Diff for: pages/public_cloud/ai_machine_learning/gi_08_s3_compliance/guide.en-us.md

@@ -136,7 +136,7 @@ Then, you need to retrieve the **access key** and **secret key** associated to t
 
 It is also important to ensure that this user has the appropriate permissions to access all the files in the bucket. Otherwise, you may encounter permission issues during the AI Solution deployment process.
 
-To grant access to your bucket for your user, click the `...`.{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
+To grant access to your bucket for your user, click the `...`{.action} button located next to your bucket name. Then, click the `Add a user to my container` option and select the same user you used during bucket creation.
 
 ![s3 bucket add user](images/s3-bucket-add-user.png)