doc: fixes the the repetitions (#43937)
Wow, this does not seem to be an uncommon misspelling. Might be there are some left that span over two lines. I noticed the one in the git module and then used `grep -rw 'the the'` to find some more.
This commit is contained in:
parent
8dc31a88e8
commit
d779eb1f15
11 changed files with 11 additions and 11 deletions
|
@ -24,7 +24,7 @@ and make them automatically available in your Ansible inventory.
|
|||
You may see a collection of other GCP modules that do not conform to this
|
||||
naming convention. These are the original modules primarily developed by the
|
||||
Ansible community. You will find some overlapping functionality such as with
|
||||
the the "gce" module and the new "gcp_compute_instance" module. Either can be
|
||||
the "gce" module and the new "gcp_compute_instance" module. Either can be
|
||||
used, but you may experience issues trying to use them together.
|
||||
|
||||
While the community GCP modules are not going away, Google is investing effort
|
||||
|
|
|
@ -60,7 +60,7 @@ The ``win_dsc`` module takes in a free-form of options so that it changes
|
|||
according to the resource it is managing. A list of built in resources can be
|
||||
found at `resources <https://docs.microsoft.com/en-us/powershell/dsc/resources>`_.
|
||||
|
||||
Using the the `Registry <https://docs.microsoft.com/en-us/powershell/dsc/registryresource>`_
|
||||
Using the `Registry <https://docs.microsoft.com/en-us/powershell/dsc/registryresource>`_
|
||||
resource as an example, this is the DSC definition as documented by Microsoft::
|
||||
|
||||
Registry [string] #ResourceName
|
||||
|
|
|
@ -377,7 +377,7 @@ class WapiModule(WapiBase):
|
|||
and/or keys filtered before it is sent to the API endpoint to
|
||||
be processed.
|
||||
:args proposed_object: A dict item that will be encoded and sent
|
||||
the the API endpoint with the updated data structure
|
||||
the API endpoint with the updated data structure
|
||||
:returns: updated object to be sent to API endpoint
|
||||
'''
|
||||
keys = set()
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
The Ansible AWS modules and these guidelines are maintained by the Ansible AWS Working Group. For
|
||||
further information see
|
||||
[the AWS working group community page](https://github.com/ansible/community/tree/master/group-aws).
|
||||
If you are planning to contribute AWS modules to Ansible then getting in touch with the the working
|
||||
If you are planning to contribute AWS modules to Ansible then getting in touch with the working
|
||||
group will be a good way to start, especially because a similar module may already be under
|
||||
development.
|
||||
|
||||
|
|
|
@ -95,7 +95,7 @@ def main():
|
|||
storage_domain_service = storage_domains_service.storage_domain_service(sd_id)
|
||||
templates_service = storage_domain_service.templates_service()
|
||||
|
||||
# Find the the unregistered Template we want to register:
|
||||
# Find the unregistered Template we want to register:
|
||||
if module.params.get('unregistered'):
|
||||
templates = templates_service.list(unregistered=True)
|
||||
else:
|
||||
|
|
|
@ -94,7 +94,7 @@ def main():
|
|||
storage_domain_service = storage_domains_service.storage_domain_service(sd_id)
|
||||
vms_service = storage_domain_service.vms_service()
|
||||
|
||||
# Find the the unregistered VM we want to register:
|
||||
# Find the unregistered VM we want to register:
|
||||
if module.params.get('unregistered'):
|
||||
vms = vms_service.list(unregistered=True)
|
||||
else:
|
||||
|
|
|
@ -2095,7 +2095,7 @@ def main():
|
|||
storage_domain_service = storage_domains_service.storage_domain_service(sd_id)
|
||||
vms_service = storage_domain_service.vms_service()
|
||||
|
||||
# Find the the unregistered VM we want to register:
|
||||
# Find the unregistered VM we want to register:
|
||||
vms = vms_service.list(unregistered=True)
|
||||
vm = next(
|
||||
(vm for vm in vms if (vm.id == module.params['id'] or vm.name == module.params['name'])),
|
||||
|
|
|
@ -96,7 +96,7 @@ options:
|
|||
- "The CSR may contain multiple Subject Alternate Names, but each one
|
||||
will lead to an individual challenge that must be fulfilled for the
|
||||
CSR to be signed."
|
||||
- "I(Note): the private key used to create the CSR I(must not) be the the
|
||||
- "I(Note): the private key used to create the CSR I(must not) be the
|
||||
account key. This is a bad idea from a security point of view, and
|
||||
the CA should not accept the CSR. Let's Encrypt will return an error
|
||||
in this case."
|
||||
|
|
|
@ -36,7 +36,7 @@ options:
|
|||
required: true
|
||||
version:
|
||||
description:
|
||||
- What version of the repository to check out. This can be the
|
||||
- What version of the repository to check out. This can be
|
||||
the literal string C(HEAD), a branch name, a tag name.
|
||||
It can also be a I(SHA-1) hash, in which case C(refspec) needs
|
||||
to be specified if the given revision is not already available.
|
||||
|
|
|
@ -39,7 +39,7 @@ options:
|
|||
type: bool
|
||||
node:
|
||||
description:
|
||||
- The node where the the service processor network should be enabled
|
||||
- The node where the service processor network should be enabled
|
||||
required: true
|
||||
dhcp:
|
||||
description:
|
||||
|
|
|
@ -262,7 +262,7 @@ dest:
|
|||
sample: "/etc/pam.d/system-auth"
|
||||
backupdest:
|
||||
description:
|
||||
- "The file name of the the backup file, if created."
|
||||
- "The file name of the backup file, if created."
|
||||
returned: success
|
||||
type: string
|
||||
version_added: 2.6
|
||||
|
|
Loading…
Reference in a new issue