diff --git a/frontend/README.md b/frontend/README.md
index 4c7210da79..8dfce7e6d2 100644
--- a/frontend/README.md
+++ b/frontend/README.md
@@ -12,7 +12,7 @@ $ cd frontend
 $ ./gradlew -p frontend clean assemble
 ```
 
-And you can build and test the front by running
+And you can build and test the frontend by running
 
 ```sh
 $ cd frontend
@@ -21,6 +21,14 @@ $ ./gradlew build
 
 You will find a jar file in frontend/server/build/libs file.
 
+To continuously test your frontend changes during development (e.g. through out pytest integration tests in test/pytest) without continuously reinstalling TS you can create a symbolic link (ln -s) from ts/frontend/model-server.jar to frontend/server/build/libs/server-1.0.jar. That way you changes get picked up (after calling `./gradlew -p frontend clean assemble`) when you start TS.
+
+When you create a PR with your changes it can happen that you see a formatting error during the CI testing.
+To fix the format simply run this command and commit the changes:
+```sh
+$ cd frontend
+$ ./gradlew format
+```
 ### Starting frontend
 
 Frontend web server using a configuration file to control the behavior of the frontend web server.
diff --git a/ts_scripts/spellcheck_conf/wordlist.txt b/ts_scripts/spellcheck_conf/wordlist.txt
index ff2a8bb2e9..fad4e8b724 100644
--- a/ts_scripts/spellcheck_conf/wordlist.txt
+++ b/ts_scripts/spellcheck_conf/wordlist.txt
@@ -1294,3 +1294,4 @@ StableDiffusionXL
 photorealistic
 miniconda
 torchaudio
+ln