Skip to content

Commit 93b84b7

Browse files
Y0CossY0Coss
committed
Duplication of fixes + FR fixes
1 parent e0f6b16 commit 93b84b7

40 files changed

+78
-78
lines changed

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.de-de.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-asia.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-au.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-ca.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-ie.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-sg.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.en-us.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.es-es.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.es-us.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.fr-ca.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ A titre d'exemple, les produits suivants ont été validés à l'utilisation ave
3939

4040
Il est aussi possible d'utiliser les API KMIP directement.
4141

42-
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.
42+
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.
4343

4444
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 :
4545

@@ -51,7 +51,7 @@ Vous pouvez aussi utiliser notre SDK pour Go : <https://github.com/ovh/kmip-go>
5151
### Couverture KMIP
5252

5353
Le KMS OVHcloud couvre un sous-ensemble des versions 1.0 à 1.4 du standard KMIP.
54-
Le détail de la couverture est disponible ci-dessous
54+
Le détail de la couverture est disponible ci-dessous.
5555

5656
> **Légende:**
5757
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.fr-fr.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ A titre d'exemple, les produits suivants ont été validés à l'utilisation ave
3939

4040
Il est aussi possible d'utiliser les API KMIP directement.
4141

42-
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.
42+
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.
4343

4444
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 :
4545

@@ -51,7 +51,7 @@ Vous pouvez aussi utiliser notre SDK pour Go : <https://github.com/ovh/kmip-go>
5151
### Couverture KMIP
5252

5353
Le KMS OVHcloud couvre un sous-ensemble des versions 1.0 à 1.4 du standard KMIP.
54-
Le détail de la couverture est disponible ci-dessous
54+
Le détail de la couverture est disponible ci-dessous.
5555

5656
> **Légende:**
5757
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.it-it.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.pl-pl.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-kmip/guide.pt-pt.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ As an example, the following products were validated with the OVHcloud KMS :
4040

4141
It's also possible to use the KMIP API directly.
4242

43-
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.
43+
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.
4444

45-
Then it's possible to exchange KMIP messages such as defined in the standard. Depending n the technology stack, we recommend the following libraries:
45+
Then it's possible to exchange KMIP messages such as defined in the standard. Depending on the technology stack, we recommend the following libraries:
4646

4747
- PyKMIP for python: <https://github.com/OpenKMIP/PyKMIP>.
4848
- 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>
5353

5454
The OVHcloud KMS covers a part of 1.0 to 1.4 versions of the KMIP standard.
5555

56-
Details of the coverage is available here:
56+
Details of the coverage are available here:
5757

5858
> **Legend:**
5959
>

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.de-de.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-asia.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-au.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-ca.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-ie.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-sg.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.en-us.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

Diff for: ‎pages/manage_and_operate/kms/kms-usage/guide.es-es.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -277,7 +277,7 @@ The **context** field must have the same value as the one given during encryptio
277277
#### Encryption with a Data Key (DK)
278278

279279
For better performance, you can generate a Data Key (DK) from a Symmetric Key (AES) to use from your application.
280-
The AES key use must have been generated with the "wrapKey, unwrapKey" operations
280+
The AES key used must have been generated with the "wrapKey, unwrapKey" operations.
281281

282282
![Encryption with DK](images/Datakey_encrypt.png){.thumbnail}
283283

0 commit comments

Comments
 (0)