diff --git a/README.md b/README.md
index 6d0e0d7..26a645c 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ For proper start commands, especially https and security related, see the [Conne
The first step is to connect the application to a Kafka server and the schema registry. In the settings screen the normal Kafka properties file data can be pasted and saved. By default the file location is `/apps/rulesservice/settings/kafka.properties` from the container's point of view.
-
+
```
@@ -92,7 +92,7 @@ To simplify entering rules, sample values can be entered and the result be recal
Once a rule file is complete, it must be copied from the `inactive` to the `active` directory. The button `Activate` does that. The reason for this two staged approach is to allow users saving intermediate definitions without impacting the currently running service.
-
+
### Step 3: Topics
@@ -102,7 +102,7 @@ Scaling is achieved by increasing the number of KStream instances used for this
The screen also allows to copy the rule files being used into the active folder to simplify activating each from the rule file dialog.
-
+
### Result
@@ -115,7 +115,7 @@ Querying this data allows detailed reporting which records were processed by wha
The exact Avro schema field definition can be found [here](docs/audit-schema.md)
-
+
### Sample files
@@ -126,7 +126,7 @@ The found messages are streamed in chunks into the screen and can be saved, eith
The files are stored in the directory `/apps/rulesservice/definitions//sampledata/`.
If no file name is specified, the name will be `partition__offset_.json`.
-
+
diff --git a/pom.xml b/pom.xml
index d7e2289..f68ff51 100644
--- a/pom.xml
+++ b/pom.xml
@@ -8,7 +8,7 @@
war
UTF-8
- 0.9.28
+ 0.9.29
2.24.1
3.8.0
3.1.8