Duplication of fixes + FR fixes

Author: Y0Coss

pages/manage_and_operate/kms/kms-kmip/guide.de-de.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-asia.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-au.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-ca.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-ie.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-sg.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.en-us.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.es-es.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.es-us.md

@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
 
 It's also possible to use the KMIP API directly.
 
-Authentication on this procotol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
+Authentication on this protocol is done with a client certificate, in the same way as for the REST API. It needs to open a TLS channel with a valid access certificate.
 
-Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
+Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
 
 - PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
 - Libkmip for C: <https://github.com/OpenKMIP/libkmip>.
@@ -53,7 +53,7 @@ You can use as well our SDK for Go: <https://github.com/ovh/kmip-go>
 
 The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
 
-Details of the coverage is available here:
+Details of the coverage are available here:
 
 > **Legend:**
 >

pages/manage_and_operate/kms/kms-kmip/guide.fr-ca.md

@@ -39,7 +39,7 @@ A titre d'exemple, les produits suivants ont été validés à l'utilisation ave
 
 Il est aussi possible d'utiliser les API KMIP directement.
 
-L'authentification sur ce protocole s’effectue avec un certificat client, de la même façon qu’avec l’API REST.  Il faut donc ouvrir un flux TLS tout en fournissant un certificat d'accès valide.
+L'authentification sur ce protocole s’effectue avec un certificat client, de la même façon qu’avec l’API REST. Il faut donc ouvrir un flux TLS tout en fournissant un certificat d'accès valide.
 
 A partir de là, il est possible d'échanger des messages KMIP tels que définis dans le standard. Selon votre stack technologique, nous vous recommandons des librairies telles que :
 
@@ -51,7 +51,7 @@ Vous pouvez aussi utiliser notre SDK pour Go : <https://github.com/ovh/kmip-go>
 ### Couverture KMIP
 
 Le KMS OVHcloud couvre un sous-ensemble des versions 1.0 à 1.4 du standard KMIP.
-Le détail de la couverture est disponible ci-dessous
+Le détail de la couverture est disponible ci-dessous.
 
 > **Légende:**
 >