diff --git a/README.md b/README.md
index 64882d7..65dbe88 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@
 
 We chose this specific stack because all of our team members have previously
 worked with this combination of Angular/Django and there is a lot of
-documentation for it online. 
+documentation for it online.
 We chose sqlite3 as persistence layer because it comes out of the box with django. Django
 also provides a built-in ORM mapper. Our db schema is very simple, sqlite3 handles it well.
 
@@ -38,18 +38,34 @@ the database is persisted at the client's filesystem.
 
 The docker images are available at:
 
-* [waecm-2021-group-04-bsp2-fe](https://hub.docker.com/r/pfingstfrosch/waecm-2021-group-04-bsp-2-fe)
-    * sha256 digest: 2d6526c871285f81dee714f41c41750e6e9c4e124cdc78f69ecd17036f620399
-* [waecm-2021-group-04-bsp2-be](https://hub.docker.com/r/pfingstfrosch/waecm-2021-group-04-bsp-2-be)
-    * sha256 digest: fe0b490a7ad5546371a8a709c9e4f80985326c9a27dddfeef6179f89affc9105
+* [waecm-2021-group-04-bsp2-fe](https://hub.docker.com/r/pfingstfrosch/waecm-2021-group-04-bsp-3-fe)
+    * sha256 digest: 68278575a559e2c28f3f68646985175c268c47a7401da2a3fac67d7a5e994727
+* [waecm-2021-group-04-bsp2-be](https://hub.docker.com/r/pfingstfrosch/waecm-2021-group-04-bsp-3-be)
+    * sha256 digest: 90befdf477d700c7c25efde38192cff2cf457207b27c01141c466444fc03e2e3
 
 ## CI
 Look at git-lab project https://gitlab.com/Pfingstfrosch/waecm-g4-CI for CI execution.
 This repository is mirrored to the CI repo, where the pipeline is executed.
 
 ## Cookie Banner Custom Element
-For evaluation purposes the original code (angular project) for the custom element is presented in this repo in branch https://student.inso.tuwien.ac.at/01527193/waecm-g4/-/tree/custom-cookie-banner/frontend
-The custom element was developed in angular because it was convenient to set up a new project, develop the component (with all the benefits of angular), and export it.
-Our Custom Element has additional optional attributes [statistik]=(bool) and [marketing]=(bool) to initialize the checkboxes (e.g. if one wants to show the user what he selected earlier).
-The Element is implemented in our Landing Component (that contains the angular routing component), therefore the banner is controlled at a single point in the app.
-A Angular Service makes the Banner Selection available within the whole app if necessary.
+For evaluation purposes the original code (angular project) for the custom
+element is presented in this repo in
+[this](https://student.inso.tuwien.ac.at/01527193/waecm-g4/-/tree/custom-cookie-banner/frontend)
+branch. The custom element was developed in angular because it was convenient to
+set up a new project, develop the component (with all the benefits of angular),
+and export it. Our Custom Element has additional optional attributes
+[statistik]=(bool) and [marketing]=(bool) to initialize the checkboxes (e.g. if
+one wants to show the user what he selected earlier). The Element is
+implemented in our Landing Component (that contains the angular routing
+component), therefore the banner is controlled at a single point in the app.  A
+Angular Service makes the Banner Selection available within the whole app if
+necessary.
+
+## Location of Tests
+
+The first tested component is our feed creation component in
+`frontend/src/app/component/einstellungen/editieren/`. The file with the tests
+is in the same folder under the name `editieren.component.spec.ts`.
+
+The second component is in the folder `frontend/src/app/component/tweets` and
+the tests in `tweets.component.spec.ts`.