diff --git a/README.md b/README.md
index 4908be81b3b8c39ce838adb65c0b1a38cf178ed1..48bbd0acfc66cb24de029a3109fec7a8275e1a6a 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
 # [Ansible](https://docs.ansible.com/ansible/index.html) repository for LAS/CS NSQ computer
-You need to have access to this repository (viz you need to add your public ssh-key (`ssh-keygen`) to your profile here.
+You need to have access to this repository (you need to add your public ssh-key (`ssh-keygen`) to your profile here).
 Then you can clone the git repository to work on in locally.
 `git clone git@git.scc.kit.edu:las/ansible.git`
 
@@ -10,8 +10,14 @@ Also create a new file which is named
 after your [fully-qualified-domain-name](https://de.wikipedia.org/wiki/Domain_(Internet)#Fully_Qualified_Domain_Name_.28FQDN.29}) (FQDN) in the `host_vars` directory including a [yaml](https://docs.ansible.com/ansible/YAMLSyntax.html) list with some host specific configuration variables, e. g. copy another similar host and adjust it.
 These files do not have the `.yml` extension and do not start with `---`
 Then create a file named after your FQDN with the extension ".yml" in the main directory of ansible which contains includes all the roles one want to run. This step needs root priviledges and therefore makes only sense for the first installation of a computer.
-* install ansible and some dependencies (`dnf install ansible git python2-dnf libselinux-python`)
-* run [ansible-pull](https://docs.ansible.com/ansible/playbooks_intro.html#ansible-pull) (`ansible-pull -K -U git@git.scc.kit.edu:las/ansible.git playbook_name.yml`)
+* install ansible and some dependencies: 
+  ```
+dnf install ansible git python2-dnf libselinux-python
+```
+* run [ansible-pull](https://docs.ansible.com/ansible/playbooks_intro.html#ansible-pull):
+  ```
+ansible-pull -K -U git@git.scc.kit.edu:las/ansible.git playbook_name.yml
+```
   * If you only want some parts of the roles to be run, you can use the option `-t TAGNAME` to run only those tasks with the given tag.
 
 ### Ask for new software
@@ -44,7 +50,7 @@ Open an issue in the GitLab issue tracker with the label: softwarerequest
 
 After installing Opera via ansible you must confirm the license agreement at first start and go to "Licensing -> Set License Path" and switch to `Other computer(s)` and fill in `@129.13.108.100`.
 
-# Develope new roles, extend or modify existing ones and update roles for new software
+# Develop new roles, extend or modify existing ones and update roles for new software
 
 ## Branches
 All roles in the master branch should work and should not brake on any of our systems (desktop, server, simulation, notebooks). The `site.yml` should always be runnable and include all roles that are stable and not explicitly for setup purposes only.
@@ -52,8 +58,3 @@ All roles in the master branch should work and should not brake on any of our sy
 For developement and testing you should use development branches like `dev-latex`.
 
 You can check the syntax of the files by running `ansible-playbook --check-syntax filename.yml` (or by using the pre-commit-hook from the Snipplets.
-
-## TODO
-* epics
-* elegant (blas: gescheit die key-verwaltung lösen)
-* dhcpd