Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Commit

Permalink
fix
Browse files Browse the repository at this point in the history
  • Loading branch information
wojcik-dorota committed Oct 3, 2023
1 parent 7853227 commit 6a2d211
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/platform/howto/vpc-peering-upcloud.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,8 +77,8 @@ To establish a VPC peering from UpCloud to Aiven, use `UpCloud API <https://deve
.. topic:: Where

* NAME_OF_YOUR_PEERING is an arbitrary name you give to your peering, for example ``peering upcloud->aiven``.
* UPCLOUD_SDN_NETWORK_UUID is the UUID you acquired in :ref:`UpCloud SDN network UUID <upcloud-uuid>`, for example ``03126dc1-a69f-4bc2-8b24-e31c22d64712``.
* AIVEN_VPC_NETWORK_UUID is the UUID you acquired in :ref:`Aiven VPC network UUID <aiven-uuid>`, for example ``03585987-bf7d-4544-8e9b-5a1b4d74a333``.
* UPCLOUD_SDN_NETWORK_UUID is the UUID you acquired in :ref:`Get UpCloud SDN network UUID <upcloud-uuid>`, for example ``03126dc1-a69f-4bc2-8b24-e31c22d64712``.
* AIVEN_VPC_NETWORK_UUID is the UUID you acquired in :ref:`Set up VPC peering from Aiven <aiven-uuid>`, for example ``03585987-bf7d-4544-8e9b-5a1b4d74a333``.

Check failure on line 81 in docs/platform/howto/vpc-peering-upcloud.rst

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/platform/howto/vpc-peering-upcloud.rst#L81

[Aiven.common_replacements] Use 'Aiven' instead of 'aiven'.
Raw output
{"message": "[Aiven.common_replacements] Use 'Aiven' instead of 'aiven'.", "location": {"path": "docs/platform/howto/vpc-peering-upcloud.rst", "range": {"start": {"line": 81, "column": 94}}}, "severity": "ERROR"}

Attributes
''''''''''
Expand Down Expand Up @@ -134,8 +134,8 @@ If your peering API request is successful, you can extect a response similar to
.. topic:: Where

* NAME_OF_YOUR_PEERING is an arbitrary name you give to your peering, for example ``peering upcloud->aiven``.
* UPCLOUD_SDN_NETWORK_UUID is the UUID you acquired in :ref:`UpCloud SDN network UUID <upcloud-uuid>`, for example ``03126dc1-a69f-4bc2-8b24-e31c22d64712``.
* AIVEN_VPC_NETWORK_UUID is the UUID you acquired in :ref:`Aiven VPC network UUID <aiven-uuid>`, for example ``03585987-bf7d-4544-8e9b-5a1b4d74a333``.
* UPCLOUD_SDN_NETWORK_UUID is the UUID you acquired in :ref:`Get UpCloud SDN network UUID <upcloud-uuid>`, for example ``03126dc1-a69f-4bc2-8b24-e31c22d64712``.
* AIVEN_VPC_NETWORK_UUID is the UUID you acquired in :ref:`Set up VPC peering from Aiven <aiven-uuid>`, for example ``03585987-bf7d-4544-8e9b-5a1b4d74a333``.

Check failure on line 138 in docs/platform/howto/vpc-peering-upcloud.rst

View workflow job for this annotation

GitHub Actions / vale

[vale] docs/platform/howto/vpc-peering-upcloud.rst#L138

[Aiven.common_replacements] Use 'Aiven' instead of 'aiven'.
Raw output
{"message": "[Aiven.common_replacements] Use 'Aiven' instead of 'aiven'.", "location": {"path": "docs/platform/howto/vpc-peering-upcloud.rst", "range": {"start": {"line": 138, "column": 94}}}, "severity": "ERROR"}
* PEERING_UUID is the UUID of your new peering, for example ``0f7984bc-5d72-4aaf-b587-90e6a8f32efc``.

Error responses
Expand Down

0 comments on commit 6a2d211

Please sign in to comment.