Skip to content

Commit e0ea30d

Browse files
dstagnoldstagnol
authored andcommitted
changing VCD terms in every guides
1 parent 86f3dd3 commit e0ea30d

File tree

221 files changed

+3763
-3763
lines changed

Some content is hidden

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

221 files changed

+3763
-3763
lines changed

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.de-de.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-asia.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-au.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-ca.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-gb.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-ie.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-sg.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.en-us.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.es-es.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps/guide.es-us.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Enter your credentials and click `LOG IN`{.action}.
5353
> [!warning]
5454
> To authenticate on the NSX interface, you need to use a vSphere account with NSX rights. Ensure that the Dedicated Cloud name (FQDN, in the form `pcc-x-x-x-x.ovh.xx`) is selected in the login form.
5555
>
56-
> If you are not using the NSX interface, but rather the API or another external tool (such as VMware Cloud Director, VCD), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
56+
> If you are not using the NSX interface, but rather the API or another external tool (such as Public VCF as-a-Service), you will need to use the account provided by OVHcloud as an identifier, followed by the PCC FQDN. For example `[email protected]` in the example below.
5757
>
5858
5959
![01 NSX Connection 02](images/01-nsxt-connection02.png){.thumbnail}

0 commit comments

Comments
 (0)