Additional proofreading

Author: Y0Coss

pages/manage_and_operate/kms/kms-troubleshooting/guide.en-gb.md

@@ -6,7 +6,7 @@ updated: 2025-06-17
 
 ## Objective
 
-This guide aim to introduce logs generated by OVHcloud KMS and how they are managed from Logs Data Platform.
+This guide aims to introduce logs generated by OVHcloud KMS and how they are managed from Logs Data Platform.
 
 ## Requirements
 
@@ -17,44 +17,48 @@ This guide aim to introduce logs generated by OVHcloud KMS and how they are mana
 
 ### Description
 
-OVHcloud KMS has a native integration with [Logs Data Plateform](/links/manage-operate/ldp) for logs management.
+OVHcloud KMS has a native integration with [Logs Data Platform](/links/manage-operate/ldp) for logs management.
 
 ### Logs direct access
 
 KMS logs are available from each KMS `Logs`{.action} tab.
 
 ![Logs tab](images/kms-logs-tab.png){.thumbnail}
 
-This tab display in real time all KMS logs.
-A selector allow to switch display between the two types of logs:
+This tab displays all KMS logsin real time.
+A selector allows to switch display between the two types of logs:
 
 - REST API audit logs.
 - KMIP audit logs.
 
 ### Logs access through LDP
 
-From the `Logs`{.action} tab, it's possible to subscribe to a LDP data stream.
-One the subscribtion enable, all the logs will be pushed to [Logs Data Plateform](/links/manage-operate/ldp) to archive generated logs and perform advanced searches, create alerts and visualisations
+From the `Logs`{.action} tab, you can subscribe to an LDP data stream.
+Once the subscription is enabled, all the logs will be pushed to [Logs Data Platform](/links/manage-operate/ldp) to archive generated logs and perform advanced searches, create alerts and visualisations.
 
 ![LDP Subscription](images/kms-ldp-subscription.png){.thumbnail}
 
 For more information, please refer to our guide "[Quick start for Logs Data Platform](/pages/manage_and_operate/observability/logs_data_platform/getting_started_quick_start)".
 
 ### Available logs details
 
-KMS logs contains following information:
+KMS logs contain the following information:
 
 - REST API
 
-Logs are display with this format:
+Logs are displayed with this format:
 
 ```bash
 {{ http_method }} {{ http_path }} - {{ http_status }} - identity: {{ iam_identities }} - operation: {{ iam_operation }} on {{ res_urn }} - from {{ip}} with certificate {{cert_id}} - request id: {{ request_id }}
 ```
 
-As example: INFO | GET /v1/servicekey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - 200 - identity: urn:v1:eu:identity:group:xx1111-ovh/john.smith - operation: okms:apiovh:serviceKey/get on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxx/serviceKey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - from Manager/APIv2 - request id: EU.manager-5.684c3abe.3880620.2080cff16eaa5539bf92cxxxxxxxx
+**Example:**
 
-Elements that can be pushed to Logs Data Plateform:
+```console
+INFO | GET /v1/servicekey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - 200 - identity: urn:v1:eu:identity:group:xx1111-ovh/john.smith - operation: okms:apiovh:serviceKey/get on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxx/serviceKey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - from Manager/APIv2 - request id: EU.manager-5.684c3abe.3880620.2080cff16eaa5539bf92cxxxxxxxx
+```
+
+Elements that can be pushed to Logs Data Platform:
 
 |**Field**|**Description**|
 | :-: | :-: |
@@ -75,15 +79,19 @@ Elements that can be pushed to Logs Data Plateform:
 
 - KMIP
 
-Logs are display with this format:
+Logs are displayed with this format:
 
 ```bash
 {{ http_method }} {{ http_path }} - {{ http_status }} - identity: {{ iam_identities }} - operation: {{ iam_operation }} on {{ res_urn }} - from {{ip}} with certificate {{cert_id}} - request id: {{ request_id }}
 ```
 
-As example : INFO | GET on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxxx/kmip/ff55638c-3e86-4cb3-xxxx-xxxxxxxx - identity: urn:v1:eu:identity:account:xx1111-ovh - operation: okms:kmip:get - from XXX.XXX.XXX.XXX with certificate e7850a19-a5de-4527-xxxx-xxxxxxxxx - request id: OKMS.db61c455-abfa-4a66-xxxx-xxxxxxxxxxx"
+**Example:**
+
+```console
+INFO | GET on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxxx/kmip/ff55638c-3e86-4cb3-xxxx-xxxxxxxx - identity: urn:v1:eu:identity:account:xx1111-ovh - operation: okms:kmip:get - from XXX.XXX.XXX.XXX with certificate e7850a19-a5de-4527-xxxx-xxxxxxxxx - request id: OKMS.db61c455-abfa-4a66-xxxx-xxxxxxxxxxx
+```
 
-Elements that can be pushed to Logs Data Plateform:
+Elements that can be pushed to Logs Data Platform:
 
 |**Field**|**Description**|
 | :-: | :-: |

pages/manage_and_operate/kms/kms-troubleshooting/guide.fr-fr.md

@@ -17,7 +17,7 @@ L'objectif de ce guide est de présenter les logs générés par le KMS OVHcloud
 
 ### Description
 
-Le KMS OVHcloud dispose d'une intégration native avec [Logs Data Plateform](/links/manage-operate/ldp) pour la gestion des logs.
+Le KMS OVHcloud dispose d'une intégration native avec [Logs Data Platform](/links/manage-operate/ldp) pour la gestion des logs.
 
 ### Accès aux logs en direct
 
@@ -34,7 +34,7 @@ Le sélecteur permet de choisir le type de logs affichés :
 ### Accès aux logs via LDP
 
 Depuis l'onglet `Logs`{.action} il est possible de s'abonner à un flux LDP.
-Une fois l'abonnement actif, l'ensemble des logs seront transmis à [Logs Data Plateform](/links/manage-operate/ldp) pour retrouver l'historique des logs générés et la possiblité de faire des recherches plus avancées, créer des alertes et des visualisations.
+Une fois l'abonnement actif, l'ensemble des logs seront transmis à [Logs Data Platform](/links/manage-operate/ldp) pour retrouver l'historique des logs générés et la possiblité de faire des recherches plus avancées, créer des alertes et des visualisations.
 
 ![LDP Subscription](images/kms-ldp-subscription.png){.thumbnail}
 
@@ -52,9 +52,13 @@ Les logs sont sous le format suivant :
 {{ http_method }} {{ http_path }} - {{ http_status }} - identity: {{ iam_identities }} - operation: {{ iam_operation }} on {{ res_urn }} - from {{ip}} with certificate {{cert_id}} - request id: {{ request_id }}
 ```
 
-Par exemple : INFO | GET /v1/servicekey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - 200 - identity: urn:v1:eu:identity:group:xx1111-ovh/john.smith - operation: okms:apiovh:serviceKey/get on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxx/serviceKey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - from Manager/APIv2 - request id: EU.manager-5.684c3abe.3880620.2080cff16eaa5539bf92cxxxxxxxx
+**Exemple :**
 
-Les éléments pouvant être transmis à Logs Data Plateform sont :
+```console
+INFO | GET /v1/servicekey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - 200 - identity: urn:v1:eu:identity:group:xx1111-ovh/john.smith - operation: okms:apiovh:serviceKey/get on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxx/serviceKey/77f0a3f6-c2ef-4e76-xxxx-xxxxxxxxxxxx - from Manager/APIv2 - request id: EU.manager-5.684c3abe.3880620.2080cff16eaa5539bf92cxxxxxxxx
+```
+
+Les éléments pouvant être transmis à Logs Data Platform sont :
 
 |**Champ**|**Description**|
 | :-: | :-: |
@@ -81,9 +85,13 @@ Les logs sont sous le format suivant :
 {{ http_method }} {{ http_path }} - {{ http_status }} - identity: {{ iam_identities }} - operation: {{ iam_operation }} on {{ res_urn }} - from {{ip}} with certificate {{cert_id}} - request id: {{ request_id }}
 ```
 
-Par exemple : INFO | GET on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxxx/kmip/ff55638c-3e86-4cb3-xxxx-xxxxxxxx - identity: urn:v1:eu:identity:account:xx1111-ovh - operation: okms:kmip:get - from XXX.XXX.XXX.XXX with certificate e7850a19-a5de-4527-xxxx-xxxxxxxxx - request id: OKMS.db61c455-abfa-4a66-xxxx-xxxxxxxxxxx"
+**Exemple :**
+
+```console
+INFO | GET on urn:v1:eu:resource:okms:8d1c84cc-1128-4629-xxxx-xxxxxxxxxxx/kmip/ff55638c-3e86-4cb3-xxxx-xxxxxxxx - identity: urn:v1:eu:identity:account:xx1111-ovh - operation: okms:kmip:get - from XXX.XXX.XXX.XXX with certificate e7850a19-a5de-4527-xxxx-xxxxxxxxx - request id: OKMS.db61c455-abfa-4a66-xxxx-xxxxxxxxxxx"
+```
 
-Les éléments pouvant être transmis à Logs Data Plateform étant :
+Les éléments pouvant être transmis à Logs Data Platform étant :
 
 |**Champ**|**Description**|
 | :-: | :-: |