diff --git a/services/eventhistory/README.md b/services/eventhistory/README.md
index 46390a2a4b1..bb58114c65b 100644
--- a/services/eventhistory/README.md
+++ b/services/eventhistory/README.md
@@ -20,7 +20,7 @@ The `eventhistory` service stores each consumed event via the configured store i
   -   `nats-js`: Stores data using key-value-store feature of [nats jetstream](https://docs.nats.io/nats-concepts/jetstream/key-value-store)
   -   `noop`: Stores nothing. Useful for testing. Not recommended in productive enviroments.
 
-1.   Note that in-memory stores are by nature not reboot persistant.
+1.  Note that in-memory stores are by nature not reboot persistent.
 2.  Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type `in-memory`. These settings are blank by default which means that the standard settings of the configured store applies.
 3.  Events stay in the store for 2 weeks by default. Use `EVENTHISTORY_RECORD_EXPIRY` to adjust this value.