Skip to content

Commit 9281a6c

Browse files
Y0CossY0Coss
committed
Proofreading and code snippets format fixes
1 parent feb4313 commit 9281a6c

File tree

15 files changed

+135
-135
lines changed

15 files changed

+135
-135
lines changed

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.de-de.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -247,9 +247,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
247247

248248
The "OVH provider" needs to be configured with a set of credentials:
249249

250-
* an `application_key`
251-
* an `application_secret`
252-
* a `consumer_key`
250+
- an `application_key`
251+
- an `application_secret`
252+
- a `consumer_key`
253253

254254
**Why?**
255255

@@ -319,11 +319,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
319319

320320
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
321321

322-
* `ovh-eu` for OVHcloud Europe API
323-
* `ovh-us` for OVHcloud US API
324-
* `ovh-ca` for OVHcloud North-America API
322+
- `ovh-eu` for OVHcloud Europe API
323+
- `ovh-us` for OVHcloud US API
324+
- `ovh-ca` for OVHcloud North-America API
325325

326-
Then, create a `variables.tf` file with service_name:
326+
Then, create a `variables.tf` file with the service_name:
327327

328328
```bash
329329
variable service_name {
@@ -374,7 +374,7 @@ Initializing provider plugins...
374374
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
375375

376376
Partner and community providers are signed by their developers.
377-
If you'd like to know more about provider signing, you can read about it here:
377+
If you’d like to know more about provider signing, you can read about it here:
378378
https://www.terraform.io/docs/cli/plugins/signing.html
379379

380380
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -468,7 +468,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
468468
469469
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
470470
471-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
471+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
472472
```
473473
474474
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-asia.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-au.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-ca.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-gb.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-ie.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-sg.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

‎pages/platform/kubernetes-k8s/customizing-kubeproxy/guide.en-us.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -245,9 +245,9 @@ Since the version 0.28.1+ of our [OVH Terraform provider](https://registry.terra
245245

246246
The "OVH provider" needs to be configured with a set of credentials:
247247

248-
* an `application_key`
249-
* an `application_secret`
250-
* a `consumer_key`
248+
- an `application_key`
249+
- an `application_secret`
250+
- a `consumer_key`
251251

252252
**Why?**
253253

@@ -317,11 +317,11 @@ This later method (or a similar alternative) is recommended to avoid storing sec
317317

318318
Here, we defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
319319

320-
* `ovh-eu` for OVHcloud Europe API
321-
* `ovh-us` for OVHcloud US API
322-
* `ovh-ca` for OVHcloud North-America API
320+
- `ovh-eu` for OVHcloud Europe API
321+
- `ovh-us` for OVHcloud US API
322+
- `ovh-ca` for OVHcloud North-America API
323323

324-
Then, create a `variables.tf` file with service_name:
324+
Then, create a `variables.tf` file with the service_name:
325325

326326
```bash
327327
variable service_name {
@@ -372,7 +372,7 @@ Initializing provider plugins...
372372
- Installed ovh/ovh v0.28.1 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)
373373

374374
Partner and community providers are signed by their developers.
375-
If you'd like to know more about provider signing, you can read about it here:
375+
If you’d like to know more about provider signing, you can read about it here:
376376
https://www.terraform.io/docs/cli/plugins/signing.html
377377

378378
Terraform has created a lock file .terraform.lock.hcl to record the provider
@@ -466,7 +466,7 @@ Plan: 1 to add, 0 to change, 0 to destroy.
466466
467467
───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
468468
469-
Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.
469+
Note: You didn’t use the -out option to save this plan, so Terraform can’t guarantee to take exactly these actions if you run "terraform apply" now.
470470
```
471471
472472
Thanks to the `plan` command, we can check what Terraform wants to create, modify or remove.

0 commit comments

Comments
 (0)