diff --git a/docs/components/receive.md b/docs/components/receive.md
index 5f81710389..4b06777f57 100644
--- a/docs/components/receive.md
+++ b/docs/components/receive.md
@@ -140,7 +140,7 @@ write:
         samples_limit: 500
 ```
 
-**IMPORTANT**: this feature is experimental and a work-in-progres. It might change in the near future, i.e. configuration might move to a file (to allow easy configuration of different request limits per tenant) or its structure could change.
+**IMPORTANT**: this feature is experimental and a work-in-progress. It might change in the near future, i.e. configuration might move to a file (to allow easy configuration of different request limits per tenant) or its structure could change.
 
 ### Remote write request limits
 
diff --git a/docs/components/store.md b/docs/components/store.md
index 7c08800394..1460d142c3 100644
--- a/docs/components/store.md
+++ b/docs/components/store.md
@@ -413,7 +413,7 @@ Following options are used for metadata caching (meta.json files, deletion mark
 - `metafile_content_ttl`: how long to cache content of meta.json and deletion mark files.
 - `metafile_max_size`: maximum size of cached meta.json and deletion mark file. Larger files are not cached.
 
-The yml structure for setting the in memory cache configs for caching bucket is the same as the [in-memory index cache](#in-memory-index-cache) and all the options to configure Caching Buket mentioned above can be used.
+The yml structure for setting the in memory cache configs for caching bucket is the same as the [in-memory index cache](#in-memory-index-cache) and all the options to configure Caching Bucket mentioned above can be used.
 
 In addition to the same cache backends memcached/in-memory/redis, caching bucket supports another type of backend.
 
diff --git a/docs/governance.md b/docs/governance.md
index 3731f24d6c..801be3361c 100644
--- a/docs/governance.md
+++ b/docs/governance.md
@@ -157,7 +157,7 @@ Should the decision be in favor, your new membership will also be announced on t
 
 As a team member, propose the new project on the [Thanos GitHub Issue](https://github.com/thanos-io/thanos/issues). However, currently to maintain project in our organization you have to become Thanos Maintainers.
 
-All are encourage to start their own project related to Thanos. Thanos team is happy to link to your poject inappropriate page e.g https://thanos.io/tip/thanos/integrations.md/
+All are encourage to start their own project related to Thanos. Thanos team is happy to link to your project inappropriate page e.g https://thanos.io/tip/thanos/integrations.md/
 
 ### How do I remove a Maintainer or Triage member?
 
diff --git a/docs/proposals-accepted/202206-active-series-limiting-hashring.md b/docs/proposals-accepted/202206-active-series-limiting-hashring.md
index ae215e0bb6..8d88cbb339 100644
--- a/docs/proposals-accepted/202206-active-series-limiting-hashring.md
+++ b/docs/proposals-accepted/202206-active-series-limiting-hashring.md
@@ -40,7 +40,7 @@ We could scale horizontally automatically during such increased load (once we im
 
 ## 6 Non-Goals
 
-* [Request-based limiting](https://github.com/thanos-io/thanos/issues/5404), i.e, number of samples in a remote wite request
+* [Request-based limiting](https://github.com/thanos-io/thanos/issues/5404), i.e, number of samples in a remote write request
 * Per-replica-tenant limiting which is already being discussed in this [PR](https://github.com/thanos-io/thanos/pull/5333)
 * Using [consistent hashing](https://github.com/thanos-io/thanos/issues/4972) implementation in Receive to make it easily scalable