docs: fix typos

Change-Id: Ic99f2ac8f8052e6e0eaaa75650f465ff079f69cb
This commit is contained in:
Pierre Riteau 2024-10-07 09:00:49 +02:00
parent e444400214
commit 37da40cfb6
3 changed files with 3 additions and 3 deletions

View File

@ -836,7 +836,7 @@ Network Time Protocol (NTP) may be configured via variables in
configured via ``chrony_ntp_servers``, and by default the ``pool.ntp.org``
servers are used.
Internally, kayobe uses the the `mrlesmithjr.chrony
Internally, kayobe uses the `mrlesmithjr.chrony
<https://galaxy.ansible.com/mrlesmithjr/chrony>`__ Ansible role. Rather than
maintain a mapping between the ``kayobe`` and ``mrlesmithjr.chrony`` worlds, all
variables are simply passed through. This means you can use all variables that

View File

@ -11,7 +11,7 @@ environment or are dependencies of the control plane.
Configuration
=============
To deploy an infrastructure VM, add a new host to the the ``infra-vms`` group
To deploy an infrastructure VM, add a new host to the ``infra-vms`` group
in the inventory:
.. code-block:: ini

View File

@ -174,7 +174,7 @@ Hooks allow you to automatically execute custom playbooks at certain points duri
the execution of a kayobe command. The point at which a hook is run is referred to
as a ``target``. Please see the :ref:`list of available targets<Hook Targets>`.
Hooks are created by symlinking an existing playbook into the the relevant directory under
Hooks are created by symlinking an existing playbook into the relevant directory under
``$KAYOBE_CONFIG_PATH/hooks``. Kayobe will search the hooks directory for sub-directories
matching ``<command>.<target>.d``, where ``command`` is the name of a kayobe command
with any spaces replaced with dashes, and ``target`` is one of the supported targets for