From e5967c02f572971e6e8ac380829902dc745b0d6c Mon Sep 17 00:00:00 2001 From: "Kian Meng, Ang" Date: Wed, 15 Dec 2021 04:54:32 +0800 Subject: [PATCH] Fix typos in docs (#76526) --- docs/docsite/Makefile | 2 +- .../developing_modules_best_practices.rst | 2 +- .../developing_modules_general_aci.rst | 2 +- .../rst/locales/ja/LC_MESSAGES/dev_guide.po | 6 ++--- .../rst/locales/ja/LC_MESSAGES/plugins.po | 4 ++-- .../locales/ja/LC_MESSAGES/porting_guides.po | 22 +++++++++---------- .../ja/LC_MESSAGES/reference_appendices.po | 8 +++---- .../locales/ja/LC_MESSAGES/scenario_guides.po | 10 ++++----- .../rst/porting_guides/porting_guide_2.10.rst | 14 ++++++------ .../rst/porting_guides/porting_guide_3.rst | 6 ++--- .../rst/porting_guides/porting_guide_5.rst | 4 ++-- .../rst/scenario_guides/guide_packet.rst | 4 ++-- .../docsite/rst/scenario_guides/guide_rax.rst | 2 +- .../rst/scenario_guides/guide_scaleway.rst | 4 ++-- 14 files changed, 45 insertions(+), 45 deletions(-) diff --git a/docs/docsite/Makefile b/docs/docsite/Makefile index c40270b4fdd..e8c1e8fae15 100644 --- a/docs/docsite/Makefile +++ b/docs/docsite/Makefile @@ -175,7 +175,7 @@ clean: rm -rf "rst/collections/$$filename"; \ fi \ done - @echo "Cleanning up generated ansible_structure" + @echo "Cleaning up generated ansible_structure" find . -type l -delete @echo "Cleaning up legacy generated rst locations" rm -rf rst/modules diff --git a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst index b28d37a1182..42d1324e504 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst @@ -105,7 +105,7 @@ Handling module failures When your module fails, help users understand what went wrong. If you are using the ``AnsibleModule`` common Python code, the ``failed`` element will be included for you automatically when you call ``fail_json``. For polite module failure behavior: * Include a key of ``failed`` along with a string explanation in ``msg``. If you don't do this, Ansible will use standard return codes: 0=success and non-zero=failure. -* Don't raise a traceback (stacktrace). Ansible can deal with stacktraces and automatically converts anything unparseable into a failed result, but raising a stacktrace on module failure is not user-friendly. +* Don't raise a traceback (stacktrace). Ansible can deal with stacktraces and automatically converts anything unparsable into a failed result, but raising a stacktrace on module failure is not user-friendly. * Do not use ``sys.exit()``. Use ``fail_json()`` from the module object. Handling exceptions (bugs) gracefully diff --git a/docs/docsite/rst/dev_guide/developing_modules_general_aci.rst b/docs/docsite/rst/dev_guide/developing_modules_general_aci.rst index 072bf67298d..b9eb8c981b5 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_general_aci.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_general_aci.rst @@ -325,7 +325,7 @@ You can test your ``construct_url()`` and ``payload()`` arguments without access import json from ansible.module_utils.network.aci.aci import ACIModule - # Just another class mimicing a bare AnsibleModule class for construct_url() and payload() methods + # Just another class mimicking a bare AnsibleModule class for construct_url() and payload() methods class AltModule(): params = dict( host='dummy', diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po index d5733515d23..59eafe0680f 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/dev_guide.po @@ -2551,7 +2551,7 @@ msgid "Include a key of ``failed`` along with a string explanation in ``msg``. I msgstr "``msg`` の文字列の説明と共に ``failed`` のキーが含まれるようにします。これを行わないと、Ansible は標準の戻りコード 0=success および non-zero=failure を使用します。" #: ../../rst/dev_guide/developing_modules_best_practices.rst:108 -msgid "Don't raise a traceback (stacktrace). Ansible can deal with stacktraces and automatically converts anything unparseable into a failed result, but raising a stacktrace on module failure is not user-friendly." +msgid "Don't raise a traceback (stacktrace). Ansible can deal with stacktraces and automatically converts anything unparsable into a failed result, but raising a stacktrace on module failure is not user-friendly." msgstr "トレースバック (スタックトレース) は発生させません。Ansible はスタックトレースを扱うことができ、解析できないものは自動的に失敗した結果に変換しますが、モジュールの失敗時にスタックトレースを発生させるのはユーザーフレンドリーではありません。" #: ../../rst/dev_guide/developing_modules_best_practices.rst:109 @@ -5392,11 +5392,11 @@ msgstr "接続プラグインにより、Ansible はターゲットホストに #: ../../rst/dev_guide/developing_plugins.rst:292 msgid "Ansible version 2.1 introduced the ``smart`` connection plugin. The ``smart`` connection type allows Ansible to automatically select either the ``paramiko`` or ``openssh`` connection plugin based on system capabilities, or the ``ssh`` connection plugin if OpenSSH supports ControlPersist." -msgstr "Ansible バージョン 2.1 では、``smart`` 接続プラグインが導入されます。``smart`` 接続タイプにより、Ansible は、システム機能に基づいて、``paramiko`` 接続プラグインまたは ``openssh`` 接続プラグインのいずれかを自動的に選択できますが、OpenSSH が ControlPersist に対応している場合は ``ssh`` の Connetion プラグインを選択します。" +msgstr "Ansible バージョン 2.1 では、``smart`` 接続プラグインが導入されます。``smart`` 接続タイプにより、Ansible は、システム機能に基づいて、``paramiko`` 接続プラグインまたは ``openssh`` 接続プラグインのいずれかを自動的に選択できますが、OpenSSH が ControlPersist に対応している場合は ``ssh`` の Connection プラグインを選択します。" #: ../../rst/dev_guide/developing_plugins.rst:294 msgid "To create a new connection plugin (for example, to support SNMP, Message bus, or other transports), copy the format of one of the existing connection plugins and drop it into ``connection`` directory on your :ref:`local plugin path `." -msgstr "新しい connetion プラグイン (SNMP、メッセージバス、またはその他のトランスポートをサポートする場合など) を作成するには、既存の connetion プラグインのいずれかの形式をコピーして、:ref:`ローカルプラグインパス ` にある ``connection`` ディレクトリーに置きます。" +msgstr "新しい connection プラグイン (SNMP、メッセージバス、またはその他のトランスポートをサポートする場合など) を作成するには、既存の connection プラグインのいずれかの形式をコピーして、:ref:`ローカルプラグインパス ` にある ``connection`` ディレクトリーに置きます。" #: ../../rst/dev_guide/developing_plugins.rst:296 msgid "Connection plugins can support common options (such as the ``--timeout`` flag) by defining an entry in the documentation for the attribute name (in this case ``timeout``). If the common option has a non-null default, the plugin should define the same default since a different default would be ignored." diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po index 1b9d9eda0a1..db9dd05a4a0 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/plugins.po @@ -182,7 +182,7 @@ msgstr "become プラグイン" #: ../../rst/plugins/become.rst:12 msgid "Become plugins work to ensure that Ansible can use certain privilege escalation systems when running the basic commands to work with the target machine as well as the modules required to execute the tasks specified in the play." -msgstr "bocome プラグインは、基本的なコマンドの実行時に、Ansible が特定の特権昇格システムを使用して、プレイで指定されたタスクを実行するのに必要なモジュールやターゲットマシンと連携できるようにします。" +msgstr "become プラグインは、基本的なコマンドの実行時に、Ansible が特定の特権昇格システムを使用して、プレイで指定されたタスクを実行するのに必要なモジュールやターゲットマシンと連携できるようにします。" #: ../../rst/plugins/become.rst:16 msgid "These utilities (``sudo``, ``su``, ``doas``, and so on) generally let you 'become' another user to execute a command with the permissions of that user." @@ -726,7 +726,7 @@ msgstr "キャッシュをサポートする inventory プラグインは、``an #: ../../rst/plugins/inventory.rst:122 msgid "Here is an example of setting inventory caching with some fact caching defaults for the cache plugin used and the timeout in an ``ansible.cfg`` file:" -msgstr "以下は、``ansible.cfg`` ファイルに、使用する chache プラグインにデフォルト設定されているファクトキャッシュの一部を使用したインベントリーキャッシュと、タイムアウトを設定する例です。" +msgstr "以下は、``ansible.cfg`` ファイルに、使用する cache プラグインにデフォルト設定されているファクトキャッシュの一部を使用したインベントリーキャッシュと、タイムアウトを設定する例です。" #: ../../rst/plugins/inventory.rst:140 msgid "You can use ``ansible-doc -t inventory -l`` to see the list of available plugins. Use ``ansible-doc -t inventory `` to see plugin-specific documentation and examples." diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po index 1fbe467adc0..17566e883dd 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/porting_guides.po @@ -310,7 +310,7 @@ msgstr "Connection プラグイン" #: ../../rst/porting_guides/porting_guide_2.0.rst:375 #: ../../rst/porting_guides/porting_guide_2.0.rst:390 msgid "connection plugins" -msgstr "conneciton プラグイン" +msgstr "connection プラグイン" #: ../../rst/porting_guides/porting_guide_2.0.rst:235 #: ../../rst/porting_guides/porting_guide_2.0.rst:378 @@ -632,7 +632,7 @@ msgid "Major Changes" msgstr "主な変更点" #: ../../rst/porting_guides/porting_guide_2.10.rst:115 -msgid "Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, wihch is included in Ansible 2.10." +msgid "Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, which is included in Ansible 2.10." msgstr "community.okd コレクションのバージョンを 1.0.0 に制限しました。これまで含まれていたバージョン 1.0.1 は、kubernetes.core に依存していたため、Ansible 2.10 に含まれていない追加のコレクションをインストールする必要がありました。バージョン 1.0.0 は、Ansible 2.10 に含まれている community.kubernetes を使用している以外は、1.0.1 と基本的に同じです。" #: ../../rst/porting_guides/porting_guide_2.10.rst:118 @@ -849,7 +849,7 @@ msgstr "nb_inventory - ``group_by`` オプションとして ``status`` を追 #: ../../rst/porting_guides/porting_guide_2.10.rst:232 #: ../../rst/porting_guides/porting_guide_3.rst:224 -msgid "nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwite. (#377)" +msgid "nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwrite. (#377)" msgstr "nb_inventory - ``config_context`` または ``custom_field`` の上書きを許可する ``extracted_primary_ip`` を移動します。(#377)" #: ../../rst/porting_guides/porting_guide_2.10.rst:233 @@ -1085,7 +1085,7 @@ msgstr "docker_image - ``build.pull`` オプションのデフォルトが ``fal #: ../../rst/porting_guides/porting_guide_2.10.rst:342 #: ../../rst/porting_guides/porting_guide_3.rst:267 -msgid "docker_image_facts - this alias is on longer availabe, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." +msgid "docker_image_facts - this alias is on longer available, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1)." msgstr "docker_image - このエイリアスは利用できなくなります。代わりに ``docker_image_info`` を使用します (https://github.com/ansible-collections/community.docker/pull/1)。" #: ../../rst/porting_guides/porting_guide_2.10.rst:343 @@ -1356,7 +1356,7 @@ msgid "grafana_datasource doesn't set password correctly (#113)" msgstr "grafana_datasource でパスワードが正しく設定されない (#113)" #: ../../rst/porting_guides/porting_guide_2.10.rst:471 -msgid "cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superceeded by ``oif_ps``." +msgid "cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superseded by ``oif_ps``." msgstr "cisco.nxos.nxos_igmp_interface - 非推奨の ``oif_prefix`` オプションおよび ``oif_source`` オプションをサポートしなくなりました。これらは ``oif_ps`` に置き換えられました。" #: ../../rst/porting_guides/porting_guide_2.10.rst:472 @@ -1364,7 +1364,7 @@ msgid "community.grafana.grafana_dashboard - the parameter ``message`` is rename msgstr "community.grafana.grafana_dashboard - ``message`` は内部的に Ansible Core Engine で使用されるため、パラメーター ``message`` の名前が ``commit_message`` に変更されました。" #: ../../rst/porting_guides/porting_guide_2.10.rst:473 -msgid "purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superceeded by ``nfsv3``." +msgid "purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superseded by ``nfsv3``." msgstr "purestorage.flashblade.purefb_fs - 非推奨の ``nfs`` オプションに対応しなくなりました。これは ``nfsv3`` に置き換えられました。" #: ../../rst/porting_guides/porting_guide_2.10.rst:476 @@ -1614,7 +1614,7 @@ msgid "Changed ``role`` to ``prefix_role`` in ``netbox_prefix.py`` (https://gith msgstr "``netbox_prefix.py`` の ``role`` を ``prefix_role`` へ変更しました (https://github.com/netbox-community/ansible_modules/issues/9)。" #: ../../rst/porting_guides/porting_guide_2.10.rst:564 -msgid "Module failures when required fields arent provided (https://github.com/netbox-community/ansible_modules/issues/24)" +msgid "Module failures when required fields aren't provided (https://github.com/netbox-community/ansible_modules/issues/24)" msgstr "必須フィールドが提供されていない場合のモジュールの失敗 (https://github.com/netbox-community/ansible_modules/issues/24)" #: ../../rst/porting_guides/porting_guide_2.10.rst:565 @@ -2506,8 +2506,8 @@ msgid "redfish_config and redfish_command - the behavior to select the first Sys msgstr "redfish_config および redfish_command - 複数のリソースが存在する場合に修正する最初の System リソース、Manager リソース、または Chassis リソースを選択する動作が削除されます。新しい ``resource_id`` オプションを使用して、変更する対象のリソースを指定します。" #: ../../rst/porting_guides/porting_guide_2.10.rst:940 -msgid "redfish_config, redfish_command - Behavior to modify the first System, Mananger, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify." -msgstr "redfish_config、redfish_command - 複数のリソースが存在する場合、最初の System、Mananger、または Chassis リソースを修正する動作は非推奨です。新しい ``resource_id`` オプションを使用して、変更する対象のリソースを指定してください。" +msgid "redfish_config, redfish_command - Behavior to modify the first System, Manager, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify." +msgstr "redfish_config、redfish_command - 複数のリソースが存在する場合、最初の System、Manager、または Chassis リソースを修正する動作は非推奨です。新しい ``resource_id`` オプションを使用して、変更する対象のリソースを指定してください。" #: ../../rst/porting_guides/porting_guide_2.10.rst:941 #: ../../rst/porting_guides/porting_guide_3.rst:431 @@ -6136,7 +6136,7 @@ msgid "The Google cloud inventory script ``gce.py`` has been migrated to the ``c msgstr "Google クラウドインベントリースクリプト ``gce.py`` を ``community.google`` コレクションに移行しました。使用を継続するには、``community.google`` コレクションをインストールしてください。" #: ../../rst/porting_guides/porting_guide_3.rst:85 -msgid "archive - remove path folder itself when ``remove`` paramater is true (https://github.com/ansible-collections/community.general/issues/1041)." +msgid "archive - remove path folder itself when ``remove`` parameter is true (https://github.com/ansible-collections/community.general/issues/1041)." msgstr "archive - ``remove`` パラメーターが true の場合にパスフォルダー自体を削除します (https://github.com/ansible-collections/community.general/issues/1041)。" #: ../../rst/porting_guides/porting_guide_3.rst:87 @@ -6192,7 +6192,7 @@ msgid "os10_bgp - Changed \"subnet\" key as list format instead of dictionary f msgstr "os10_bgp - listen コマンドの複数の neighbor 接頭辞をサポートするために、「listen」キーの「subnet」キーを、ディクショナリー形式からリスト形式に変更しました。" #: ../../rst/porting_guides/porting_guide_3.rst:134 -msgid "os10_bgp - Changed \"vrf\" key as list format instead of dictionary format to supprot multiple VRF in router BGP and changed the \"vrf\" key name to \"vrfs\"" +msgid "os10_bgp - Changed \"vrf\" key as list format instead of dictionary format to support multiple VRF in router BGP and changed the \"vrf\" key name to \"vrfs\"" msgstr "os10_bgp - ルーター BGP で複数の VRF をサポートするために、「vrf」キーをディクショナリー形式ではなくリスト形式に変更し、「vrf」キーの名前を「vrfs」に変更しました。" #: ../../rst/porting_guides/porting_guide_3.rst:137 diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po index af7e1e04fe0..c0524355a4e 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/reference_appendices.po @@ -3048,7 +3048,7 @@ msgstr "DEFAULT_NO_TARGET_SYSLOG" #: ../../rst/reference_appendices/config.rst:1661 #: ../../rst/reference_appendices/config.rst:3861 -msgid "Toggle Ansible logging to syslog on the target when it executes tasks. On Windows hosts this will disable a newer style PowerShell modules from writting to the event log." +msgid "Toggle Ansible logging to syslog on the target when it executes tasks. On Windows hosts this will disable a newer style PowerShell modules from writing to the event log." msgstr "タスクの実行時に、Ansible ログをターゲットの syslog へ切り替えます。Windows ホストでは、これにより、新しいスタイルの PowerShell モジュールがイベントログに書き込むことができなくなります。" #: ../../rst/reference_appendices/config.rst:1666 @@ -3849,7 +3849,7 @@ msgid "GALAXY_DISPLAY_PROGRESS" msgstr "GALAXY_DISPLAY_PROGRESS" #: ../../rst/reference_appendices/config.rst:2235 -msgid "Some steps in ``ansible-galaxy`` display a progress wheel which can cause issues on certain displays or when outputing the stdout to a file. This config option controls whether the display wheel is shown or not. The default is to show the display wheel if stdout has a tty." +msgid "Some steps in ``ansible-galaxy`` display a progress wheel which can cause issues on certain displays or when outputting the stdout to a file. This config option controls whether the display wheel is shown or not. The default is to show the display wheel if stdout has a tty." msgstr "``ansible-galaxy`` の一部の手順では、特定の表示で、または標準出力 (stdout) をファイルに出力するときに問題が発生する可能性のある進行状況ホイールを表示します。この設定オプションは、表示ホイールを表示するかどうかを制御します。デフォルトでは、stdout に tty があると、表示ホイールが表示されます。" #: ../../rst/reference_appendices/config.rst:2241 @@ -4422,7 +4422,7 @@ msgstr "OLD_PLUGIN_CACHE_CLEARING" #: ../../rst/reference_appendices/config.rst:2656 #: ../../rst/reference_appendices/config.rst:4421 -msgid "Previously Ansible would only clear some of the plugin loading caches when loading new roles, this led to some behaviours in which a plugin loaded in prevoius plays would be unexpectedly 'sticky'. This setting allows to return to that behaviour." +msgid "Previously Ansible would only clear some of the plugin loading caches when loading new roles, this led to some behaviours in which a plugin loaded in previous plays would be unexpectedly 'sticky'. This setting allows to return to that behaviour." msgstr "以前の Ansible は、新しいロールを読み込むときにプラグインの読み込みキャッシュの一部のみを削除していました。これにより、以前のプレイで読み込まれたプラグインが予期せず「スティッキー」になる動作が発生しました。この設定により、その動作に戻ることができます。" #: ../../rst/reference_appendices/config.rst:2662 @@ -5643,7 +5643,7 @@ msgid "See also :ref:`GALAXY_TOKEN_PATH `" msgstr "「:ref:`GALAXY_TOKEN_PATH `」も参照してください。" #: ../../rst/reference_appendices/config.rst:4233 -msgid "Some steps in ``ansible-galaxy`` display a progress wheel which can cause issues on certain displays or when outputing the stdout to a file.This config option controls whether the display wheel is shown or not.The default is to show the display wheel if stdout has a tty." +msgid "Some steps in ``ansible-galaxy`` display a progress wheel which can cause issues on certain displays or when outputting the stdout to a file.This config option controls whether the display wheel is shown or not.The default is to show the display wheel if stdout has a tty." msgstr "``ansible-galaxy`` の一部の手順では、特定の表示で、または標準出力 (stdout) をファイルに出力するときに問題を引き起こす可能性のある進行状況ホイールを表示します。この設定オプションは、表示ホイールを表示するかどうかを制御します。デフォルトでは、stdout に tty があると、表示ホイールが表示されます。" #: ../../rst/reference_appendices/config.rst:4235 diff --git a/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po b/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po index 4f2be9e3513..d8cbd550485 100644 --- a/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po +++ b/docs/docsite/rst/locales/ja/LC_MESSAGES/scenario_guides.po @@ -3372,12 +3372,12 @@ msgstr "パケットでは、デバイスと予約済みの IP アドレスは #: ../../rst/scenario_guides/guide_packet.rst:37 #: ../../rst/scenario_guides/guide_scaleway.rst:39 -msgid "If you want to use a new SSH keypair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as:" +msgid "If you want to use a new SSH key pair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as:" msgstr "本チュートリアルで新しい SSH キーペアを使用する場合は、以下のように ``./id_rsa`` および ``./id_rsa.pub`` に生成してください。" #: ../../rst/scenario_guides/guide_packet.rst:43 #: ../../rst/scenario_guides/guide_scaleway.rst:45 -msgid "If you want to use an existing keypair, just copy the private and public key over to the playbook directory." +msgid "If you want to use an existing key pair, just copy the private and public key over to the playbook directory." msgstr "既存のキーペアを使用する場合は、秘密鍵と公開鍵を Playbook ディレクトリーにコピーします。" #: ../../rst/scenario_guides/guide_packet.rst:47 @@ -3698,7 +3698,7 @@ msgid "While you don't need to know how it works, it may be interesting to know msgstr "どのように機能するかを知る必要はありませんが、返される変数の種類を把握しておくといいでしょう、" #: ../../rst/scenario_guides/guide_rax.rst:317 -msgid "The ``rax_facts`` module provides facts as followings, which match the ``rax.py`` inventory script:" +msgid "The ``rax_facts`` module provides facts as following, which match the ``rax.py`` inventory script:" msgstr "``rax_facts`` モジュールは、``rax.py`` インベントリースクリプトに一致する以下のようなファクトを提供します。" #: ../../rst/scenario_guides/guide_rax.rst:408 @@ -5191,7 +5191,7 @@ msgid "Network routes" msgstr "ネットワークルート" #: ../../rst/scenario_guides/vmware_rest_scenarios/vm_tool_information.rst:82 -msgid "Use ``vcenter_vm_guest_networking_routes_info`` to explore the route table of your vitual machine." +msgid "Use ``vcenter_vm_guest_networking_routes_info`` to explore the route table of your virtual machine." msgstr "仮想マシンのルートテーブルを確認するには、``vcenter_vm_guest_networking_routes_info`` を使用します。" #: ../../rst/scenario_guides/vmware_scenarios/faq.rst:5 @@ -6648,7 +6648,7 @@ msgid "instanceUuid (str, optional)" msgstr "instanceUuid (str, optional)" #: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:257 -msgid "VirtualCenter-specific 128-bit UUID of a virtual machine, represented as a hexademical string. This identifier is used by VirtualCenter to uniquely identify all virtual machine instances, including those that may share the same SMBIOS UUID." +msgid "VirtualCenter-specific 128-bit UUID of a virtual machine, represented as a hexadecimal string. This identifier is used by VirtualCenter to uniquely identify all virtual machine instances, including those that may share the same SMBIOS UUID." msgstr "仮想マシンの VirtualCenter 固有の 128 ビットの UUID は 16 進法として表示されます。この識別子は、同じ SMBIOS UUID を共有する可能性のある仮想マシンインスタンスを含め、すべての仮想マシンインスタンスを一意に識別するために VirtualCenter により使用されます。" #: ../../rst/scenario_guides/vmware_scenarios/vmware_inventory_vm_attributes.rst:260 diff --git a/docs/docsite/rst/porting_guides/porting_guide_2.10.rst b/docs/docsite/rst/porting_guides/porting_guide_2.10.rst index 9d6c63fc67f..678c28edaa1 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_2.10.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_2.10.rst @@ -112,7 +112,7 @@ community.general Major Changes ------------- -- Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, wihch is included in Ansible 2.10. +- Restricting the version of the community.okd collection to 1.0.0. The previously included version, 1.0.1, had a dependency on kubernetes.core and thus required the installation of an additional collection that was not included in Ansible 2.10. Version 1.0.0 is essentially identical to 1.0.1, except that it uses community.kubernetes, which is included in Ansible 2.10. ovirt.ovirt ~~~~~~~~~~~ @@ -229,7 +229,7 @@ netbox.netbox - nb_inventory - Add ``dns_name`` option that adds ``dns_name`` to the host when ``True`` and device has a primary IP address. (#394) - nb_inventory - Add ``status`` as a ``group_by`` option. (398) -- nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwite. (#377) +- nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwrite. (#377) - nb_inventory - Services are now a list of integers due to NetBox 2.10 changes. (#396) - nb_lookup - Allow ID to be passed in and use ``.get`` instead of ``.filter``. (#376) - nb_lookup - Allow ``api_endpoint`` and ``token`` to be found via env. (#391) @@ -339,7 +339,7 @@ community.docker - docker_image - the ``source`` option is now mandatory (https://github.com/ansible-collections/community.docker/pull/1). - docker_image - the ``use_tls`` option has been removed. Use ``tls`` and ``validate_certs`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_image - the default of the ``build.pull`` option changed to ``false`` (https://github.com/ansible-collections/community.docker/pull/1). -- docker_image_facts - this alias is on longer availabe, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1). +- docker_image_facts - this alias is on longer available, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_network - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1). - docker_network - the ``ipam_options`` option has been removed. Use ``ipam_config`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_service - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1). @@ -468,9 +468,9 @@ community.grafana Breaking Changes ---------------- -- cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superceeded by ``oif_ps``. +- cisco.nxos.nxos_igmp_interface - no longer supports the deprecated ``oif_prefix`` and ``oif_source`` options. These have been superseded by ``oif_ps``. - community.grafana.grafana_dashboard - the parameter ``message`` is renamed to ``commit_message`` since ``message`` is used by Ansible Core engine internally. -- purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superceeded by ``nfsv3``. +- purestorage.flashblade.purefb_fs - no longer supports the deprecated ``nfs`` option. This has been superseded by ``nfsv3``. amazon.aws ~~~~~~~~~~ @@ -561,7 +561,7 @@ netbox.netbox - Change ``ip-addresses`` key in netbox inventory plugin to ``ip_addresses`` (https://github.com/netbox-community/ansible_modules/issues/139) - Changed ``group`` to ``tenant_group`` in ``netbox_tenant.py`` (https://github.com/netbox-community/ansible_modules/issues/9) - Changed ``role`` to ``prefix_role`` in ``netbox_prefix.py`` (https://github.com/netbox-community/ansible_modules/issues/9) -- Module failures when required fields arent provided (https://github.com/netbox-community/ansible_modules/issues/24) +- Module failures when required fields aren't provided (https://github.com/netbox-community/ansible_modules/issues/24) - Renamed ``netbox_interface`` to ``netbox_device_interface`` (https://github.com/netbox-community/ansible_modules/issues/9) - This version has a few breaking changes due to new namespace and collection name. I felt it necessary to change the name of the lookup plugin and inventory plugin just not to have a non descriptive namespace call to use them. Below is an example: ``netbox.netbox.netbox`` would be used for both inventory plugin and lookup plugin, but in different contexts so no collision will arise, but confusion will. @@ -937,7 +937,7 @@ community.general - redfish_config - Deprecate ``bios_attribute_name`` and ``bios_attribute_value`` in favor of new `bios_attributes`` option. - redfish_config - the ``bios_attribute_name`` and ``bios_attribute_value`` options will be removed. To maintain the existing behavior use the ``bios_attributes`` option instead. - redfish_config and redfish_command - the behavior to select the first System, Manager, or Chassis resource to modify when multiple are present will be removed. Use the new ``resource_id`` option to specify target resource to modify. -- redfish_config, redfish_command - Behavior to modify the first System, Mananger, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify. +- redfish_config, redfish_command - Behavior to modify the first System, Manager, or Chassis resource when multiple are present is deprecated. Use the new ``resource_id`` option to specify target resource to modify. - xbps - the ``force`` option never had any effect. It is now deprecated, and will be removed in 3.0.0 (https://github.com/ansible-collections/community.general/pull/568). community.vmware diff --git a/docs/docsite/rst/porting_guides/porting_guide_3.rst b/docs/docsite/rst/porting_guides/porting_guide_3.rst index f03d559faab..ba64b85977b 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_3.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_3.rst @@ -309,7 +309,7 @@ dellemc.os10 ~~~~~~~~~~~~ - os10_bgp - Changed "subnet" key as list format instead of dictionary format under "listen" key to support multiple neighbor prefix for listen command -- os10_bgp - Changed "vrf" key as list format instead of dictionary format to supprot multiple VRF in router BGP and changed the "vrf" key name to "vrfs" +- os10_bgp - Changed "vrf" key as list format instead of dictionary format to support multiple VRF in router BGP and changed the "vrf" key name to "vrfs" ngine_io.cloudstack ~~~~~~~~~~~~~~~~~~~ @@ -406,7 +406,7 @@ netbox.netbox - nb_inventory - Add ``dns_name`` option that adds ``dns_name`` to the host when ``True`` and device has a primary IP address. (#394) - nb_inventory - Add ``status`` as a ``group_by`` option. (398) -- nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwite. (#377) +- nb_inventory - Move around ``extracted_primary_ip`` to allow for ``config_context`` or ``custom_field`` to overwrite. (#377) - nb_inventory - Services are now a list of integers due to NetBox 2.10 changes. (#396) - nb_lookup - Allow ID to be passed in and use ``.get`` instead of ``.filter``. (#376) - nb_lookup - Allow ``api_endpoint`` and ``token`` to be found via env. (#391) @@ -449,7 +449,7 @@ community.docker - docker_image - the ``source`` option is now mandatory (https://github.com/ansible-collections/community.docker/pull/1). - docker_image - the ``use_tls`` option has been removed. Use ``tls`` and ``validate_certs`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_image - the default of the ``build.pull`` option changed to ``false`` (https://github.com/ansible-collections/community.docker/pull/1). -- docker_image_facts - this alias is on longer availabe, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1). +- docker_image_facts - this alias is on longer available, use ``docker_image_info`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_network - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1). - docker_network - the ``ipam_options`` option has been removed. Use ``ipam_config`` instead (https://github.com/ansible-collections/community.docker/pull/1). - docker_service - no longer returns ``ansible_facts`` (https://github.com/ansible-collections/community.docker/pull/1). diff --git a/docs/docsite/rst/porting_guides/porting_guide_5.rst b/docs/docsite/rst/porting_guides/porting_guide_5.rst index bc5a261949f..8af3d9d1285 100644 --- a/docs/docsite/rst/porting_guides/porting_guide_5.rst +++ b/docs/docsite/rst/porting_guides/porting_guide_5.rst @@ -309,7 +309,7 @@ amazon.aws ~~~~~~~~~~ - amazon.aws collection - Due to the AWS SDKs announcing the end of support for Python less than 3.6 (https://boto3.amazonaws.com/v1/documentation/api/1.17.64/guide/migrationpy3.html) this collection now requires Python 3.6+ (https://github.com/ansible-collections/amazon.aws/pull/298). -- amazon.aws collection - The amazon.aws collection has dropped support for ``botocore<1.18.0`` and ``boto3<1.15.0``. Most modules will continue to work with older versions of the AWS SDK, however compatability with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/502). +- amazon.aws collection - The amazon.aws collection has dropped support for ``botocore<1.18.0`` and ``boto3<1.15.0``. Most modules will continue to work with older versions of the AWS SDK, however compatibility with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/502). - ec2_instance - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_instance``. - ec2_instance_info - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_instance_info``. - ec2_vpc_endpoint - The module has been migrated from the ``community.aws`` collection. Playbooks using the Fully Qualified Collection Name for this module should be updated to use ``amazon.aws.ec2_vpc_endpoint``. @@ -371,7 +371,7 @@ cloudscale_ch.cloud community.aws ~~~~~~~~~~~~~ -- community.aws collection - The community.aws collection has dropped support for ``botocore<1.18.0`` and ``boto3<1.15.0`` (https://github.com/ansible-collections/community.aws/pull/711). Most modules will continue to work with older versions of the AWS SDK, however compatability with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/442). +- community.aws collection - The community.aws collection has dropped support for ``botocore<1.18.0`` and ``boto3<1.15.0`` (https://github.com/ansible-collections/community.aws/pull/711). Most modules will continue to work with older versions of the AWS SDK, however compatibility with older versions of the SDK is not guaranteed and will not be tested. When using older versions of the SDK a warning will be emitted by Ansible (https://github.com/ansible-collections/amazon.aws/pull/442). community.ciscosmb ~~~~~~~~~~~~~~~~~~ diff --git a/docs/docsite/rst/scenario_guides/guide_packet.rst b/docs/docsite/rst/scenario_guides/guide_packet.rst index 2759ca4010f..a5df74b04d7 100644 --- a/docs/docsite/rst/scenario_guides/guide_packet.rst +++ b/docs/docsite/rst/scenario_guides/guide_packet.rst @@ -34,13 +34,13 @@ If you're not comfortable exporting your API token, you can pass it as a paramet On Packet, devices and reserved IP addresses belong to `projects `_. In order to use the packet_device module, you need to specify the UUID of the project in which you want to create or manage devices. You can find a project's UUID in the Packet portal `here `_ (it's just under the project table) or via one of the available `CLIs `_. -If you want to use a new SSH keypair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as: +If you want to use a new SSH key pair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as: .. code-block:: bash $ ssh-keygen -t rsa -f ./id_rsa -If you want to use an existing keypair, just copy the private and public key over to the playbook directory. +If you want to use an existing key pair, just copy the private and public key over to the playbook directory. Device Creation diff --git a/docs/docsite/rst/scenario_guides/guide_rax.rst b/docs/docsite/rst/scenario_guides/guide_rax.rst index c1433b3221b..1d9b380da8a 100644 --- a/docs/docsite/rst/scenario_guides/guide_rax.rst +++ b/docs/docsite/rst/scenario_guides/guide_rax.rst @@ -314,7 +314,7 @@ This can be achieved with the ``rax_facts`` module and an inventory file similar While you don't need to know how it works, it may be interesting to know what kind of variables are returned. -The ``rax_facts`` module provides facts as followings, which match the ``rax.py`` inventory script: +The ``rax_facts`` module provides facts as following, which match the ``rax.py`` inventory script: .. code-block:: json diff --git a/docs/docsite/rst/scenario_guides/guide_scaleway.rst b/docs/docsite/rst/scenario_guides/guide_scaleway.rst index 77af9ba7274..ede7d897892 100644 --- a/docs/docsite/rst/scenario_guides/guide_scaleway.rst +++ b/docs/docsite/rst/scenario_guides/guide_scaleway.rst @@ -36,13 +36,13 @@ The simplest way to authenticate yourself is to set the Scaleway API token in an If you're not comfortable exporting your API token, you can pass it as a parameter to the modules using the ``api_token`` argument. -If you want to use a new SSH keypair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as: +If you want to use a new SSH key pair in this tutorial, you can generate it to ``./id_rsa`` and ``./id_rsa.pub`` as: .. code-block:: bash $ ssh-keygen -t rsa -f ./id_rsa -If you want to use an existing keypair, just copy the private and public key over to the playbook directory. +If you want to use an existing key pair, just copy the private and public key over to the playbook directory. .. _scaleway_add_sshkey: