diff --git a/CHANGELOG.md b/CHANGELOG.md
index 00c1e592ba06f8d0c0ed020c701070c59ee6f145..1c2c3ce3c4ed33fab35494be1459b4d8959126d4 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,5 @@
 # Change Log
+
 All notable changes to this project will be documented in this file.
 
 
@@ -8,11 +9,13 @@ All notable changes to this project will be documented in this file.
 ## [1.4] - 2022-03-28
 
 ### Added
+
 - defined `\fronmatter`, `\mainmatter` and `\backmatter` for HsH-report class
 - included the caption package to fix #6
 
 ### Fixes
-- references now get point to the to of floats, not to the captions position (#6)
+
+- references now get point to the top of floats, not to the captions position (#6)
 
 
 ## [1.3] - 2022-03-07
@@ -31,10 +34,12 @@ All notable changes to this project will be documented in this file.
 ## [1.2] - 2021-10-24
 
 ### Fixed
+
 - Issues that came with the Kernel update from 01.06.2021 are fixed (#2, #3, #4)
 - typos
 
 ### Added
+
 - defined checklist environment via enumitem-package in `config.tex`
 - added required package for enum item
 
@@ -45,29 +50,34 @@ This version provides mostly minor fixed and upgrades.
 **IMPORTANT:** the `personal.tex` has been removed
 
 ### Added
- -  dtx installer file. All class files can be generated from this file. This removes code duplications and allows for more easy maintenance as well as
- 	deployment. This file will only be available on a separate branch and not be part of the master branch.
+
+- Dtx installer file. All class files can be generated from this file. This removes code duplications and allows for more easy maintenance as well as
+  deployment. This file will only be available on a separate branch and not be part of the master branch.
 
 ### Changed
- - Makefile has been reworked. Should now be more stable and easier to understand
- - Title page as been improved. You can now align the standard title page as you prefer
- - the declaration of authorship now uses the proper babel interface for localization
- - Licence is now LPPL
+
+- Makefile has been reworked. Should now be more stable and easier to understand
+- Title page as been improved. You can now align the standard title page as you prefer
+- the declaration of authorship now uses the proper babel interface for localization
+- Licence is now LPPL
 
 ### Removed
- - `personal.tex` has been removed. It pretty much not used anyway. All contents have been moved to the project files preamble.
+
+- `personal.tex` has been removed. It pretty much not used anyway. All contents have been moved to the project files preamble.
 
 
 ## [1.0] - 2021-03-31
+
 Initial Version. Official first release
 
 ### Added
- - HsH-article class
- - HsH-report class
- - HsH-standalone class
- - `config.tex` file
- - `personal.tex` file
- - folder structure, with readme files for every folder
- - empty project file
- - makefile
- - example on the example branch
+
+- HsH-article class
+- HsH-report class
+- HsH-standalone class
+- `config.tex` file
+- `personal.tex` file
+- folder structure, with readme files for every folder
+- empty project file
+- makefile
+- example on the example branch
diff --git a/README.md b/README.md
index fe9eb8b9938fe28cc8f4be3e722d878cdf49cc80..369ccdfd97e1abea4ac3ab619ca7a86f16de5237 100644
--- a/README.md
+++ b/README.md
@@ -3,20 +3,20 @@
 This is a template designed to ease the workflow when writing documents for the Hochschule Hannover. It is intended to be used in all sophisticated
 works, from lab-reports to master’s thesis's.  
 The project provides custom document-classes caring the `HsH-` prefix as well as support files. These classes extend the well known KOMA-Script
-classes and customize them with specific configurations, presets and provide commonly needed features.  
+classes and customize them with specific configurations, presets and provide commonly needed features.
 
-**Provided classes are:**  
+**Provided classes are:**
 
-	HsH-article
-	HsH-report
-	HsH-book (planed)
-	HsH-standalone
+- `HsH-article`
+- `HsH-report`
+- `HsH-book` (planed)
+- `HsH-standalone`
 
 [![Version](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/badges/release.svg)](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/releases)  
 
 
 
-# Quick start guide:
+# Quick start guide
 
 
 ## Recommended software
@@ -25,9 +25,9 @@ As a Tex-Distribution, [MiKTeX is recommended](https://miktex.org/), TexLive sho
 To edit the `.tex` files, you could use any text editor, but I personally like [Visual Studio Code](https://code.visualstudio.com/) the most, which
 can also be used for pretty much all other programming languages. Use the [Latex Workshop extension](https://marketplace.visualstudio.com/items?itemName=James-Yu.latex-workshop),
 and you can steal my config file from [here](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/snippets/111).  
-If you prefer a Tex-only editor, I used [Texmaker](https://www.xm1math.net/texmaker/) in the past, and it's also very good.  
+If you prefer a Tex-only editor, I used [Texmaker](https://www.xm1math.net/texmaker/) in the past, and it's also very good.
 
-If you want to use citations in your work, you should get familiar with the `biblatex` package and include it in your project. The classes set it up 
+If you want to use citations in your work, you should get familiar with the `biblatex` package and include it in your project. The classes set it up
 to use `biber` as the backend, which is more modern and has more features than the usual `bibtex`, but you will need to set you editor up to also use
 this.
 
@@ -42,12 +42,12 @@ To get you started, there is a working example Project on the example branch tha
 
 To get started, create a new folder for your project somewhere on your PC and create your `.tex` file. Copy the class file (`.cls`) you want to use
 and the `HsH-logo.pdf` from the src folder to your project folder. You can optionally copy the `config.tex`, but you can also configure everything in
-your preamble. 
+your preamble.
 
 
 ## Using a proper subfolder structure
 
-The projects also provides a recommendation for a subfolder structure, to keep things organized. You can 
+The projects also provides a recommendation for a subfolder structure, to keep things organized. You can
 [download the .zip-Archive](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/archive/master/latex-template-hsh-master.zip)
 and unpack it or clone the repository via `git clone https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh.git`.
 This has the downside of storing class files and other needed files in the _./src_ folder, which means it needs to be added to the path searched when
@@ -56,7 +56,7 @@ The provided Makefile demonstrates how to run a successful build, you might want
 
 
 
-# Documentation:
+# Documentation
 
 
 ## The different classes
@@ -65,6 +65,7 @@ This project provides a set of additional classes designed for use in the Hochsc
 classes](https://ctan.org/pkg/koma-script) by adding styling and providing some additional commands. The provided classes are:
 
 ### `HsH-article`
+
 Based on the `scrartcl` this class is designed for quick and compact documents. It does not have chapters and therefore never breaks to a new page on
 its own. This class is useful for writing lab-protocols and alike.
 
@@ -87,22 +88,22 @@ underlying subclass and processed there. So you can use everything from the corr
 
 ### Default Options
 If you don't define something different, the classes set your project up to use the following options:
- - `fontsize=11pt` the font size
- - `a4paper` the paper size
- - `ngerman` the document language
- - `sans` the font type (Sans Serif)
- - `margin=0.25cm` ONLY for `hsh-standalone`, adds an empty margin around all pages
+- `fontsize=11pt` the font size
+- `a4paper` the paper size
+- `ngerman` the document language
+- `sans` the font type (Sans Serif)
+- `margin=0.25cm` ONLY for `hsh-standalone`, adds an empty margin around all pages
 
 ### List of all options
- - `german`, `ngerman` These two options are aliases. They switch the document language to German, which affects autogenerated naming as well as the 
-   formatting of numbers. This is implemented by using an internal if switch, called `\@german`, which is set to true.
- - `english` This option is the opposite of the previous ones. It sets the document language to English by setting `\@german` to false.
- - `f1` - `f5` To use the correct logo of a certain faculty, you can define your faculty with these options. If none of these are present, a generic
-   grey logo is chosen.  
-   The different logos correspond to different pages of the `HsH-Logo.pdf`, so you could change this file and therefore the used logo as long as you 
-   keep the page numbering consistent with the original.
- - `sans` This option sets the font family to Sans Serif.
- - `roman` The opposite of `sans`, sets a roman/serif font.
+- `german`, `ngerman` These two options are aliases. They switch the document language to German, which affects autogenerated naming as well as the
+  formatting of numbers. This is implemented by using an internal if switch, called `\@german`, which is set to true.
+- `english` This option is the opposite of the previous ones. It sets the document language to English by setting `\@german` to false.
+- `f1` - `f5` To use the correct logo of a certain faculty, you can define your faculty with these options. If none of these are present, a generic
+  grey logo is chosen.  
+  The different logos correspond to different pages of the `HsH-Logo.pdf`, so you could change this file and therefore the used logo as long as you
+  keep the page numbering consistent with the original.
+- `sans` This option sets the font family to Sans Serif.
+- `roman` The opposite of `sans`, sets a roman/serif font.
 
 All remaining options are passed along to the respective subclasses and processed there. This means, that you can use all the options described in
 their respec­tive documentations.
@@ -114,37 +115,37 @@ their respec­tive documentations.
 These Packages are automatically included by the class file. These are either important for provided functions or so generally useful that they are
 used in pretty much every project anyway.
 
- - `inputenc` for input encoding, all input files (.tex files, etc.) are expected to be UTF8 encoded
- - `fontenc` for output encoding, set to T1, if you use non-Latin characters (like Cyrillic, etc.) you need to add that
- - `lmodern` is a font
- - `babel` for German typesetting
- - `geometry` for margins and stuff, (will probably be removed at some point)
- - `scrlayer-scrpage` KOMA package for headers and footers
- - `scrhack` KOMA package for compatibility with listings
- - `pgffor` allows for the use of for-loops (internal)
- - `graphicx` for importing images
- - `hyperref` for references and links
- - `caption` to customise captions and make references point to the begining of the floats
- - `bookmark` for bookmarking
- - `amsmath` for a lot of general purpose maths features
- - `csquotes` makes quotations easier
- - `ziffer` is only included when the German document option is provided, sets comma as decimal
+- `inputenc` for input encoding, all input files (.tex files, etc.) are expected to be UTF8 encoded
+- `fontenc` for output encoding, set to T1, if you use non-Latin characters (like Cyrillic, etc.) you need to add that
+- `lmodern` is a font
+- `babel` for German typesetting
+- `geometry` for margins and stuff, (will probably be removed at some point)
+- `scrlayer-scrpage` KOMA package for headers and footers
+- `scrhack` KOMA package for compatibility with listings
+- `pgffor` allows for the use of for-loops (internal)
+- `graphicx` for importing images
+- `hyperref` for references and links
+- `caption` to customize captions and make references point to the beginning of the floats
+- `bookmark` for bookmarking
+- `amsmath` for a lot of general purpose maths features
+- `csquotes` makes quotations easier
+- `ziffer` is only included when the German document option is provided, sets comma as decimal
 
 ### Recommended packages
 These packages are recommended, but not included automatically to save compile time when they are not needed. If you want to use one of them, include
 it in your preamble.
 
- - `bibtex` a package for citation and source management. Keep in mind, that there are multiple backends and `biber` is configured, if you want to
-   continue using the old backend, type `\usepackage[backend=bibtex]{biblatex}` in your preamble.  
- - `subfigure` one of multiple packages, that allows you to put multiple images into a figure
- - `siunitx` is an amazing tool for Units
- - `csvsimple` allows you to import CSV files, which is handy if you want to display measurements
- - `listings` allows you to include format code snippets
- - `pgfplots` is a great maths engine, which can create amazing plots
- - `tikz` is already included with pgfplots, but is also a nice standalone package
- - `circuitikz` expands the previous packages with macros for circuit creation
- - `standalone` is a package, that allows you to create simple images from sub-texfiles. This can save a lot of compile time, especially with tikz and
-   alike.
+- `bibtex` a package for citation and source management. Keep in mind, that there are multiple backends and `biber` is configured, if you want to
+  continue using the old backend, type `\usepackage[backend=bibtex]{biblatex}` in your preamble.
+- `subfigure` one of multiple packages, that allows you to put multiple images into a figure
+- `siunitx` is an amazing tool for Units
+- `csvsimple` allows you to import CSV files, which is handy if you want to display measurements
+- `listings` allows you to include format code snippets
+- `pgfplots` is a great maths engine, which can create amazing plots
+- `tikz` is already included with pgfplots, but is also a nice standalone package
+- `circuitikz` expands the previous packages with macros for circuit creation
+- `standalone` is a package, that allows you to create simple images from sub-texfiles. This can save a lot of compile time, especially with tikz and
+  alike.
 
 There's more...
 
@@ -158,17 +159,17 @@ This command is not new, but changed. It creates a title-page fitting for most u
 using on of the three options `r`, `c` or `l` for right aligned, centred or left aligned.  
 You can use the following macros to define the different information presented on the title-page:
 
- - `\author` as usual, this is where you put your name. But you can also input a comma-seperated list, if more than one person has written in this file.
- - `\matrikelnr` a new macro for your matriculation number. This is optional, but will be put next to your name if present. You can input again a
-   comma-seperated list, if more than one author is present.
- - `\titlehead` is for a small line left of the logo. This is usually the department or division. May be empty
- - `\subject` is for a broad description of what your file is. "Laborbericht" for example. Can be empty.
- - `\title` is quite obvious. The only one that must be present.
- - `\subtitle` is a smaller second line under the title. Can be empty
- - `\date` is the date of your project. You can use a custom one, but if you don't set it, the current date at compile time will be used.
- - `\professor` a new macro do define your professors name, if needed.
- - `\keywords` will not be printed on the title-page, but rather on the end of the abstract, if you define some. They will also be but into the PDFs
-   metadata.
+- `\author` as usual, this is where you put your name. But you can also input a comma-seperated list, if more than one person has written in this file.
+- `\matrikelnr` a new macro for your matriculation number. This is optional, but will be put next to your name if present. You can input again a
+  comma-seperated list, if more than one author is present.
+- `\titlehead` is for a small line left of the logo. This is usually the department or division. May be empty
+- `\subject` is for a broad description of what your file is. "Laborbericht" for example. Can be empty.
+- `\title` is quite obvious. The only one that must be present.
+- `\subtitle` is a smaller second line under the title. Can be empty
+- `\date` is the date of your project. You can use a custom one, but if you don't set it, the current date at compile time will be used.
+- `\professor` a new macro do define your professors name, if needed.
+- `\keywords` will not be printed on the title-page, but rather on the end of the abstract, if you define some. They will also be but into the PDFs
+  metadata.
 
 ### `\declarationAuthorship`
 This macro will typeset a declaration of authorship, which is needed for most academic works. It will be produced at the bottom of the current page,
@@ -176,28 +177,30 @@ separated by a horizontal line.
 The macro is defined in German and English and will automatically match your document language.
 
 ### `\abs`
-A helpful macro for absolute values. It can be used in maths mode and will put vertical lines around its content, that match the height of the content.  
+A helpful macro for absolute values. It can be used in maths mode and will put vertical lines around its content, that match the height of the
+content.  
 This macro is only provided, meaning if another package defines it, its definition will be used.
 
 ### HsH-Logo macros
 These are more of a by-product, but they are defined, so you could use them:
- - `\HsHlogoPath` the path to an image, that is used as the logo. Given a default value by the class.
- - `\HsHlogoPage` the page of the previous file, which is used. This is changed with the `f1`-`f5` options.
- - `\includeHsHlogohere[width]` this macro produces the logo using the previous macros. The width can optionally be provided.
+- `\HsHlogoPath` the path to an image, that is used as the logo. Given a default value by the class.
+- `\HsHlogoPage` the page of the previous file, which is used. This is changed with the `f1`-`f5` options.
+- `\includeHsHlogohere[width]` this macro produces the logo using the previous macros. The width can optionally be provided.
 
 
 
 # Common additions and expansions (Snippets)
 
 Sadly most Profs have widely different expectations when it comes to styling of written works. So you might find yourself having to change some
-settings. For some cases this has already been done and, to help others, uploaded in 
+settings. For some cases this has already been done and, to help others, uploaded in
 [the snippets section](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/snippets) of the project. Most of them are only visible when you
 are logged in!!  
-Also, if you create your own set of additions that are usefull for other, feel free to contact me and I will give you acces right so you can upload it there.
+Also, if you create your own set of additions that are useful for other, feel free to contact me and I will give you access right, so you can upload
+it there.
 
 
 
-# Frequently Asked Questions:
+# Frequently Asked Questions
 
 
 ## What is the `config.tex`?
@@ -207,7 +210,7 @@ well as allowing easy reuse of configs for other projects.
 
 The provided classes automatically check for this file and use it, if it is present. But they are completely optional, so you can just ditch them if
 you want to. Keep in mind that the `config.tex` will be included right before the `\begin{document}`, so it overrides all settings you may have put
-in your preamble.  
+in your preamble.
 
 The `config.tex` is intended for configurations. For example new- or redefinitions of commands should be put here. Also, packages-specific configs are
 loaded here. The `\@ifpackageloaded{pakagename}{true}{false}` macro allows to check for the existence of a package, so that you can reuse config files,
@@ -230,15 +233,17 @@ For building from sub folders, just add a second `-include-directory=../src` to
 
 ### Using Texmaker and MiKTeX
 As stated above, you just need to extend your Latex-call with the needed include path.  
-To do this, go to *Options → config Texmaker → Commands*  
-change the pdflatex command to: 
+To do this, go to _Options → config Texmaker → Commands_  
+change the pdflatex command to:
 
 ```bash
 pdflatex -synctex=1 -interaction=nonstopmode -include-directory=./src -include-directory=../src %.tex
 ```
 
 ### Using VS Code with LaTeX Workshop
-In VS Code you can configure your launch to set environment variables. Just edit your `settings.json`, so that your pdflatex tool contains a `env:` (add it, if it isn't there yet). If you use the template below, you will also get some additional nice configurations. See also [here](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/snippets/111) for some additional configs.
+In VS Code you can configure your launch to set environment variables. Just edit your `settings.json`, so that your pdflatex tool contains a `env:`
+(add it, if it isn't there yet). If you use the template below, you will also get some additional nice configurations. See also
+[here](https://lab.it.hs-hannover.de/qxx-tul-u1/latex-template-hsh/-/snippets/111) for some additional configs.
 
 ```json
 "latex-workshop.latex.tools": [
@@ -318,4 +323,4 @@ or use `\usepackage[backend=bibtex]{biblatex}` in your preamble to keep using Bi
 The classes by default set all sub scripts upright ("steil" in German), because this is required in Germany in most cases.  
 You can deactivate this permanently with `\normalsubscripts` and reactivate it with `\upsubscripts`.  
 If you want to change it for a single use, you can use the original Tex Macro `\sb{}` instead of the `_` to get the original behaviour.  
-DO NOT use `_\math..{}`! This would be a nested font change and lead to unexpected results. `\sb{\math..{}}` is possible. 
+DO NOT use `_\math..{}`! This would be a nested font change and lead to unexpected results. `\sb{\math..{}}` is possible.