diff --git a/etl/README.md b/etl/README.md
index c26a7ccc2..9a97c2706 100644
--- a/etl/README.md
+++ b/etl/README.md
@@ -152,7 +152,7 @@ To avoid that, the ETL framework allows storing progress by setting `OnLoadCommi
 
 Then we can use this data to know the progress the ETL transformation made.
 
-You can also specify `ExtractStartKey` and `ExtractEndKey` to limit the nubmer
+You can also specify `ExtractStartKey` and `ExtractEndKey` to limit the number
 of items transformed.
 
 ## Ways to work with ETL framework
diff --git a/kv/Readme.md b/kv/Readme.md
index 23799ec3d..cba4f0538 100644
--- a/kv/Readme.md
+++ b/kv/Readme.md
@@ -6,7 +6,7 @@ Words "KV" and "DB" have special meaning here:
 - DB - object-oriented-style API to access data: Get/Put/Delete/WalkOverTable/MultiPut, managing transactions
   internally.
 
-So, DB abstraction fits 95% times and leads to more maintainable code - because it's looks stateless.
+So, DB abstraction fits 95% times and leads to more maintainable code - because it looks stateless.
 
 About "key-value-style": Modern key-value databases don't provide Get/Put/Delete methods,
 because it's very hard-drive-unfriendly - it pushes developers do random-disk-access which
@@ -57,7 +57,7 @@ kv_temporal.go
 - MultipleDatabases, Customization: `NewMDBX().Path(path).WithBucketsConfig(config).Open()`
 
 
-- 1 Transaction object can be used only withing 1 goroutine.
+- 1 Transaction object can be used only within 1 goroutine.
 - Only 1 write transaction can be active at a time (other will wait).
 - Unlimited read transactions can be active concurrently (not blocked by write transaction).