openstack/openstack-helm
Code Issues Proposed changes

[Docs] Fixed a few typos

Browse Source 
This patch fixes several typos I found while reading the documentation

Change-Id: I01b1766403761c7e85303a214baeb0c5337fd0c2
Signed-off-by: Manuel Buil <mbuil@suse.com>
This commit is contained in:
Manuel Buil 2019-04-22 17:01:11 +02:00
parent 22289a945c
commit 0f459ecfee
4 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/devref/endpoints.rst
View File

@ -81,7 +81,7 @@ there is a second convention here. All ``{{ define }}`` macros in charts
should be pre-fixed with the chart that is defining them. This allows
developers to easily identify the source of a Helm macro and also avoid
namespace collisions. In the example above, the macro
``endpoint_type_look_addr`` is defined in the ``helm-toolkit`` chart.
``endpoint_type_lookup_addr`` is defined in the ``helm-toolkit`` chart.
This macro is passing three parameters (aided by the ``tuple`` method
built into the go/sprig templating library used by Helm):

4
doc/source/devref/pod-disruption-budgets.rst
View File

@ -1,14 +1,14 @@
Pod Disruption Budgets
----------------------
OpenStack-Helm leverages PodDistruptionBudgets to enforce quotas
OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas
that ensure that a certain number of replicas of a pod are available
at any given time. This is particularly important in the case when a Kubernetes
node needs to be drained.
These quotas are configurable by modifying the ``minAvailable`` field
within each PodDistruptionBudget manifest, which is conveniently mapped
within each PodDisruptionBudget manifest, which is conveniently mapped
to a templated variable inside the ``values.yaml`` file.
The ``min_available`` within each service's ``values.yaml`` file can be
represented by either a whole number, such as ``1``, or a percentage,

8
doc/source/locale/id/LC_MESSAGES/doc-devref.po
View File

@ -486,12 +486,12 @@ msgstr ""
"konfigurasi Keystone imajiner dijelaskan di sini:"
msgid ""
"OpenStack-Helm leverages PodDistruptionBudgets to enforce quotas that ensure "
"OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas that ensure "
"that a certain number of replicas of a pod are available at any given time. "
"This is particularly important in the case when a Kubernetes node needs to "
"be drained."
msgstr ""
"OpenStack-Helm memanfaatkan PodDistruptionBudgets untuk menegakkan kuota "
"OpenStack-Helm memanfaatkan PodDisruptionBudgets untuk menegakkan kuota "
"yang memastikan bahwa sejumlah replika pod tertentu tersedia pada waktu "
"tertentu. Ini sangat penting dalam kasus ketika node Kubernetes perlu "
"dikuras."
@ -734,7 +734,7 @@ msgstr ""
msgid ""
"These quotas are configurable by modifying the ``minAvailable`` field within "
"each PodDistruptionBudget manifest, which is conveniently mapped to a "
"each PodDisruptionBudget manifest, which is conveniently mapped to a "
"templated variable inside the ``values.yaml`` file. The ``min_available`` "
"within each service's ``values.yaml`` file can be represented by either a "
"whole number, such as ``1``, or a percentage, such as ``80%``. For example, "
@ -744,7 +744,7 @@ msgid ""
"of that pod are running."
msgstr ""
"Kuota ini dapat dikonfigurasi dengan memodifikasi field ``minAvailable`` "
"dalam setiap manifes PodDistruptionBudget, yang dengan mudah dipetakan ke "
"dalam setiap manifes PodDisruptionBudget, yang dengan mudah dipetakan ke "
"variabel templated di dalam file ``values.yaml``. ``Min_available`` dalam "
"file ``values.yaml`` masing-masing layanan dapat direpresentasikan dengan "
"salah satu bilangan bulat, seperti ``1``, atau persentase, seperti ``80%``. "

8
doc/source/locale/ko_KR/LC_MESSAGES/doc-devref.po
View File

@ -471,13 +471,13 @@ msgstr ""
"기 있습니다:"
msgid ""
"OpenStack-Helm leverages PodDistruptionBudgets to enforce quotas that ensure "
"OpenStack-Helm leverages PodDisruptionBudgets to enforce quotas that ensure "
"that a certain number of replicas of a pod are available at any given time. "
"This is particularly important in the case when a Kubernetes node needs to "
"be drained."
msgstr ""
"OpenStack-Helm은 주어진 시간에 특정 수의 pod 복제본의 가용성을 보장하도록 할"
"당량을 강제하기 위해 PodDistruptionBudget을 활용합니다. 이는 Kubernetes 노드"
"당량을 강제하기 위해 PodDisruptionBudget을 활용합니다. 이는 Kubernetes 노드"
"가 빠져야 될 필요가 있는 경우에 특히 중요합니다."
msgid ""
@ -702,7 +702,7 @@ msgstr ""
msgid ""
"These quotas are configurable by modifying the ``minAvailable`` field within "
"each PodDistruptionBudget manifest, which is conveniently mapped to a "
"each PodDisruptionBudget manifest, which is conveniently mapped to a "
"templated variable inside the ``values.yaml`` file. The ``min_available`` "
"within each service's ``values.yaml`` file can be represented by either a "
"whole number, such as ``1``, or a percentage, such as ``80%``. For example, "
@ -712,7 +712,7 @@ msgid ""
"of that pod are running."
msgstr ""
"이러한 할당량은 ``values.yaml`` 파일 내부의 템플릿 변수에 편리하게 매핑된 각 "
"PodDistruptionBudget 매니페스트 내의 ``minAvailable`` 필드를 수정하여 구성할 "
"PodDisruptionBudget 매니페스트 내의 ``minAvailable`` 필드를 수정하여 구성할 "
"수 있습니다. 각 서비스의 ``values.yaml`` 파일 내 ``min_available`` 는 ``1`` "
"과 같은 정수나 ``80%`` 와 같은 퍼센트로 표현될 수 있습니다. 예를 들어, 5개의 "
"pod 복제본(keystone-api)을 배포할 때, ``mun_available: 3``을 사용하면 적어도 "