Skip to content

Commit 1004266

Browse files
Y0CossY0Coss
authored
Merge pull request #7659 from ovh/SR-KMS-fixes
[EN]-KMS-grammatical fixes
2 parents 3dcbe26 + 93b84b7 commit 1004266

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+84
-84
lines changed

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

‎pages/manage_and_operate/kms/kms-kmip/guide.en-gb.md

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

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

Lines changed: 3 additions & 3 deletions
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
>

0 commit comments

Comments
 (0)