diff --git a/nats-concepts/jetstream/key-value-store/kv_walkthrough.md b/nats-concepts/jetstream/key-value-store/kv_walkthrough.md
index 45c4030b..30b52b8c 100644
--- a/nats-concepts/jetstream/key-value-store/kv_walkthrough.md
+++ b/nats-concepts/jetstream/key-value-store/kv_walkthrough.md
@@ -106,7 +106,7 @@ It is harmless to delete a non-existent key (check this!!).
 
 K/V Stores can also be used in concurrent design patterns, such as semaphores, by using atomic 'create' and 'update' operations.
 
-E.g. a client wanting exclusive use of a file can lock it by creating a key, whose value is the file name, with `create` and deleting this key after completing use of that file. A client can increase the reslience against failure by using a timeout for the `bucket` containing this key. The client can use `update` with a revision number to keep the `bucket` alive.
+E.g. a client wanting exclusive use of a file can lock it by creating a key, whose value is the file name, with `create` and deleting this key after completing use of that file. A client can increase the resilience against failure by using a timeout for the `bucket` containing this key. The client can use `update` with a revision number to keep the `bucket` alive.
 
 Updates can also be used for more fine-grained concurrency control, sometimes known as `optimistic locking`, where multiple clients can try a task, but only one can successfully complete it.