Skip to content

Commit 44c1500

Browse files
author
tcpdumpfbacke
committed
FIxes
1 parent a013e47 commit 44c1500

File tree

16 files changed

+18
-18
lines changed

16 files changed

+18
-18
lines changed

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.de-de.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-asia.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-au.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-ca.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-gb.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-ie.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-sg.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.en-us.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.es-es.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.es-us.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.fr-ca.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.fr-fr.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.it-it.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.pl-pl.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/public_cloud/containers_orchestration/managed_private_registry/deploy-chart-from-registry-in-kubernetes/guide.pt-pt.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This tutorial presupposes that you already have a working OVHcloud Managed Kuber
1818

1919
You also need to have a working OVHcloud Managed Private Registry and have followed the guide on [managing Helm charts in the OVHcloud Managed Private Registry](/pages/public_cloud/containers_orchestration/managed_private_registry/using-helm-charts).
2020

21-
After following the previous guide, you should have at least one Wordpress Helm chart in your Managed Private Registry:
21+
After following the previous guide, you should have at least one WordPress Helm chart in your Managed Private Registry:
2222

2323
![Helm charts in OVHcloud Managed Private Registry](images/helm-chart-in-ovh-private-registry.png)
2424

Diff for: pages/web_cloud/email_and_collaborative_solutions/microsoft_exchange/exchange_adding_domain/guide.de-de.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Der Assistent zeigt nun Informationen zur Konfiguration der gewünschten Nutzung
7070
>![Domain hinzufügen](images/add_domain_exchange_authoritative.png){.thumbnail}
7171
>
7272
73-
> [!warnung]
73+
> [!warning]
7474
>
7575
> Wenn Sie beim Hinzufügen Ihres Domainnamens zu Ihrer E-Mail-Plattform die Meldung „**autoritative Domain erkannt**“ erhalten, bedeutet dies, dass dieser Domainname auf einer anderen E-Mail-Plattform im **autoritativen** Modus deklariert ist. Sie müssen es auf beiden Plattformen in den **nicht autorisierenden** Modus schalten, damit sie koexistieren können.
7676
@@ -123,7 +123,7 @@ Wenn Sie eine Domain aus Ihrem Exchange oder E-Mail Pro Dienst entfernen möchte
123123
>
124124
> Bevor Sie E-Mail-Accounts löschen, überprüfen Sie, dass diese nicht verwendet werden. Eine Sicherung dieser Accounts kann notwendig sein. Wenn nötig lesen Sie die Anleitung ["Ihre E-Mail-Adresse manuell migrieren"](/pages/web_cloud/email_and_collaborative_solutions/migrating/manual_email_migration), in der beschrieben wird, wie Sie Daten eines Accounts über Ihr Kundencenter oder ein E-Mail-Programm exportieren.
125125
126-
Gehen Sie zum Tab `Assoziierte Domains`{.action} Ihres Dienstes. In der Tabelle gibt die `Spalte` Accounts die Anzahl der Accounts an, die Ihren Domainnamen zugewiesen sind.
126+
Gehen Sie zum Tab `Assoziierte Domains`{.action} Ihres Dienstes. In der Tabelle gibt die Spalte `E-Mail Accounts` die Anzahl der Accounts an, die Ihren Domainnamen zugewiesen sind.
127127

128128
![emailpro](images/add_domain_exchange_step6.png){.thumbnail}
129129

@@ -134,7 +134,7 @@ Wenn E-Mail-Accounts die Domain verwenden, die Sie abtrennen möchten, haben Sie
134134
Im Bearbeitungsfenster können Sie die mit dem Account verbundene Domain über das Drop-down-Menü ändern.
135135
![emailpro](images/add_domain_exchange_step9.png){.thumbnail}
136136

137-
- **Konten Ihres Dienstes löschen**: Gehen Sie in den Tab `E-Mail Accounts`{.action}. Klicken Sie rechts neben dem zu löschenden Account auf den Button `...`{.action} und dann `Diesen Account zurücksetzen`{.action} oder `Zurücksetzen`{.action}.
137+
- **Accounts Ihres Dienstes löschen**: Gehen Sie in den Tab `E-Mail Accounts`{.action}. Klicken Sie rechts neben dem zu löschenden Account auf den Button `...`{.action} und dann `Diesen Account zurücksetzen`{.action} oder `Zurücksetzen`{.action}.
138138
![emailpro](images/add_domain_exchange_step7.png){.thumbnail}
139139

140140
Sobald die Accounts einer anderen Domain zugewiesen wurden oder die Zurücksetzung abgeschlossen ist, kann die Domain gelöscht werden.

0 commit comments

Comments
 (0)