fix: set terminology according to lint settings

Author: noxilixon

README.md

@@ -4,7 +4,7 @@ This repository currently contains our WIP state for the infrastructure code.
 
 This is a replacement for the old [puppet repository](https://github.com/freifunk-berlin/puppet).
 
-Keep in mind that we also use ansible to configure the BerlinBackBone, this is done in the [bbb-configs repository](https://github.com/freifunk-berlin/bbb-configs).
+Keep in mind that we also use Ansible to configure the BerlinBackBone, this is done in the [bbb-configs repository](https://github.com/freifunk-berlin/bbb-configs).
 
 The code is, where necessary, quite debian centric since that's the distribution we use in our infrastructure.
 
@@ -22,18 +22,17 @@ This repository currently manages these services:
 
 ## Requirements // How to use
 
-- check out this repo and `cd` into it
+- check out this repository and `cd` into it
 - create a venv and activate it: `python -m venv venv && source venv/bin/activate`
 - install the python dependencies: `pip install -r requirements.txt`
 - install the external roles: `ansible-galaxy install -r requirements.yml`
 - install the external collections: `ansible-galaxy collection install -r requirements.yml`
 - Save the secret encryption password for ansible-vault under `./.vaultpass`
   - For alternative methods look here: <https://docs.ansible.com/ansible/latest/user_guide/vault.html>
 
-
 ## Structure
 
-We follow an adapted version of the [ansible alternative layout](https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.html#alternative-directory-layout).
+We follow an adapted version of the [Ansible alternative layout](https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.html#alternative-directory-layout).
 Where we put the inventory in an extra directory, but don't use different directories for the stages (Since we don't have any).
 Also, the roles are divided into 2 directories, one for external ones, and one for our internal ones.
 

Tutorials.md

@@ -1,6 +1,6 @@
 # Tutorials
 
-In this file, you will find some tutorials describing common workflows for using this repo. We generally assume, that all Hosts, that will be managed by this ansible repository run a recent minimal stable Debian version (at time of writing: Debian 11). Our custom roles do mostly rely on this.
+In this file, you will find some tutorials describing common workflows for using this repository. We generally assume, that all Hosts, that will be managed by this Ansible repository run a recent minimal stable Debian version (at time of writing: Debian 11). Our custom roles do mostly rely on this.
 
 ## Prerequisites on to-be-provisioned machine
 
@@ -13,7 +13,7 @@ In this file, you will find some tutorials describing common workflows for using
 
 - this repository cloned
 - python3 installation
-- ansible installation (`pip install -r requirements.txt`)
+- Ansible installation (`pip install -r requirements.txt`)
 
 We use ansible-vaultpass for storing secrets encrypted in this repository. For provisioning machines with this repository, you need a password in the `.vaultpass` files for decrypting the variables.
 
@@ -40,15 +40,15 @@ After that, you can start the first provision stage with `ansible-playbook play.
 
 ### 2. Provision machine for its actual purpose
 
-After that, just run the rest of the playbooks for the given machine, accessing it with your own ssh login: `ansible-playbook play.yml --limit=testmachine`. Don't forget to add `--user testuser` if the name of your local user differs from the remote user.
+After that, just run the rest of the playbooks for the given machine, accessing it with your own SSH login: `ansible-playbook play.yml --limit=testmachine`. Don't forget to add `--user testuser` if the name of your local user differs from the remote user.
 
 ## Provision a machine to buildbotworker
 
-For adding your buildbotworker machine to this repo, we need to follow three steps. The machine does not need to be reachable from the internet. It will connect itself to the buildbot, so it only needs basic access to the internet.
+For adding your buildbotworker machine to this repository, we need to follow three steps. The machine does not need to be reachable from the internet. It will connect itself to the buildbot, so it only needs basic access to the internet.
 
-### Get your machine known to ansible
+### Get your machine known to Ansible
 
-To get your machine known to ansible, add it to the `hosts`-file at `inventory/hosts`.
+To get your machine known to Ansible, add it to the `hosts`-file at `inventory/hosts`.
 
 ```ini
 [buildbotworker]