From 7fdaf426060852a2acff69cb0d27ba6e76fd47c3 Mon Sep 17 00:00:00 2001
From: Harsh Pratap Singh <119954739+harsh-ps-2003@users.noreply.github.com>
Date: Sat, 12 Aug 2023 14:20:30 +0530
Subject: [PATCH] fixing docs ci

---
 .github/ISSUE_TEMPLATE/feature-request.md     |   2 +-
 CHANGELOG.md                                  |  18 +-
 CODE_OF_CONDUCT.md                            |   4 +-
 CONTRIBUTING.md                               |  14 +-
 MAINTAINERS.md                                |   2 +-
 README.md                                     |   4 +-
 docs/blog/2022-09-08-thanos-at-medallia.md    |   6 +-
 ...6-02-lfx-mentorship-query-observability.md |   4 +-
 docs/components/compact.md                    |  64 +++----
 docs/components/query-frontend.md             |  96 +++++-----
 docs/components/query.md                      | 118 ++++++------
 docs/components/receive.md                    | 116 +++++------
 docs/components/rule.md                       | 124 ++++++------
 docs/components/sidecar.md                    |  76 ++++----
 docs/components/store.md                      |  80 ++++----
 docs/components/tools.md                      | 180 +++++++++---------
 docs/contributing/coding-style-guide.md       |   4 +-
 .../contributing/how-to-contribute-to-docs.md |   2 +-
 docs/contributing/mentorship.md               |   2 +-
 docs/design.md                                |   2 +-
 docs/getting-started.md                       |   4 +-
 docs/operating/binary-index-header.md         |   2 +-
 .../cross-cluster-tls-communication.md        |  20 +-
 docs/operating/https.md                       |   2 +-
 .../202012-deletions-object-storage.md        |   2 +-
 .../202106-automated-per-endpoint-mTLS.md     |   4 +-
 ...more-granular-query-performance-metrics.md |  10 +-
 .../202206-active-series-limiting-hashring.md |  22 +--
 .../202209-receive-tenant-external-labels.md  |   2 +-
 .../20221129-avoid-global-sort.md             |   6 +-
 .../201812-thanos-remote-receive.md           |   2 +-
 .../201912-thanos-binary-index-header.md      |   2 +-
 .../202001-thanos-query-health-handling.md    |   2 +-
 .../202003-thanos-rules-federation.md         |  22 +--
 docs/proposals-done/202005-query-logging.md   |   4 +-
 .../202005-scalable-rule-storage.md           |   2 +-
 .../202005-version-documentation.md           |   6 +-
 docs/proposals-rejected/201807-config.md      |  22 +--
 docs/quick-tutorial.md                        |  26 +--
 docs/storage.md                               |  12 +-
 examples/alerts/alerts.md                     |   6 +-
 mixin/README.md                               |  10 +-
 mixin/runbook.md                              |   4 +-
 pkg/ui/react-app/README.md                    |   8 +-
 tutorials/killercoda/README.md                |   2 +-
 tutorials/kubernetes-helm/README.md           |  10 +-
 46 files changed, 566 insertions(+), 566 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature-request.md b/.github/ISSUE_TEMPLATE/feature-request.md
index ae06a990a41..57e052308e2 100644
--- a/.github/ISSUE_TEMPLATE/feature-request.md
+++ b/.github/ISSUE_TEMPLATE/feature-request.md
@@ -33,7 +33,7 @@ assignees: ''
 
 (Write your answer here.)
 
-### Additional context
+### Additional contex
 
 <!--
   Is there anything else you can add about the proposal?
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 2e407afe62c..a88d1c87504 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -126,13 +126,13 @@ We use *breaking :warning:* to mark changes that are not backward compatible (re
 ### Fixed
 
 - [#6066](https://github.com/thanos-io/thanos/pull/6066) Tracing: fixed panic because of nil sampler
-- [#6086](https://github.com/thanos-io/thanos/pull/6086) Store Gateway: Fix store-gateway deadlock due to not close BlockSeriesClient
+- [#6086](https://github.com/thanos-io/thanos/pull/6086) Store Gateway: Fix store-gateway deadlock due to not close BlockSeriesClien
 
 ## [v0.30.1](https://github.com/thanos-io/thanos/tree/release-0.30) - 4.01.2023
 
 ### Fixed
 
-- [#6009](https://github.com/thanos-io/thanos/pull/6009) Query Frontend/Store: fix duplicate metrics registration in Redis client
+- [#6009](https://github.com/thanos-io/thanos/pull/6009) Query Frontend/Store: fix duplicate metrics registration in Redis clien
 
 ## [v0.30.0](https://github.com/thanos-io/thanos/tree/release-0.30) - 2.01.2023
 
@@ -562,11 +562,11 @@ The binaries published with this release are built with Go1.17.8 to avoid [CVE-2
 
 ### Changed
 
-- 
+-
 
 ### Removed
 
-- 
+-
 
 ## [v0.20.0](https://github.com/thanos-io/thanos/releases/tag/v0.20.0) - 2021.04.28
 
@@ -706,7 +706,7 @@ The binaries published with this release are built with Go1.17.8 to avoid [CVE-2
   - This, generally, reduces baseline memory usage of store when inactive, as well as a total number of mapped files (which is limited to 64k in some systems.
 - [#3437](https://github.com/thanos-io/thanos/pull/3437) StoreAPI: Added `hints` field to `LabelNamesResponse` and `LabelValuesResponse`. Hints in an opaque data structure that can be used to carry additional information from the store and its content is implementation specific.
   - This, generally, reduces baseline memory usage of store when inactive, as well as a total number of mapped files (which is limited to 64k in some systems.
-- [#3415](https://github.com/thanos-io/thanos/pull/3415) Tools: Added `thanos tools bucket mark` command that allows to mark given block for deletion or for no-compact
+- [#3415](https://github.com/thanos-io/thanos/pull/3415) Tools: Added `thanos tools bucket mark` command that allows to mark given block for deletion or for no-compac
 
 ### Fixed
 
@@ -804,7 +804,7 @@ Highlights:
 - [#2832](https://github.com/thanos-io/thanos/pull/2832) ui React: Add runtime and build info page
 - [#2926](https://github.com/thanos-io/thanos/pull/2926) API: Add new blocks HTTP API to serve blocks metadata. The status endpoints (`/api/v1/status/flags`, `/api/v1/status/runtimeinfo` and `/api/v1/status/buildinfo`) are now available on all components with a HTTP API.
 - [#2892](https://github.com/thanos-io/thanos/pull/2892) Receive: Receiver fails when the initial upload fails.
-- [#2865](https://github.com/thanos-io/thanos/pull/2865) ui: Migrate Thanos Ruler UI to React
+- [#2865](https://github.com/thanos-io/thanos/pull/2865) ui: Migrate Thanos Ruler UI to Reac
 - [#2964](https://github.com/thanos-io/thanos/pull/2964) Query: Add time range parameters to label APIs. Add `start` and `end` fields to Store API `LabelNamesRequest` and `LabelValuesRequest`.
 - [#2996](https://github.com/thanos-io/thanos/pull/2996) Sidecar: Add `reloader_config_apply_errors_total` metric. Add new flags `--reloader.watch-interval`, and `--reloader.retry-interval`.
 - [#2973](https://github.com/thanos-io/thanos/pull/2973) Add Thanos Query Frontend component.
@@ -1198,9 +1198,9 @@ Accepted into CNCF:
 
 - [#1248](https://github.com/thanos-io/thanos/pull/1248) Add a web UI to show the state of remote storage.
 
-- [#1217](https://github.com/thanos-io/thanos/pull/1217) Thanos Receive gained basic hashring support
+- [#1217](https://github.com/thanos-io/thanos/pull/1217) Thanos Receive gained basic hashring suppor
 
-- [#1262](https://github.com/thanos-io/thanos/pull/1262) Thanos Receive got a new metric `thanos_http_requests_total` which shows how many requests were handled by it
+- [#1262](https://github.com/thanos-io/thanos/pull/1262) Thanos Receive got a new metric `thanos_http_requests_total` which shows how many requests were handled by i
 
 - [#1243](https://github.com/thanos-io/thanos/pull/1243) Thanos Receive got an ability to forward time series data between nodes. Now you can pass the hashring configuration via `--receive.hashrings-file`; the refresh interval `--receive.hashrings-file-refresh-interval`; the name of the local node's name `--receive.local-endpoint`; and finally the header's name which is used to determine the tenant `--receive.tenant-header`.
 
@@ -1439,7 +1439,7 @@ New Store tracing span: \* `store_query_gate_ismyturn` shows how long it took fo
 - [#848](https://github.com/thanos-io/thanos/pull/848) Compact: now correctly works with time series with duplicate labels.
 - [#894](https://github.com/thanos-io/thanos/pull/894) Thanos Rule: UI now correctly shows evaluation time.
 - [#865](https://github.com/thanos-io/thanos/pull/865) Query: now properly parses DNS SRV Service Discovery.
-- [#889](https://github.com/thanos-io/thanos/pull/889) Store: added safeguard against merging posting groups segfault
+- [#889](https://github.com/thanos-io/thanos/pull/889) Store: added safeguard against merging posting groups segfaul
 - [#941](https://github.com/thanos-io/thanos/pull/941) Sidecar: added better handling of intermediate restarts.
 - [#933](https://github.com/thanos-io/thanos/pull/933) Query: Fixed 30 seconds lag of adding new store to query.
 - [#962](https://github.com/thanos-io/thanos/pull/962) Sidecar: Make config reloader file writes atomic.
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
index f87eb555a26..d0217435443 100644
--- a/CODE_OF_CONDUCT.md
+++ b/CODE_OF_CONDUCT.md
@@ -1,8 +1,8 @@
-# Thanos Community Code of Conduct
+# Thanos Community Code of Conduc
 
 Thanos follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). Additionally our team members can be contacted directly for code of conduct abuse, as described below.
 
-# Enforcement
+# Enforcemen
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team members (e.g @bwplotka, @povilasv) at [CNCF slack workspace](https://slack.cncf.io/). The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 560b1cabcb4..f0b8170dc1c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,9 +9,9 @@ First of all please follow the [CODE_OF_CONDUCT](CODE_OF_CONDUCT.md) in all your
 The philosophy of Thanos and our community borrows heavily from UNIX philosophy and the Golang programming language.
 
 * Each subcommand should do one thing and do it well.
-  * eg. Thanos query proxies incoming calls to known store API endpoints merging the result
+  * eg. Thanos query proxies incoming calls to known store API endpoints merging the resul
 * Write components that work together.
-  * e.g. blocks should be stored in native Prometheus format
+  * e.g. blocks should be stored in native Prometheus forma
 * Make it easy to read, write, and run components.
   * e.g. reduce complexity in system design and implementation
 
@@ -60,7 +60,7 @@ However, when discussing these components in a more general manner we use the `a
 * Documentation
 * Code comments
 
-## Development
+## Developmen
 
 The following section explains various suggestions and procedures to note during development of Thanos.
 
@@ -128,9 +128,9 @@ Start your development with forking `thanos-io/thanos.git` . Here are sample ste
 $ GOPATH=$(go env GOPATH)
 $ mkdir -p $GOPATH/src/github.com/thanos-io
 $ cd $GOPATH/src/github.com/thanos-io
-$ git clone https://github.com/<your_github_id>/thanos.git
+$ git clone https://github.com/<your_github_id>/thanos.gi
 $ cd thanos
-$ git remote add upstream https://github.com/thanos-io/thanos.git
+$ git remote add upstream https://github.com/thanos-io/thanos.gi
 $ git remote update
 $ git merge upstream/main
 $ make build
@@ -186,7 +186,7 @@ It is a good practice to keep your branch updated by rebasing your branch to mai
 * If you feel like your PR is waiting too long for a review, feel free to ping the [`#thanos-dev`](https://slack.cncf.io/) channel on our slack for a review!
 * If you are a new contributor with no write access, you can tag in the respective maintainer for the changes, but be patient enough for the reviews. *Remember, good things take time :)*
 
-### Dependency management
+### Dependency managemen
 
 The Thanos project uses [Go modules](https://golang.org/cmd/go/#hdr-Modules__module_versions__and_more) to manage dependencies on external packages. This requires a working Go environment with version 1.11 or greater and git installed.
 
@@ -205,7 +205,7 @@ Tidy up the `go.mod` and `go.sum` files:
 ```bash
 make deps
 git add go.mod go.sum
-git commit
+git commi
 ```
 
 You have to commit the changes to `go.mod` and `go.sum` before submitting the pull request.
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
index e481d6c10dd..f53a7849b16 100644
--- a/MAINTAINERS.md
+++ b/MAINTAINERS.md
@@ -50,7 +50,7 @@ To improve navigating through issues and PRs we introduce various [labels](https
 
 The main labels are:
 
-#### Component
+#### Componen
 
 `component: *` and `website/docs` labels indicate an area related to the change or issue.
 
diff --git a/README.md b/README.md
index 4236e6b7e79..f9b4852b29b 100644
--- a/README.md
+++ b/README.md
@@ -62,9 +62,9 @@ Source file to copy and edit: https://docs.google.com/drawings/d/1iimTbcicKXqz0F
 The philosophy of Thanos and our community is borrowing much from UNIX philosophy and the golang programming language.
 
 * Each subcommand should do one thing and do it well
-  * e.g. thanos query proxies incoming calls to known store API endpoints merging the result
+  * e.g. thanos query proxies incoming calls to known store API endpoints merging the resul
 * Write components that work together
-  * e.g. blocks should be stored in native prometheus format
+  * e.g. blocks should be stored in native prometheus forma
 * Make it easy to read, write, and, run components
   * e.g. reduce complexity in system design and implementation
 
diff --git a/docs/blog/2022-09-08-thanos-at-medallia.md b/docs/blog/2022-09-08-thanos-at-medallia.md
index 91ac7f37dd9..514b1651a42 100644
--- a/docs/blog/2022-09-08-thanos-at-medallia.md
+++ b/docs/blog/2022-09-08-thanos-at-medallia.md
@@ -20,7 +20,7 @@ The number of active series that our metrics platforms ingests at any given time
 
 With a scrape frequency of once per minute, that puts or ingestion throughput between 13-17 Million samples per seconds across all our ingest components (Prometheus/Thanos Receive).
 
-## Historical and current business context
+## Historical and current business contex
 
 Founded in 2001, Medallia is a pioneer and leader in the field of experience management as a SaaS solution. The initial focus for the company was on collecting and analyzing solicited feedback (i.e., web-based surveys). But, the focus has evolved over the years to include a variety of interactions, including voice, video, digital, IoT, social media, and corporate-messaging tools.
 
@@ -28,7 +28,7 @@ Observability is largely a practice of capturing a variety of health and perform
 
 Just as a goal in observability is to catch problems early and to facilitate fast mitigation, Medallia helps its customers to detect customer and employee dissatisfaction and to take proactive action while the relationship can still be salvaged .
 
-## Problem Statement
+## Problem Statemen
 
 With such a strong analogy from our own business to lean on, the value of investing in observability has not been a difficult concept to justify. However, until the middle of the previous decade, observability within Medallia was limited to reachability monitoring and log aggregation. At that point, however, the company’s broad-focused SRE organization brought forth the use of metrics, which was both a revelation to and a revolution within the engineering organization with respect to awareness of the quality and performance of our software.
 
@@ -106,7 +106,7 @@ Our current inventory, across all data centers, includes:
 - 402 Prometheus instances
 - 39 Alertmanager instances
 
-### Compute Cost
+### Compute Cos
 
 Over the course of a week, total resource utilization for all of our Thanos and Prometheus components across all data centers is within these ranges:
 
diff --git a/docs/blog/2023-06-02-lfx-mentorship-query-observability.md b/docs/blog/2023-06-02-lfx-mentorship-query-observability.md
index d1133ac615f..ec5e5a4879f 100644
--- a/docs/blog/2023-06-02-lfx-mentorship-query-observability.md
+++ b/docs/blog/2023-06-02-lfx-mentorship-query-observability.md
@@ -6,7 +6,7 @@ author: Pradyumna Krishna
 
 Hello everyone, my name is Pradyumna Krishna and I was contributing to Thanos as a part of the LFX mentorship programme. I was working on adding Query Execution Observability to the Thanos PromQL engine and Thanos project itself. I am going to share my experience and provide insights into the project.
 
-## The Project
+## The Projec
 
 ### What's PromQL?
 
@@ -66,7 +66,7 @@ Thanos UI got updated with time, resulting in the development of the explanation
 - Add method to explain query vector ([thanos-io/promql-engine#252](https://github.com/thanos-io/promql-engine/pull/252))
 - Query Explanation ([thanos-io/thanos#6346](https://github.com/thanos-io/thanos/pull/6346))
 
-### What next
+### What nex
 
 We have laid the foundation of Query Observability by implementing the Query Explanation feature. The next steps forward can be:
 * Showing memory allocations, CPU usage
diff --git a/docs/components/compact.md b/docs/components/compact.md
index dbc7f7d1531..09c07ea228a 100644
--- a/docs/components/compact.md
+++ b/docs/components/compact.md
@@ -17,7 +17,7 @@ Example content of `bucket.yml`:
 ```yaml
 type: GCS
 config:
-  bucket: example-bucket
+  bucket: example-bucke
 ```
 
 By default, `thanos compact` will run to completion which makes it possible to execute it as a cronjob. Using the arguments `--wait` and `--wait-interval=5m` it's possible to keep it running.
@@ -279,28 +279,28 @@ usage: thanos compact [<flags>]
 Continuously compacts blocks in an object store bucket.
 
 Flags:
-      --block-files-concurrency=1  
+      --block-files-concurrency=1
                                 Number of goroutines to use when
-                                fetching/uploading block files from object
+                                fetching/uploading block files from objec
                                 storage.
-      --block-meta-fetch-concurrency=32  
+      --block-meta-fetch-concurrency=32
                                 Number of goroutines to use when fetching block
                                 metadata from object storage.
-      --block-viewer.global.sync-block-interval=1m  
+      --block-viewer.global.sync-block-interval=1m
                                 Repeat interval for syncing the blocks between
                                 local and remote view for /global Block Viewer
                                 UI.
-      --block-viewer.global.sync-block-timeout=5m  
+      --block-viewer.global.sync-block-timeout=5m
                                 Maximum time for syncing the blocks between
                                 local and remote view for /global Block Viewer
                                 UI.
-      --bucket-web-label=BUCKET-WEB-LABEL  
+      --bucket-web-label=BUCKET-WEB-LABEL
                                 External block label to use as group title in
                                 the bucket web UI
-      --compact.blocks-fetch-concurrency=1  
+      --compact.blocks-fetch-concurrency=1
                                 Number of goroutines to use when download block
                                 during compaction.
-      --compact.cleanup-interval=5m  
+      --compact.cleanup-interval=5m
                                 How often we should clean up partially uploaded
                                 blocks and blocks with deletion mark in the
                                 background when --wait has been enabled. Setting
@@ -308,7 +308,7 @@ Flags:
                                 happen at the end of an iteration.
       --compact.concurrency=1   Number of goroutines to use when compacting
                                 groups.
-      --compact.progress-interval=5m  
+      --compact.progress-interval=5m
                                 Frequency of calculating the compaction progress
                                 in the background when --wait has been enabled.
                                 Setting it to "0s" disables it. Now compaction,
@@ -329,7 +329,7 @@ Flags:
                                 based deduplication algorithm will be used.
                                 At least one replica label has to be set via
                                 --deduplication.replica-label flag.
-      --deduplication.replica-label=DEDUPLICATION.REPLICA-LABEL ...  
+      --deduplication.replica-label=DEDUPLICATION.REPLICA-LABEL ...
                                 Label to treat as a replica indicator of blocks
                                 that can be deduplicated (repeated flag). This
                                 will merge multiple replica blocks into one.
@@ -353,28 +353,28 @@ Flags:
                                 Note that deleting blocks immediately can cause
                                 query failures, if store gateway still has the
                                 block loaded, or compactor is ignoring the
-                                deletion because it's compacting the block at
+                                deletion because it's compacting the block a
                                 the same time.
-      --disable-admin-operations  
+      --disable-admin-operations
                                 Disable UI/API admin operations like marking
                                 blocks for deletion and no compaction.
-      --downsample.concurrency=1  
+      --downsample.concurrency=1
                                 Number of goroutines to use when downsampling
                                 blocks.
       --downsampling.disable    Disables downsampling. This is not recommended
-                                as querying long time ranges without
+                                as querying long time ranges withou
                                 non-downsampled data is not efficient and useful
                                 e.g it is not possible to render all samples for
                                 a human eye anyway
       --hash-func=              Specify which hash function to use when
                                 calculating the hashes of produced files.
-                                If no function has been specified, it does not
+                                If no function has been specified, it does no
                                 happen. This permits avoiding downloading some
                                 files twice albeit at some performance cost.
                                 Possible values are: "", "SHA256".
   -h, --help                    Show context-sensitive help (also try
                                 --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                 Listen host:port for HTTP endpoints.
       --http-grace-period=2m    Time to wait after an interrupt received for
                                 HTTP Server.
@@ -384,7 +384,7 @@ Flags:
       --log.format=logfmt       Log format to use. Possible options: logfmt or
                                 json.
       --log.level=info          Log filtering level.
-      --max-time=9999-12-31T23:59:59Z  
+      --max-time=9999-12-31T23:59:59Z
                                 End of time range limit to compact.
                                 Thanos Compactor will compact only blocks,
                                 which happened earlier than this value. Option
@@ -392,36 +392,36 @@ Flags:
                                 duration relative to current time, such as -1d
                                 or 2h45m. Valid duration units are ms, s, m, h,
                                 d, w, y.
-      --min-time=0000-01-01T00:00:00Z  
+      --min-time=0000-01-01T00:00:00Z
                                 Start of time range limit to compact.
                                 Thanos Compactor will compact only blocks, which
                                 happened later than this value. Option can be a
                                 constant time in RFC3339 format or time duration
                                 relative to current time, such as -1d or 2h45m.
                                 Valid duration units are ms, s, m, h, d, w, y.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                 Alternative to 'objstore.config-file'
                                 flag (mutually exclusive). Content of
                                 YAML file that contains object store
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                Path to YAML file that contains objec
                                 store configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
-      --retention.resolution-1h=0d  
+      --retention.resolution-1h=0d
                                 How long to retain samples of resolution 2 (1
                                 hour) in bucket. Setting this to 0d will retain
                                 samples of this resolution forever
-      --retention.resolution-5m=0d  
+      --retention.resolution-5m=0d
                                 How long to retain samples of resolution 1 (5
                                 minutes) in bucket. Setting this to 0d will
                                 retain samples of this resolution forever
-      --retention.resolution-raw=0d  
+      --retention.resolution-raw=0d
                                 How long to retain raw samples in bucket.
                                 Setting this to 0d will retain samples of this
                                 resolution forever
-      --selector.relabel-config=<content>  
+      --selector.relabel-config=<content>
                                 Alternative to 'selector.relabel-config-file'
                                 flag (mutually exclusive). Content of
                                 YAML file that contains relabeling
@@ -429,18 +429,18 @@ Flags:
                                 blocks. It follows native Prometheus
                                 relabel-config syntax. See format details:
                                 https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
-      --selector.relabel-config-file=<file-path>  
+      --selector.relabel-config-file=<file-path>
                                 Path to YAML file that contains relabeling
                                 configuration that allows selecting
                                 blocks. It follows native Prometheus
                                 relabel-config syntax. See format details:
                                 https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                 Alternative to 'tracing.config-file' flag
                                 (mutually exclusive). Content of YAML file
                                 with tracing configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                 Path to YAML file with tracing
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -454,11 +454,11 @@ Flags:
       --web.disable-cors        Whether to disable CORS headers to be set by
                                 Thanos. By default Thanos sets CORS headers to
                                 be allowed by all.
-      --web.external-prefix=""  Static prefix for all HTML links and redirect
+      --web.external-prefix=""  Static prefix for all HTML links and redirec
                                 URLs in the bucket web UI interface.
                                 Actual endpoints are still served on / or the
-                                web.route-prefix. This allows thanos bucket
-                                web UI to be served behind a reverse proxy that
+                                web.route-prefix. This allows thanos bucke
+                                web UI to be served behind a reverse proxy tha
                                 strips a URL sub-path.
       --web.prefix-header=""    Name of HTTP request header used for dynamic
                                 prefixing of UI links and redirects.
diff --git a/docs/components/query-frontend.md b/docs/components/query-frontend.md
index 5ddd032aed0..3e0a2bfbfc8 100644
--- a/docs/components/query-frontend.md
+++ b/docs/components/query-frontend.md
@@ -7,8 +7,8 @@ Query Frontend is fully stateless and horizontally scalable.
 Example command to run Query Frontend:
 
 ```bash
-thanos query-frontend \
-    --http-address     "0.0.0.0:9090" \
+thanos query-frontend
+    --http-address     "0.0.0.0:9090"
     --query-frontend.downstream-url="<thanos-querier>:<querier-http-port>"
 ```
 
@@ -170,8 +170,8 @@ You can find the default values [here](https://github.com/thanos-io/thanos/blob/
 If downstream queriers need basic authentication to access, we can run query-frontend:
 
 ```bash
-thanos query-frontend \
-    --http-address     "0.0.0.0:9090" \
+thanos query-frontend
+    --http-address     "0.0.0.0:9090"
     --query-frontend.forward-header "Authorization"
     --query-frontend.downstream-url="<thanos-querier>:<querier-http-port>"
 ```
@@ -185,46 +185,46 @@ Query frontend command implements a service deployed in front of queriers to
 improve query parallelization and caching.
 
 Flags:
-      --cache-compression-type=""  
+      --cache-compression-type=""
                                  Use compression in results cache.
                                  Supported values are: 'snappy' and ” (disable
                                  compression).
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
       --http.config=""           [EXPERIMENTAL] Path to the configuration file
                                  that can enable TLS or authentication for all
                                  HTTP endpoints.
-      --labels.default-time-range=24h  
+      --labels.default-time-range=24h
                                  The default metadata time range duration for
                                  retrieving labels through Labels and Series API
                                  when the range parameters are not specified.
-      --labels.max-query-parallelism=14  
+      --labels.max-query-parallelism=14
                                  Maximum number of labels requests will be
                                  scheduled in parallel by the Frontend.
-      --labels.max-retries-per-request=5  
+      --labels.max-retries-per-request=5
                                  Maximum number of retries for a single
                                  label/series API request; beyond this,
                                  the downstream error is returned.
       --labels.partial-response  Enable partial response for labels requests
                                  if no partial_response param is specified.
                                  --no-labels.partial-response for disabling.
-      --labels.response-cache-config=<content>  
+      --labels.response-cache-config=<content>
                                  Alternative to
                                  'labels.response-cache-config-file' flag
-                                 (mutually exclusive). Content of YAML file that
+                                 (mutually exclusive). Content of YAML file tha
                                  contains response cache configuration.
-      --labels.response-cache-config-file=<file-path>  
+      --labels.response-cache-config-file=<file-path>
                                  Path to YAML file that contains response cache
                                  configuration.
-      --labels.response-cache-max-freshness=1m  
+      --labels.response-cache-max-freshness=1m
                                  Most recent allowed cacheable result for
-                                 labels requests, to prevent caching very recent
+                                 labels requests, to prevent caching very recen
                                  results that might still be in flux.
-      --labels.split-interval=24h  
+      --labels.split-interval=24h
                                  Split labels requests by an interval and
                                  execute in parallel, it should be greater
                                  than 0 when labels.response-cache-config is
@@ -241,121 +241,121 @@ Flags:
                                  LogStartAndFinishCall : Logs the start and
                                  finish call of the requests. NoLogCall :
                                  Disable request logging.
-      --query-frontend.compress-responses  
+      --query-frontend.compress-responses
                                  Compress HTTP responses.
-      --query-frontend.downstream-tripper-config=<content>  
+      --query-frontend.downstream-tripper-config=<content>
                                  Alternative to
                                  'query-frontend.downstream-tripper-config-file'
                                  flag (mutually exclusive). Content of YAML file
                                  that contains downstream tripper configuration.
                                  If your downstream URL is localhost or
                                  127.0.0.1 then it is highly recommended to
-                                 increase max_idle_conns_per_host to at least
+                                 increase max_idle_conns_per_host to at leas
                                  100.
-      --query-frontend.downstream-tripper-config-file=<file-path>  
+      --query-frontend.downstream-tripper-config-file=<file-path>
                                  Path to YAML file that contains downstream
                                  tripper configuration. If your downstream URL
                                  is localhost or 127.0.0.1 then it is highly
-                                 recommended to increase max_idle_conns_per_host
+                                 recommended to increase max_idle_conns_per_hos
                                  to at least 100.
-      --query-frontend.downstream-url="http://localhost:9090"  
+      --query-frontend.downstream-url="http://localhost:9090"
                                  URL of downstream Prometheus Query compatible
                                  API.
-      --query-frontend.forward-header=<http-header-name> ...  
+      --query-frontend.forward-header=<http-header-name> ...
                                  List of headers forwarded by the query-frontend
                                  to downstream queriers, default is empty
-      --query-frontend.log-queries-longer-than=0  
+      --query-frontend.log-queries-longer-than=0
                                  Log queries that are slower than the specified
                                  duration. Set to 0 to disable. Set to < 0 to
                                  enable on all queries.
-      --query-frontend.org-id-header=<http-header-name> ...  
+      --query-frontend.org-id-header=<http-header-name> ...
                                  Request header names used to identify the
                                  source of slow queries (repeated flag).
                                  The values of the header will be added to
                                  the org id field in the slow query log. If
-                                 multiple headers match the request, the first
+                                 multiple headers match the request, the firs
                                  matching arg specified will take precedence.
                                  If no headers match 'anonymous' will be used.
-      --query-frontend.vertical-shards=QUERY-FRONTEND.VERTICAL-SHARDS  
+      --query-frontend.vertical-shards=QUERY-FRONTEND.VERTICAL-SHARDS
                                  Number of shards to use when
                                  distributing shardable PromQL queries.
                                  For more details, you can refer to
                                  the Vertical query sharding proposal:
                                  https://thanos.io/tip/proposals-accepted/202205-vertical-query-sharding.md
-      --query-range.align-range-with-step  
+      --query-range.align-range-with-step
                                  Mutate incoming queries to align their
                                  start and end with their step for better
-                                 cache-ability. Note: Grafana dashboards do that
+                                 cache-ability. Note: Grafana dashboards do tha
                                  by default.
-      --query-range.horizontal-shards=0  
+      --query-range.horizontal-shards=0
                                  Split queries in this many requests
                                  when query duration is below
                                  query-range.max-split-interval.
-      --query-range.max-query-length=0  
+      --query-range.max-query-length=0
                                  Limit the query time range (end - start time)
                                  in the query-frontend, 0 disables it.
-      --query-range.max-query-parallelism=14  
+      --query-range.max-query-parallelism=14
                                  Maximum number of query range requests will be
                                  scheduled in parallel by the Frontend.
-      --query-range.max-retries-per-request=5  
+      --query-range.max-retries-per-request=5
                                  Maximum number of retries for a single query
                                  range request; beyond this, the downstream
                                  error is returned.
-      --query-range.max-split-interval=0  
+      --query-range.max-split-interval=0
                                  Split query range below this interval in
                                  query-range.horizontal-shards. Queries with a
                                  range longer than this value will be split in
                                  multiple requests of this length.
-      --query-range.min-split-interval=0  
+      --query-range.min-split-interval=0
                                  Split query range requests above this
                                  interval in query-range.horizontal-shards
                                  requests of equal range. Using
                                  this parameter is not allowed with
-                                 query-range.split-interval. One should also set
+                                 query-range.split-interval. One should also se
                                  query-range.split-min-horizontal-shards to a
                                  value greater than 1 to enable splitting.
-      --query-range.partial-response  
+      --query-range.partial-response
                                  Enable partial response for query range
                                  requests if no partial_response param is
                                  specified. --no-query-range.partial-response
                                  for disabling.
-      --query-range.request-downsampled  
+      --query-range.request-downsampled
                                  Make additional query for downsampled data in
                                  case of empty or incomplete response to range
                                  request.
-      --query-range.response-cache-config=<content>  
+      --query-range.response-cache-config=<content>
                                  Alternative to
                                  'query-range.response-cache-config-file' flag
-                                 (mutually exclusive). Content of YAML file that
+                                 (mutually exclusive). Content of YAML file tha
                                  contains response cache configuration.
-      --query-range.response-cache-config-file=<file-path>  
+      --query-range.response-cache-config-file=<file-path>
                                  Path to YAML file that contains response cache
                                  configuration.
-      --query-range.response-cache-max-freshness=1m  
+      --query-range.response-cache-max-freshness=1m
                                  Most recent allowed cacheable result for query
-                                 range requests, to prevent caching very recent
+                                 range requests, to prevent caching very recen
                                  results that might still be in flux.
-      --query-range.split-interval=24h  
+      --query-range.split-interval=24h
                                  Split query range requests by an interval and
                                  execute in parallel, it should be greater than
                                  0 when query-range.response-cache-config is
                                  configured.
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
diff --git a/docs/components/query.md b/docs/components/query.md
index 60615724fd4..86edb3c88a4 100644
--- a/docs/components/query.md
+++ b/docs/components/query.md
@@ -9,9 +9,9 @@ Querier is fully stateless and horizontally scalable.
 Example command to run Querier:
 
 ```bash
-thanos query \
-    --http-address     "0.0.0.0:9090" \
-    --endpoint         "<store-api>:<grpc-port>" \
+thanos query
+    --http-address     "0.0.0.0:9090"
+    --endpoint         "<store-api>:<grpc-port>"
     --endpoint         "<store-api2>:<grpc-port>"
 ```
 
@@ -68,11 +68,11 @@ Two or more series that are only distinguished by the given replica label, will
 If we configure Querier like this:
 
 ```
-thanos query \
-    --http-address        "0.0.0.0:9090" \
-    --query.replica-label "replica" \
-    --endpoint            "<store-api>:<grpc-port>" \
-    --endpoint            "<store-api2>:<grpc-port>" \
+thanos query
+    --http-address        "0.0.0.0:9090"
+    --query.replica-label "replica"
+    --endpoint            "<store-api>:<grpc-port>"
+    --endpoint            "<store-api2>:<grpc-port>"
 ```
 
 And we query for metric `up{job="prometheus",env="2"}` with this option we will get 2 results:
@@ -93,12 +93,12 @@ WITHOUT this replica flag (deduplication turned off), we will get 3 results:
 * Prometheus + sidecar "A" in different cluster: `cluster=2,env=2,replica=A,replicaX=A`
 
 ```
-thanos query \
-    --http-address        "0.0.0.0:9090" \
-    --query.replica-label "replica" \
-    --query.replica-label "replicaX" \
-    --endpoint            "<store-api>:<grpc-port>" \
-    --endpoint            "<store-api2>:<grpc-port>" \
+thanos query
+    --http-address        "0.0.0.0:9090"
+    --query.replica-label "replica"
+    --query.replica-label "replicaX"
+    --endpoint            "<store-api>:<grpc-port>"
+    --endpoint            "<store-api2>:<grpc-port>"
 ```
 
 This logic can also be controlled via parameter on QueryAPI. More details below.
@@ -279,69 +279,69 @@ Query node exposing PromQL enabled Query API with data retrieved from multiple
 store nodes.
 
 Flags:
-      --alert.query-url=ALERT.QUERY-URL  
-                                 The external Thanos Query URL that would be set
+      --alert.query-url=ALERT.QUERY-URL
+                                 The external Thanos Query URL that would be se
                                  in all alerts 'Source' field.
       --enable-feature= ...      Comma separated experimental feature names
                                  to enable.The current list of features is
                                  query-pushdown.
       --endpoint=<endpoint> ...  Addresses of statically configured Thanos
                                  API servers (repeatable). The scheme may be
-                                 prefixed with 'dns+' or 'dnssrv+' to detect
+                                 prefixed with 'dns+' or 'dnssrv+' to detec
                                  Thanos API servers through respective DNS
                                  lookups.
-      --endpoint-group=<endpoint-group> ...  
+      --endpoint-group=<endpoint-group> ...
                                  Experimental: DNS name of statically configured
                                  Thanos API server groups (repeatable). Targets
                                  resolved from the DNS name will be queried in
                                  a round-robin, instead of a fanout manner.
                                  This flag should be used when connecting a
                                  Thanos Query to HA groups of Thanos components.
-      --endpoint-group-strict=<endpoint-group-strict> ...  
+      --endpoint-group-strict=<endpoint-group-strict> ...
                                  Experimental: DNS name of statically configured
                                  Thanos API server groups (repeatable) that are
                                  always used, even if the health check fails.
-      --endpoint-strict=<staticendpoint> ...  
+      --endpoint-strict=<staticendpoint> ...
                                  Addresses of only statically configured Thanos
                                  API servers that are always used, even if
                                  the health check fails. Useful if you have a
                                  caching layer on top.
-      --grpc-address="0.0.0.0:10901"  
+      --grpc-address="0.0.0.0:10901"
                                  Listen ip:port address for gRPC endpoints
                                  (StoreAPI). Make sure this address is routable
                                  from other components.
-      --grpc-client-server-name=""  
+      --grpc-client-server-name=""
                                  Server name to verify the hostname on
                                  the returned gRPC certificates. See
                                  https://tools.ietf.org/html/rfc4366#section-3.1
       --grpc-client-tls-ca=""    TLS CA Certificates to use to verify gRPC
                                  servers
-      --grpc-client-tls-cert=""  TLS Certificates to use to identify this client
+      --grpc-client-tls-cert=""  TLS Certificates to use to identify this clien
                                  to the server
       --grpc-client-tls-key=""   TLS Key for the client's certificate
       --grpc-client-tls-secure   Use TLS when talking to the gRPC server
-      --grpc-client-tls-skip-verify  
+      --grpc-client-tls-skip-verify
                                  Disable TLS certificate verification i.e self
                                  signed, signed by fake CA
       --grpc-compression=none    Compression algorithm to use for gRPC requests
                                  to other clients. Must be one of: snappy, none
       --grpc-grace-period=2m     Time to wait after an interrupt received for
                                  GRPC Server.
-      --grpc-server-max-connection-age=60m  
+      --grpc-server-max-connection-age=60m
                                  The grpc server max connection age. This
                                  controls how often to re-establish connections
                                  and redo TLS handshakes.
       --grpc-server-tls-cert=""  TLS Certificate for gRPC server, leave blank to
                                  disable TLS
-      --grpc-server-tls-client-ca=""  
+      --grpc-server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
       --grpc-server-tls-key=""   TLS Key for the gRPC server, leave blank to
                                  disable TLS
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
@@ -360,44 +360,44 @@ Flags:
                                  LogStartAndFinishCall: Logs the start and
                                  finish call of the requests. NoLogCall: Disable
                                  request logging.
-      --query.active-query-path=""  
+      --query.active-query-path=""
                                  Directory to log currently active queries in
                                  the queries.active file.
-      --query.auto-downsampling  Enable automatic adjustment (step / 5) to what
+      --query.auto-downsampling  Enable automatic adjustment (step / 5) to wha
                                  source of data should be used in store gateways
                                  if no max_source_resolution param is specified.
-      --query.conn-metric.label=external_labels... ...  
+      --query.conn-metric.label=external_labels... ...
                                  Optional selection of query connection metric
-                                 labels to be collected from endpoint set
-      --query.default-evaluation-interval=1m  
+                                 labels to be collected from endpoint se
+      --query.default-evaluation-interval=1m
                                  Set default evaluation interval for sub
                                  queries.
-      --query.default-step=1s    Set default step for range queries. Default
+      --query.default-step=1s    Set default step for range queries. Defaul
                                  step is only used when step is not set in UI.
-                                 In such cases, Thanos UI will use default
+                                 In such cases, Thanos UI will use defaul
                                  step to calculate resolution (resolution
                                  = max(rangeSeconds / 250, defaultStep)).
                                  This will not work from Grafana, but Grafana
                                  has __step variable which can be used.
-      --query.lookback-delta=QUERY.LOOKBACK-DELTA  
+      --query.lookback-delta=QUERY.LOOKBACK-DELTA
                                  The maximum lookback duration for retrieving
                                  metrics during expression evaluations.
                                  PromQL always evaluates the query for the
                                  certain timestamp (query range timestamps are
-                                 deduced by step). Since scrape intervals might
+                                 deduced by step). Since scrape intervals migh
                                  be different, PromQL looks back for given
-                                 amount of time to get latest sample. If it
+                                 amount of time to get latest sample. If i
                                  exceeds the maximum lookback delta it assumes
                                  series is stale and returns none (a gap).
-                                 This is why lookback delta should be set to at
+                                 This is why lookback delta should be set to a
                                  least 2 times of the slowest scrape interval.
                                  If unset it will use the promql default of 5m.
       --query.max-concurrent=20  Maximum number of queries processed
                                  concurrently by query node.
-      --query.max-concurrent-select=4  
+      --query.max-concurrent-select=4
                                  Maximum number of select requests made
                                  concurrently per a query.
-      --query.metadata.default-time-range=0s  
+      --query.metadata.default-time-range=0s
                                  The default metadata time range duration for
                                  retrieving labels through Labels and Series API
                                  when the range parameters are not specified.
@@ -406,35 +406,35 @@ Flags:
       --query.partial-response   Enable partial response for queries if
                                  no partial_response param is specified.
                                  --no-query.partial-response for disabling.
-      --query.promql-engine=prometheus  
+      --query.promql-engine=prometheus
                                  Default PromQL engine to use.
-      --query.replica-label=QUERY.REPLICA-LABEL ...  
+      --query.replica-label=QUERY.REPLICA-LABEL ...
                                  Labels to treat as a replica indicator along
                                  which data is deduplicated. Still you will
                                  be able to query without deduplication using
                                  'dedup=false' parameter. Data includes time
                                  series, recording rules, and alerting rules.
-      --query.telemetry.request-duration-seconds-quantiles=0.1... ...  
+      --query.telemetry.request-duration-seconds-quantiles=0.1... ...
                                  The quantiles for exporting metrics about the
                                  request duration quantiles.
-      --query.telemetry.request-samples-quantiles=100... ...  
+      --query.telemetry.request-samples-quantiles=100... ...
                                  The quantiles for exporting metrics about the
                                  samples count quantiles.
-      --query.telemetry.request-series-seconds-quantiles=10... ...  
+      --query.telemetry.request-series-seconds-quantiles=10... ...
                                  The quantiles for exporting metrics about the
                                  series count quantiles.
       --query.timeout=2m         Maximum time to process query by query node.
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --selector-label=<name>="<value>" ...  
+      --selector-label=<name>="<value>" ...
                                  Query selector labels that will be exposed in
                                  info endpoint (repeated).
       --store=<store> ...        Deprecation Warning - This flag is deprecated
@@ -443,46 +443,46 @@ Flags:
                                  (repeatable). The scheme may be prefixed with
                                  'dns+' or 'dnssrv+' to detect store API servers
                                  through respective DNS lookups.
-      --store-strict=<staticstore> ...  
+      --store-strict=<staticstore> ...
                                  Deprecation Warning - This flag is deprecated
                                  and replaced with `endpoint-strict`. Addresses
                                  of only statically configured store API servers
                                  that are always used, even if the health check
                                  fails. Useful if you have a caching layer on
                                  top.
-      --store.limits.request-samples=0  
+      --store.limits.request-samples=0
                                  The maximum samples allowed for a single
                                  Series request, The Series call fails if
                                  this limit is exceeded. 0 means no limit.
                                  NOTE: For efficiency the limit is internally
                                  implemented as 'chunks limit' considering each
                                  chunk contains a maximum of 120 samples.
-      --store.limits.request-series=0  
+      --store.limits.request-series=0
                                  The maximum series allowed for a single Series
                                  request. The Series call fails if this limit is
                                  exceeded. 0 means no limit.
-      --store.response-timeout=0ms  
+      --store.response-timeout=0ms
                                  If a Store doesn't send any data in this
                                  specified duration then a Store will be ignored
                                  and partial data will be returned if it's
                                  enabled. 0 disables timeout.
-      --store.sd-dns-interval=30s  
+      --store.sd-dns-interval=30s
                                  Interval between DNS resolutions.
-      --store.sd-files=<path> ...  
+      --store.sd-files=<path> ...
                                  Path to files that contain addresses of store
                                  API servers. The path can be a glob pattern
                                  (repeatable).
       --store.sd-interval=5m     Refresh interval to re-read file SD files.
                                  It is used as a resync fallback.
-      --store.unhealthy-timeout=5m  
+      --store.unhealthy-timeout=5m
                                  Timeout before an unhealthy store is cleaned
                                  from the store UI page.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
diff --git a/docs/components/receive.md b/docs/components/receive.md
index 371e5f4a7f4..014462a3a61 100644
--- a/docs/components/receive.md
+++ b/docs/components/receive.md
@@ -36,7 +36,7 @@ Thanos Receive supports getting TSDB stats using the `/api/v1/status/tsdb` endpo
 
 Note that each Thanos Receive will only expose local stats and replicated series will not be included in the response.
 
-## Tenant lifecycle management
+## Tenant lifecycle managemen
 
 Tenants in Receivers are created dynamically and do not need to be provisioned upfront. When a new value is detected in the tenant HTTP header, Receivers will provision and start managing an independent TSDB for that tenant. TSDB blocks that are sent to S3 will contain a unique `tenant_id` label which can be used to compact blocks independently for each tenant.
 
@@ -47,16 +47,16 @@ Note that because of the built-in decommissioning process, the semantic of the `
 ## Example
 
 ```bash
-thanos receive \
-    --tsdb.path "/path/to/receive/data/dir" \
-    --grpc-address 0.0.0.0:10907 \
-    --http-address 0.0.0.0:10909 \
-    --receive.replication-factor 1 \
-    --label "receive_replica=\"0\"" \
-    --label "receive_cluster=\"eu1\"" \
-    --receive.local-endpoint 127.0.0.1:10907 \
-    --receive.hashrings-file ./data/hashring.json \
-    --remote-write.address 0.0.0.0:10908 \
+thanos receive
+    --tsdb.path "/path/to/receive/data/dir"
+    --grpc-address 0.0.0.0:10907
+    --http-address 0.0.0.0:10909
+    --receive.replication-factor 1
+    --label "receive_replica=\"0\""
+    --label "receive_cluster=\"eu1\""
+    --receive.local-endpoint 127.0.0.1:10907
+    --receive.hashrings-file ./data/hashring.json
+    --remote-write.address 0.0.0.0:10908
     --objstore.config-file "bucket.yml"
 ```
 
@@ -256,33 +256,33 @@ usage: thanos receive [<flags>]
 Accept Prometheus remote write API requests and write to local tsdb.
 
 Flags:
-      --grpc-address="0.0.0.0:10901"  
+      --grpc-address="0.0.0.0:10901"
                                  Listen ip:port address for gRPC endpoints
                                  (StoreAPI). Make sure this address is routable
                                  from other components.
       --grpc-grace-period=2m     Time to wait after an interrupt received for
                                  GRPC Server.
-      --grpc-server-max-connection-age=60m  
+      --grpc-server-max-connection-age=60m
                                  The grpc server max connection age. This
                                  controls how often to re-establish connections
                                  and redo TLS handshakes.
       --grpc-server-tls-cert=""  TLS Certificate for gRPC server, leave blank to
                                  disable TLS
-      --grpc-server-tls-client-ca=""  
+      --grpc-server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
       --grpc-server-tls-key=""   TLS Key for the gRPC server, leave blank to
                                  disable TLS
       --hash-func=               Specify which hash function to use when
                                  calculating the hashes of produced files.
-                                 If no function has been specified, it does not
+                                 If no function has been specified, it does no
                                  happen. This permits avoiding downloading some
                                  files twice albeit at some performance cost.
                                  Possible values are: "", "SHA256".
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
@@ -295,125 +295,125 @@ Flags:
       --log.format=logfmt        Log format to use. Possible options: logfmt or
                                  json.
       --log.level=info           Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                  Alternative to 'objstore.config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains object store
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                 Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                 Path to YAML file that contains objec
                                  store configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --receive.default-tenant-id="default-tenant"  
+      --receive.default-tenant-id="default-tenant"
                                  Default tenant ID to use when none is provided
                                  via a header.
-      --receive.grpc-compression=snappy  
+      --receive.grpc-compression=snappy
                                  Compression algorithm to use for gRPC requests
                                  to other receivers. Must be one of: snappy,
                                  none
-      --receive.hashrings=<content>  
+      --receive.hashrings=<content>
                                  Alternative to 'receive.hashrings-file' flag
                                  (lower priority). Content of file that contains
                                  the hashring configuration.
-      --receive.hashrings-algorithm=hashmod  
+      --receive.hashrings-algorithm=hashmod
                                  The algorithm used when distributing series in
                                  the hashrings. Must be one of hashmod, ketama.
                                  Will be overwritten by the tenant-specific
                                  algorithm in the hashring config.
-      --receive.hashrings-file=<path>  
+      --receive.hashrings-file=<path>
                                  Path to file that contains the hashring
                                  configuration. A watcher is initialized
                                  to watch changes and update the hashring
                                  dynamically.
-      --receive.hashrings-file-refresh-interval=5m  
+      --receive.hashrings-file-refresh-interval=5m
                                  Refresh interval to re-read the hashring
                                  configuration file. (used as a fallback)
-      --receive.local-endpoint=RECEIVE.LOCAL-ENDPOINT  
+      --receive.local-endpoint=RECEIVE.LOCAL-ENDPOINT
                                  Endpoint of local receive node. Used to
                                  identify the local node in the hashring
                                  configuration. If it's empty AND hashring
-                                 configuration was provided, it means that
+                                 configuration was provided, it means tha
                                  receive will run in RoutingOnly mode.
-      --receive.relabel-config=<content>  
+      --receive.relabel-config=<content>
                                  Alternative to 'receive.relabel-config-file'
                                  flag (mutually exclusive). Content of YAML file
                                  that contains relabeling configuration.
-      --receive.relabel-config-file=<file-path>  
+      --receive.relabel-config-file=<file-path>
                                  Path to YAML file that contains relabeling
                                  configuration.
-      --receive.replica-header="THANOS-REPLICA"  
+      --receive.replica-header="THANOS-REPLICA"
                                  HTTP header specifying the replica number of a
                                  write request.
-      --receive.replication-factor=1  
+      --receive.replication-factor=1
                                  How many times to replicate incoming write
                                  requests.
-      --receive.tenant-certificate-field=  
+      --receive.tenant-certificate-field=
                                  Use TLS client's certificate field to
                                  determine tenant for write requests.
-                                 Must be one of organization, organizationalUnit
+                                 Must be one of organization, organizationalUni
                                  or commonName. This setting will cause the
                                  receive.tenant-header flag value to be ignored.
-      --receive.tenant-header="THANOS-TENANT"  
+      --receive.tenant-header="THANOS-TENANT"
                                  HTTP header to determine tenant for write
                                  requests.
-      --receive.tenant-label-name="tenant_id"  
+      --receive.tenant-label-name="tenant_id"
                                  Label name through which the tenant will be
                                  announced.
-      --remote-write.address="0.0.0.0:19291"  
+      --remote-write.address="0.0.0.0:19291"
                                  Address to listen on for remote write requests.
-      --remote-write.client-server-name=""  
+      --remote-write.client-server-name=""
                                  Server name to verify the hostname
                                  on the returned TLS certificates. See
                                  https://tools.ietf.org/html/rfc4366#section-3.1
-      --remote-write.client-tls-ca=""  
+      --remote-write.client-tls-ca=""
                                  TLS CA Certificates to use to verify servers.
-      --remote-write.client-tls-cert=""  
-                                 TLS Certificates to use to identify this client
+      --remote-write.client-tls-cert=""
+                                 TLS Certificates to use to identify this clien
                                  to the server.
-      --remote-write.client-tls-key=""  
+      --remote-write.client-tls-key=""
                                  TLS Key for the client's certificate.
-      --remote-write.server-tls-cert=""  
+      --remote-write.server-tls-cert=""
                                  TLS Certificate for HTTP server, leave blank to
                                  disable TLS.
-      --remote-write.server-tls-client-ca=""  
+      --remote-write.server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
-      --remote-write.server-tls-key=""  
+      --remote-write.server-tls-key=""
                                  TLS Key for the HTTP server, leave blank to
                                  disable TLS.
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --store.limits.request-samples=0  
+      --store.limits.request-samples=0
                                  The maximum samples allowed for a single
                                  Series request, The Series call fails if
                                  this limit is exceeded. 0 means no limit.
                                  NOTE: For efficiency the limit is internally
                                  implemented as 'chunks limit' considering each
                                  chunk contains a maximum of 120 samples.
-      --store.limits.request-series=0  
+      --store.limits.request-series=0
                                  The maximum series allowed for a single Series
                                  request. The Series call fails if this limit is
                                  exceeded. 0 means no limit.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tsdb.allow-overlapping-blocks  
+      --tsdb.allow-overlapping-blocks
                                  Allow overlapping blocks, which in turn enables
                                  vertical compaction and vertical query merge.
                                  Does not do anything, enabled all the time.
@@ -422,7 +422,7 @@ Flags:
                                  be stored per tenant. In case the exemplar
                                  storage becomes full (number of stored
                                  exemplars becomes equal to max-exemplars),
-                                 ingesting a new exemplar will evict the oldest
+                                 ingesting a new exemplar will evict the oldes
                                  exemplar from storage. 0 (or less) value of
                                  this flag disables exemplars storage.
       --tsdb.no-lockfile         Do not create lockfile in TSDB data directory.
@@ -434,10 +434,10 @@ Flags:
                                  policy (i.e. infinite retention).
                                  For more details on how retention is
                                  enforced for individual tenants, please
-                                 refer to the Tenant lifecycle management
+                                 refer to the Tenant lifecycle managemen
                                  section in the Receive documentation:
-                                 https://thanos.io/tip/components/receive.md/#tenant-lifecycle-management
-      --tsdb.too-far-in-future.time-window=0s  
+                                 https://thanos.io/tip/components/receive.md/#tenant-lifecycle-managemen
+      --tsdb.too-far-in-future.time-window=0s
                                  [EXPERIMENTAL] Configures the allowed time
                                  window for ingesting samples too far in the
                                  future. Disabled (0s) by defaultPlease note
diff --git a/docs/components/rule.md b/docs/components/rule.md
index 946f3ea49c8..91e4b956844 100644
--- a/docs/components/rule.md
+++ b/docs/components/rule.md
@@ -15,16 +15,16 @@ You can think of Rule as a simplified Prometheus that does not require a sidecar
 The data of each Rule node can be labeled to satisfy the clusters labeling scheme. High-availability pairs can be run in parallel and should be distinguished by the designated replica label, just like regular Prometheus servers. Read more about Ruler in HA [here](#ruler-ha)
 
 ```bash
-thanos rule \
-    --data-dir             "/path/to/data" \
-    --eval-interval        "30s" \
-    --rule-file            "/path/to/rules/*.rules.yaml" \
+thanos rule
+    --data-dir             "/path/to/data"
+    --eval-interval        "30s"
+    --rule-file            "/path/to/rules/*.rules.yaml"
     --alert.query-url      "http://0.0.0.0:9090" \ # This tells what query URL to link to in UI.
-    --alertmanagers.url    "http://alert.thanos.io" \
-    --query                "query.example.org" \
-    --query                "query2.example.org" \
-    --objstore.config-file "bucket.yml" \
-    --label                'monitor_cluster="cluster1"' \
+    --alertmanagers.url    "http://alert.thanos.io"
+    --query                "query.example.org"
+    --query                "query2.example.org"
+    --objstore.config-file "bucket.yml"
+    --label                'monitor_cluster="cluster1"'
     --label                'replica="A"'
 ```
 
@@ -213,17 +213,17 @@ The WAL only storage reuses the upstream [Prometheus agent](https://prometheus.i
 Stateless mode can be enabled by providing [Prometheus remote write config](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write) in file via `--remote-write.config` or inlined `--remote-write.config-file` flag. For example:
 
 ```bash
-thanos rule \
-    --data-dir                  "/path/to/data" \
-    --eval-interval             "30s" \
-    --rule-file                 "/path/to/rules/*.rules.yaml" \
+thanos rule
+    --data-dir                  "/path/to/data"
+    --eval-interval             "30s"
+    --rule-file                 "/path/to/rules/*.rules.yaml"
     --alert.query-url           "http://0.0.0.0:9090" \ # This tells what query URL to link to in UI.
-    --alertmanagers.url         "http://alert.thanos.io" \
-    --query                     "query.example.org" \
-    --query                     "query2.example.org" \
-    --objstore.config-file      "bucket.yml" \
-    --label                     'monitor_cluster="cluster1"' \
-    --label                     'replica="A"' \
+    --alertmanagers.url         "http://alert.thanos.io"
+    --query                     "query.example.org"
+    --query                     "query2.example.org"
+    --objstore.config-file      "bucket.yml"
+    --label                     'monitor_cluster="cluster1"'
+    --label                     'replica="A"'
     --remote-write.config-file  'rw-config.yaml'
 ```
 
@@ -262,49 +262,49 @@ Ruler evaluating Prometheus rules against given Query nodes, exposing Store API
 and storing old blocks in bucket.
 
 Flags:
-      --alert.label-drop=ALERT.LABEL-DROP ...  
+      --alert.label-drop=ALERT.LABEL-DROP ...
                                  Labels by name to drop before sending
                                  to alertmanager. This allows alert to be
                                  deduplicated on replica label (repeated).
                                  Similar Prometheus alert relabelling
-      --alert.query-url=ALERT.QUERY-URL  
-                                 The external Thanos Query URL that would be set
+      --alert.query-url=ALERT.QUERY-URL
+                                 The external Thanos Query URL that would be se
                                  in all alerts 'Source' field
-      --alert.relabel-config=<content>  
+      --alert.relabel-config=<content>
                                  Alternative to 'alert.relabel-config-file' flag
-                                 (mutually exclusive). Content of YAML file that
+                                 (mutually exclusive). Content of YAML file tha
                                  contains alert relabelling configuration.
-      --alert.relabel-config-file=<file-path>  
-                                 Path to YAML file that contains alert
+      --alert.relabel-config-file=<file-path>
+                                 Path to YAML file that contains aler
                                  relabelling configuration.
-      --alertmanagers.config=<content>  
+      --alertmanagers.config=<content>
                                  Alternative to 'alertmanagers.config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file that contains alerting
                                  configuration. See format details:
                                  https://thanos.io/tip/components/rule.md/#configuration.
                                  If defined, it takes precedence
                                  over the '--alertmanagers.url' and
                                  '--alertmanagers.send-timeout' flags.
-      --alertmanagers.config-file=<file-path>  
+      --alertmanagers.config-file=<file-path>
                                  Path to YAML file that contains alerting
                                  configuration. See format details:
                                  https://thanos.io/tip/components/rule.md/#configuration.
                                  If defined, it takes precedence
                                  over the '--alertmanagers.url' and
                                  '--alertmanagers.send-timeout' flags.
-      --alertmanagers.sd-dns-interval=30s  
+      --alertmanagers.sd-dns-interval=30s
                                  Interval between DNS resolutions of
                                  Alertmanager hosts.
-      --alertmanagers.send-timeout=10s  
+      --alertmanagers.send-timeout=10s
                                  Timeout for sending alerts to Alertmanager
-      --alertmanagers.url=ALERTMANAGERS.URL ...  
+      --alertmanagers.url=ALERTMANAGERS.URL ...
                                  Alertmanager replica URLs to push firing
                                  alerts. Ruler claims success if push to
                                  at least one alertmanager from discovered
                                  succeeds. The scheme should not be empty
                                  e.g `http` might be used. The scheme may be
-                                 prefixed with 'dns+' or 'dnssrv+' to detect
+                                 prefixed with 'dns+' or 'dnssrv+' to detec
                                  Alertmanager IPs through respective DNS
                                  lookups. The port defaults to 9093 or the
                                  SRV record's value. The URL path is used as a
@@ -317,40 +317,40 @@ Flags:
                                  period.
       --for-outage-tolerance=1h  Max time to tolerate prometheus outage for
                                  restoring "for" state of alert.
-      --grpc-address="0.0.0.0:10901"  
+      --grpc-address="0.0.0.0:10901"
                                  Listen ip:port address for gRPC endpoints
                                  (StoreAPI). Make sure this address is routable
                                  from other components.
       --grpc-grace-period=2m     Time to wait after an interrupt received for
                                  GRPC Server.
-      --grpc-server-max-connection-age=60m  
+      --grpc-server-max-connection-age=60m
                                  The grpc server max connection age. This
                                  controls how often to re-establish connections
                                  and redo TLS handshakes.
       --grpc-server-tls-cert=""  TLS Certificate for gRPC server, leave blank to
                                  disable TLS
-      --grpc-server-tls-client-ca=""  
+      --grpc-server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
       --grpc-server-tls-key=""   TLS Key for the gRPC server, leave blank to
                                  disable TLS
       --hash-func=               Specify which hash function to use when
                                  calculating the hashes of produced files.
-                                 If no function has been specified, it does not
+                                 If no function has been specified, it does no
                                  happen. This permits avoiding downloading some
                                  files twice albeit at some performance cost.
                                  Possible values are: "", "SHA256".
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
       --http.config=""           [EXPERIMENTAL] Path to the configuration file
                                  that can enable TLS or authentication for all
                                  HTTP endpoints.
-      --label=<name>="<value>" ...  
+      --label=<name>="<value>" ...
                                  Labels to be applied to all generated metrics
                                  (repeated). Similar to external labels for
                                  Prometheus, used to identify ruler and its
@@ -367,19 +367,19 @@ Flags:
                                  LogStartAndFinishCall: Logs the start and
                                  finish call of the requests. NoLogCall: Disable
                                  request logging.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                  Alternative to 'objstore.config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains object store
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                 Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                 Path to YAML file that contains objec
                                  store configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
       --query=<query> ...        Addresses of statically configured query
                                  API servers (repeatable). The scheme may be
-                                 prefixed with 'dns+' or 'dnssrv+' to detect
+                                 prefixed with 'dns+' or 'dnssrv+' to detec
                                  query API servers through respective DNS
                                  lookups.
       --query.config=<content>   Alternative to 'query.config-file' flag
@@ -389,7 +389,7 @@ Flags:
                                  https://thanos.io/tip/components/rule.md/#configuration.
                                  If defined, it takes precedence over the
                                  '--query' and '--query.sd-files' flags.
-      --query.config-file=<file-path>  
+      --query.config-file=<file-path>
                                  Path to YAML file that contains query API
                                  servers configuration. See format details:
                                  https://thanos.io/tip/components/rule.md/#configuration.
@@ -400,17 +400,17 @@ Flags:
                                  restoration.
       --query.http-method=POST   HTTP method to use when sending queries.
                                  Possible options: [GET, POST]
-      --query.sd-dns-interval=30s  
+      --query.sd-dns-interval=30s
                                  Interval between DNS resolutions.
-      --query.sd-files=<path> ...  
+      --query.sd-files=<path> ...
                                  Path to file that contains addresses of query
                                  API servers. The path can be a glob pattern
                                  (repeatable).
       --query.sd-interval=5m     Refresh interval to re-read file SD files.
                                  (used as a fallback)
-      --remote-write.config=<content>  
+      --remote-write.config=<content>
                                  Alternative to 'remote-write.config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML config for the remote-write
                                  configurations, that specify servers
                                  where samples should be sent to (see
@@ -420,7 +420,7 @@ Flags:
                                  ruler's TSDB. If an empty config (or file) is
                                  provided, the flag is ignored and ruler is run
                                  with its own TSDB.
-      --remote-write.config-file=<file-path>  
+      --remote-write.config-file=<file-path>
                                  Path to YAML config for the remote-write
                                  configurations, that specify servers
                                  where samples should be sent to (see
@@ -430,19 +430,19 @@ Flags:
                                  ruler's TSDB. If an empty config (or file) is
                                  provided, the flag is ignored and ruler is run
                                  with its own TSDB.
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
       --resend-delay=1m          Minimum amount of time to wait before resending
                                  an alert to Alertmanager.
-      --restore-ignored-label=RESTORE-IGNORED-LABEL ...  
+      --restore-ignored-label=RESTORE-IGNORED-LABEL ...
                                  Label names to be ignored when restoring alerts
                                  from the remote storage. This is only used in
                                  stateless mode.
@@ -451,29 +451,29 @@ Flags:
                                  Note that rules are not automatically detected,
                                  use SIGHUP or do HTTP POST /-/reload to re-read
                                  them.
-      --shipper.upload-compacted  
+      --shipper.upload-compacted
                                  If true shipper will try to upload compacted
                                  blocks as well. Useful for migration purposes.
                                  Works only if compaction is disabled on
                                  Prometheus. Do it once and then disable the
                                  flag when done.
-      --store.limits.request-samples=0  
+      --store.limits.request-samples=0
                                  The maximum samples allowed for a single
                                  Series request, The Series call fails if
                                  this limit is exceeded. 0 means no limit.
                                  NOTE: For efficiency the limit is internally
                                  implemented as 'chunks limit' considering each
                                  chunk contains a maximum of 120 samples.
-      --store.limits.request-series=0  
+      --store.limits.request-series=0
                                  The maximum series allowed for a single Series
                                  request. The Series call fails if this limit is
                                  exceeded. 0 means no limit.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -487,11 +487,11 @@ Flags:
       --web.disable-cors         Whether to disable CORS headers to be set by
                                  Thanos. By default Thanos sets CORS headers to
                                  be allowed by all.
-      --web.external-prefix=""   Static prefix for all HTML links and redirect
+      --web.external-prefix=""   Static prefix for all HTML links and redirec
                                  URLs in the bucket web UI interface.
                                  Actual endpoints are still served on / or the
-                                 web.route-prefix. This allows thanos bucket
-                                 web UI to be served behind a reverse proxy that
+                                 web.route-prefix. This allows thanos bucke
+                                 web UI to be served behind a reverse proxy tha
                                  strips a URL sub-path.
       --web.prefix-header=""     Name of HTTP request header used for dynamic
                                  prefixing of UI links and redirects.
diff --git a/docs/components/sidecar.md b/docs/components/sidecar.md
index 13bde923ce3..9631b892a9b 100644
--- a/docs/components/sidecar.md
+++ b/docs/components/sidecar.md
@@ -33,19 +33,19 @@ You can configure watching for changes in directory via `--reloader.rule-dir=DIR
 
 Thanos sidecar can watch `--reloader.config-file=CONFIG_FILE` configuration file, replace environment variables found in there in `$(VARIABLE)` format, and produce generated config in `--reloader.config-envsubst-file=OUT_CONFIG_FILE` file.
 
-## Example basic deployment
+## Example basic deploymen
 
 ```bash
-prometheus \
-  --storage.tsdb.max-block-duration=2h \
-  --storage.tsdb.min-block-duration=2h \
+prometheus
+  --storage.tsdb.max-block-duration=2h
+  --storage.tsdb.min-block-duration=2h
   --web.enable-lifecycle
 ```
 
 ```bash
-thanos sidecar \
-    --tsdb.path        "/path/to/prometheus/data/dir" \
-    --prometheus.url   "http://localhost:9090" \
+thanos sidecar
+    --tsdb.path        "/path/to/prometheus/data/dir"
+    --prometheus.url   "http://localhost:9090"
     --objstore.config-file  "bucket.yml"
 ```
 
@@ -76,33 +76,33 @@ usage: thanos sidecar [<flags>]
 Sidecar for Prometheus server.
 
 Flags:
-      --grpc-address="0.0.0.0:10901"  
+      --grpc-address="0.0.0.0:10901"
                                  Listen ip:port address for gRPC endpoints
                                  (StoreAPI). Make sure this address is routable
                                  from other components.
       --grpc-grace-period=2m     Time to wait after an interrupt received for
                                  GRPC Server.
-      --grpc-server-max-connection-age=60m  
+      --grpc-server-max-connection-age=60m
                                  The grpc server max connection age. This
                                  controls how often to re-establish connections
                                  and redo TLS handshakes.
       --grpc-server-tls-cert=""  TLS Certificate for gRPC server, leave blank to
                                  disable TLS
-      --grpc-server-tls-client-ca=""  
+      --grpc-server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
       --grpc-server-tls-key=""   TLS Key for the gRPC server, leave blank to
                                  disable TLS
       --hash-func=               Specify which hash function to use when
                                  calculating the hashes of produced files.
-                                 If no function has been specified, it does not
+                                 If no function has been specified, it does no
                                  happen. This permits avoiding downloading some
                                  files twice albeit at some performance cost.
                                  Possible values are: "", "SHA256".
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
@@ -112,89 +112,89 @@ Flags:
       --log.format=logfmt        Log format to use. Possible options: logfmt or
                                  json.
       --log.level=info           Log filtering level.
-      --min-time=0000-01-01T00:00:00Z  
+      --min-time=0000-01-01T00:00:00Z
                                  Start of time range limit to serve. Thanos
                                  sidecar will serve only metrics, which happened
-                                 later than this value. Option can be a constant
+                                 later than this value. Option can be a constan
                                  time in RFC3339 format or time duration
                                  relative to current time, such as -1d or 2h45m.
                                  Valid duration units are ms, s, m, h, d, w, y.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                  Alternative to 'objstore.config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains object store
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                 Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                 Path to YAML file that contains objec
                                  store configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --prometheus.get_config_interval=30s  
+      --prometheus.get_config_interval=30s
                                  How often to get Prometheus config
-      --prometheus.get_config_timeout=5s  
+      --prometheus.get_config_timeout=5s
                                  Timeout for getting Prometheus config
-      --prometheus.http-client=<content>  
+      --prometheus.http-client=<content>
                                  Alternative to 'prometheus.http-client-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file or string with http
                                  client configs. See Format details:
                                  https://thanos.io/tip/components/sidecar.md/#configuration.
-      --prometheus.http-client-file=<file-path>  
+      --prometheus.http-client-file=<file-path>
                                  Path to YAML file or string with http
                                  client configs. See Format details:
                                  https://thanos.io/tip/components/sidecar.md/#configuration.
-      --prometheus.ready_timeout=10m  
+      --prometheus.ready_timeout=10m
                                  Maximum time to wait for the Prometheus
                                  instance to start up
-      --prometheus.url=http://localhost:9090  
+      --prometheus.url=http://localhost:9090
                                  URL at which to reach Prometheus's API.
                                  For better performance use local network.
-      --reloader.config-envsubst-file=""  
+      --reloader.config-envsubst-file=""
                                  Output file for environment variable
                                  substituted config file.
       --reloader.config-file=""  Config file watched by the reloader.
-      --reloader.retry-interval=5s  
+      --reloader.retry-interval=5s
                                  Controls how often reloader retries config
                                  reload in case of error.
-      --reloader.rule-dir=RELOADER.RULE-DIR ...  
+      --reloader.rule-dir=RELOADER.RULE-DIR ...
                                  Rule directories for the reloader to refresh
                                  (repeated field).
-      --reloader.watch-interval=3m  
+      --reloader.watch-interval=3m
                                  Controls how often reloader re-reads config and
                                  rules.
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --shipper.upload-compacted  
+      --shipper.upload-compacted
                                  If true shipper will try to upload compacted
                                  blocks as well. Useful for migration purposes.
                                  Works only if compaction is disabled on
                                  Prometheus. Do it once and then disable the
                                  flag when done.
-      --store.limits.request-samples=0  
+      --store.limits.request-samples=0
                                  The maximum samples allowed for a single
                                  Series request, The Series call fails if
                                  this limit is exceeded. 0 means no limit.
                                  NOTE: For efficiency the limit is internally
                                  implemented as 'chunks limit' considering each
                                  chunk contains a maximum of 120 samples.
-      --store.limits.request-series=0  
+      --store.limits.request-series=0
                                  The maximum series allowed for a single Series
                                  request. The Series call fails if this limit is
                                  exceeded. 0 means no limit.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -205,7 +205,7 @@ Flags:
 
 ## Configuration
 
-### Prometheus HTTP client
+### Prometheus HTTP clien
 
 You can configure the Prometheus HTTP client for Thanos sidecar with YAML, either by passing the YAML content directly to the `--prometheus.http-client` flag, or by passing the YAML file path to the `--prometheus.http-client-file` flag.
 
diff --git a/docs/components/store.md b/docs/components/store.md
index 11caf5b25c4..1758e24fd48 100644
--- a/docs/components/store.md
+++ b/docs/components/store.md
@@ -3,8 +3,8 @@
 The `thanos store` command (also known as Store Gateway) implements the Store API on top of historical data in an object storage bucket. It acts primarily as an API gateway and therefore does not need significant amounts of local disk space. It joins a Thanos cluster on startup and advertises the data it can access. It keeps a small amount of information about all remote blocks on local disk and keeps it in sync with the bucket. This data is generally safe to delete across restarts at the cost of increased startup times.
 
 ```bash
-thanos store \
-    --data-dir        "/local/state/data/dir" \
+thanos store
+    --data-dir        "/local/state/data/dir"
     --objstore.config-file "bucket.yml"
 ```
 
@@ -29,19 +29,19 @@ Store node giving access to blocks in a bucket provider. Now supported GCS, S3,
 Azure, Swift, Tencent COS and Aliyun OSS.
 
 Flags:
-      --block-meta-fetch-concurrency=32  
+      --block-meta-fetch-concurrency=32
                                  Number of goroutines to use when fetching block
                                  metadata from object storage.
-      --block-sync-concurrency=20  
+      --block-sync-concurrency=20
                                  Number of goroutines to use when constructing
                                  index-cache.json blocks from object storage.
                                  Must be equal or greater than 1.
-      --bucket-web-label=BUCKET-WEB-LABEL  
+      --bucket-web-label=BUCKET-WEB-LABEL
                                  External block label to use as group title in
                                  the bucket web UI
       --cache-index-header       Cache TSDB index-headers on disk to reduce
                                  startup time. When set to true, Thanos Store
-                                 will download index headers from remote object
+                                 will download index headers from remote objec
                                  storage on startup and create a header file on
                                  disk. Use --data-dir to set the directory in
                                  which index headers will be downloaded.
@@ -56,38 +56,38 @@ Flags:
                                  purposes (index-header, in-mem cache items and
                                  meta.jsons). If removed, no data will be lost,
                                  just store will have to rebuild the cache.
-                                 NOTE: Putting raw blocks here will not
+                                 NOTE: Putting raw blocks here will no
                                  cause the store to read them. For such use
                                  cases use Prometheus + sidecar. Ignored if
                                  --no-cache-index-header option is specified.
-      --grpc-address="0.0.0.0:10901"  
+      --grpc-address="0.0.0.0:10901"
                                  Listen ip:port address for gRPC endpoints
                                  (StoreAPI). Make sure this address is routable
                                  from other components.
       --grpc-grace-period=2m     Time to wait after an interrupt received for
                                  GRPC Server.
-      --grpc-server-max-connection-age=60m  
+      --grpc-server-max-connection-age=60m
                                  The grpc server max connection age. This
                                  controls how often to re-establish connections
                                  and redo TLS handshakes.
       --grpc-server-tls-cert=""  TLS Certificate for gRPC server, leave blank to
                                  disable TLS
-      --grpc-server-tls-client-ca=""  
+      --grpc-server-tls-client-ca=""
                                  TLS CA to verify clients against. If no
-                                 client CA is specified, there is no client
+                                 client CA is specified, there is no clien
                                  verification on server side. (tls.NoClientCert)
       --grpc-server-tls-key=""   TLS Key for the gRPC server, leave blank to
                                  disable TLS
   -h, --help                     Show context-sensitive help (also try
                                  --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                  Listen host:port for HTTP endpoints.
       --http-grace-period=2m     Time to wait after an interrupt received for
                                  HTTP Server.
       --http.config=""           [EXPERIMENTAL] Path to the configuration file
                                  that can enable TLS or authentication for all
                                  HTTP endpoints.
-      --ignore-deletion-marks-delay=24h  
+      --ignore-deletion-marks-delay=24h
                                  Duration after which the blocks marked for
                                  deletion will be filtered out while fetching
                                  blocks. The idea of ignore-deletion-marks-delay
@@ -102,7 +102,7 @@ Flags:
                                  be deleted rather than deleting the block
                                  straight away. If delete-delay is non-zero
                                  for compactor or bucket verify component,
-                                 ignore-deletion-marks-delay should be set
+                                 ignore-deletion-marks-delay should be se
                                  to (delete-delay)/2 so that blocks marked
                                  for deletion are filtered out while fetching
                                  blocks before being deleted from bucket.
@@ -111,54 +111,54 @@ Flags:
       --index-cache-size=250MB   Maximum size of items held in the in-memory
                                  index cache. Ignored if --index-cache.config or
                                  --index-cache.config-file option is specified.
-      --index-cache.config=<content>  
+      --index-cache.config=<content>
                                  Alternative to 'index-cache.config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains index cache
                                  configuration. See format details:
                                  https://thanos.io/tip/components/store.md/#index-cache
-      --index-cache.config-file=<file-path>  
+      --index-cache.config-file=<file-path>
                                  Path to YAML file that contains index
                                  cache configuration. See format details:
                                  https://thanos.io/tip/components/store.md/#index-cache
       --log.format=logfmt        Log format to use. Possible options: logfmt or
                                  json.
       --log.level=info           Log filtering level.
-      --max-time=9999-12-31T23:59:59Z  
+      --max-time=9999-12-31T23:59:59Z
                                  End of time range limit to serve. Thanos Store
                                  will serve only blocks, which happened earlier
                                  than this value. Option can be a constant time
                                  in RFC3339 format or time duration relative
                                  to current time, such as -1d or 2h45m. Valid
                                  duration units are ms, s, m, h, d, w, y.
-      --min-time=0000-01-01T00:00:00Z  
+      --min-time=0000-01-01T00:00:00Z
                                  Start of time range limit to serve. Thanos
                                  Store will serve only metrics, which happened
-                                 later than this value. Option can be a constant
+                                 later than this value. Option can be a constan
                                  time in RFC3339 format or time duration
                                  relative to current time, such as -1d or 2h45m.
                                  Valid duration units are ms, s, m, h, d, w, y.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                  Alternative to 'objstore.config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains object store
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                 Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                 Path to YAML file that contains objec
                                  store configuration. See format details:
                                  https://thanos.io/tip/thanos/storage.md/#configuration
-      --request.logging-config=<content>  
+      --request.logging-config=<content>
                                  Alternative to 'request.logging-config-file'
-                                 flag (mutually exclusive). Content
+                                 flag (mutually exclusive). Conten
                                  of YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --request.logging-config-file=<file-path>  
+      --request.logging-config-file=<file-path>
                                  Path to YAML file with request logging
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/logging.md/#configuration
-      --selector.relabel-config=<content>  
+      --selector.relabel-config=<content>
                                  Alternative to 'selector.relabel-config-file'
                                  flag (mutually exclusive). Content of
                                  YAML file that contains relabeling
@@ -166,47 +166,47 @@ Flags:
                                  blocks. It follows native Prometheus
                                  relabel-config syntax. See format details:
                                  https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
-      --selector.relabel-config-file=<file-path>  
+      --selector.relabel-config-file=<file-path>
                                  Path to YAML file that contains relabeling
                                  configuration that allows selecting
                                  blocks. It follows native Prometheus
                                  relabel-config syntax. See format details:
                                  https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
-      --store.enable-index-header-lazy-reader  
+      --store.enable-index-header-lazy-reader
                                  If true, Store Gateway will lazy memory map
                                  index-header only once the block is required by
                                  a query.
-      --store.grpc.downloaded-bytes-limit=0  
+      --store.grpc.downloaded-bytes-limit=0
                                  Maximum amount of downloaded (either
                                  fetched or touched) bytes in a single
                                  Series/LabelNames/LabelValues call. The Series
                                  call fails if this limit is exceeded. 0 means
                                  no limit.
-      --store.grpc.series-max-concurrency=20  
+      --store.grpc.series-max-concurrency=20
                                  Maximum number of concurrent Series calls.
-      --store.grpc.series-sample-limit=0  
+      --store.grpc.series-sample-limit=0
                                  DEPRECATED: use store.limits.request-samples.
-      --store.grpc.touched-series-limit=0  
+      --store.grpc.touched-series-limit=0
                                  DEPRECATED: use store.limits.request-series.
-      --store.limits.request-samples=0  
+      --store.limits.request-samples=0
                                  The maximum samples allowed for a single
                                  Series request, The Series call fails if
                                  this limit is exceeded. 0 means no limit.
                                  NOTE: For efficiency the limit is internally
                                  implemented as 'chunks limit' considering each
                                  chunk contains a maximum of 120 samples.
-      --store.limits.request-series=0  
+      --store.limits.request-series=0
                                  The maximum series allowed for a single Series
                                  request. The Series call fails if this limit is
                                  exceeded. 0 means no limit.
       --sync-block-duration=3m   Repeat interval for syncing the blocks between
                                  local and remote view.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                  Alternative to 'tracing.config-file' flag
                                  (mutually exclusive). Content of YAML file
                                  with tracing configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                  Path to YAML file with tracing
                                  configuration. See format details:
                                  https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -215,11 +215,11 @@ Flags:
       --web.disable-cors         Whether to disable CORS headers to be set by
                                  Thanos. By default Thanos sets CORS headers to
                                  be allowed by all.
-      --web.external-prefix=""   Static prefix for all HTML links and redirect
+      --web.external-prefix=""   Static prefix for all HTML links and redirec
                                  URLs in the bucket web UI interface.
                                  Actual endpoints are still served on / or the
-                                 web.route-prefix. This allows thanos bucket
-                                 web UI to be served behind a reverse proxy that
+                                 web.route-prefix. This allows thanos bucke
+                                 web UI to be served behind a reverse proxy tha
                                  strips a URL sub-path.
       --web.prefix-header=""     Name of HTTP request header used for dynamic
                                  prefixing of UI links and redirects.
@@ -393,7 +393,7 @@ Here is an example of what effect client-side caching could have:
   - `servername`: Override the server name used to validate the server certificate
   - `insecure_skip_verify`: Disable certificate verification
 
-## Caching Bucket
+## Caching Bucke
 
 Thanos Store Gateway supports a "caching bucket" with [chunks](../design.md#chunk) and metadata caching to speed up loading of [chunks](../design.md#chunk) from TSDB blocks. To configure caching, one needs to use `--store.caching-bucket.config=<yaml content>` or `--store.caching-bucket.config-file=<file.yaml>`.
 
diff --git a/docs/components/tools.md b/docs/components/tools.md
index 7c4c3c00a39..e65d9831d91 100644
--- a/docs/components/tools.md
+++ b/docs/components/tools.md
@@ -16,12 +16,12 @@ Flags:
                            --help-man).
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -84,7 +84,7 @@ Subcommands:
 
 ```
 
-## Bucket
+## Bucke
 
 The `thanos tools bucket` subcommand of Thanos is a set of commands to inspect data in object storage buckets. It is normally run as a standalone command to aid with troubleshooting.
 
@@ -116,21 +116,21 @@ Flags:
                            --help-man).
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                            Alternative to 'objstore.config-file' flag (mutually
                            exclusive). Content of YAML file that contains
                            object store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                           Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                           Path to YAML file that contains objec
                            store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -210,12 +210,12 @@ usage: thanos tools bucket web [<flags>]
 Web interface for remote storage bucket.
 
 Flags:
-      --disable-admin-operations  
+      --disable-admin-operations
                                 Disable UI/API admin operations like marking
                                 blocks for deletion and no compaction.
   -h, --help                    Show context-sensitive help (also try
                                 --help-long and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                                 Listen host:port for HTTP endpoints.
       --http-grace-period=2m    Time to wait after an interrupt received for
                                 HTTP Server.
@@ -226,7 +226,7 @@ Flags:
       --log.format=logfmt       Log format to use. Possible options: logfmt or
                                 json.
       --log.level=info          Log filtering level.
-      --max-time=9999-12-31T23:59:59Z  
+      --max-time=9999-12-31T23:59:59Z
                                 End of time range limit to serve. Thanos
                                 tool bucket web will serve only blocks,
                                 which happened earlier than this value. Option
@@ -234,26 +234,26 @@ Flags:
                                 duration relative to current time, such as -1d
                                 or 2h45m. Valid duration units are ms, s, m, h,
                                 d, w, y.
-      --min-time=0000-01-01T00:00:00Z  
+      --min-time=0000-01-01T00:00:00Z
                                 Start of time range limit to serve. Thanos
                                 tool bucket web will serve only blocks, which
                                 happened later than this value. Option can be a
                                 constant time in RFC3339 format or time duration
                                 relative to current time, such as -1d or 2h45m.
                                 Valid duration units are ms, s, m, h, d, w, y.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                 Alternative to 'objstore.config-file'
                                 flag (mutually exclusive). Content of
                                 YAML file that contains object store
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                Path to YAML file that contains objec
                                 store configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
       --refresh=30m             Refresh interval to download metadata from
                                 remote storage
-      --selector.relabel-config=<content>  
+      --selector.relabel-config=<content>
                                 Alternative to 'selector.relabel-config-file'
                                 flag (mutually exclusive). Content of
                                 YAML file that contains relabeling
@@ -261,19 +261,19 @@ Flags:
                                 blocks. It follows native Prometheus
                                 relabel-config syntax. See format details:
                                 https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
-      --selector.relabel-config-file=<file-path>  
+      --selector.relabel-config-file=<file-path>
                                 Path to YAML file that contains relabeling
                                 configuration that allows selecting
                                 blocks. It follows native Prometheus
                                 relabel-config syntax. See format details:
                                 https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config
       --timeout=5m              Timeout to download metadata from remote storage
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                 Alternative to 'tracing.config-file' flag
                                 (mutually exclusive). Content of YAML file
                                 with tracing configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                 Path to YAML file with tracing
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -281,11 +281,11 @@ Flags:
       --web.disable-cors        Whether to disable CORS headers to be set by
                                 Thanos. By default Thanos sets CORS headers to
                                 be allowed by all.
-      --web.external-prefix=""  Static prefix for all HTML links and redirect
+      --web.external-prefix=""  Static prefix for all HTML links and redirec
                                 URLs in the bucket web UI interface.
                                 Actual endpoints are still served on / or the
-                                web.route-prefix. This allows thanos bucket
-                                web UI to be served behind a reverse proxy that
+                                web.route-prefix. This allows thanos bucke
+                                web UI to be served behind a reverse proxy tha
                                 strips a URL sub-path.
       --web.prefix-header=""    Name of HTTP request header used for dynamic
                                 prefixing of UI links and redirects.
@@ -345,14 +345,14 @@ Flags:
       --id=ID ...          Block IDs to verify (and optionally repair) only.
                            If none is specified, all blocks will be verified.
                            Repeated field
-  -i, --issues=index_known_issues... ...  
+  -i, --issues=index_known_issues... ...
                            Issues to verify (and optionally repair). Possible
                            issue to verify, without repair: [overlapped_blocks];
                            Possible issue to verify and repair:
                            [index_known_issues duplicated_compaction]
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
-      --objstore-backup.config=<content>  
+      --objstore-backup.config=<content>
                            Alternative to 'objstore-backup.config-file'
                            flag (mutually exclusive). Content of YAML
                            file that contains object store-backup
@@ -360,29 +360,29 @@ Flags:
                            https://thanos.io/tip/thanos/storage.md/#configuration
                            Used for repair logic to backup blocks before
                            removal.
-      --objstore-backup.config-file=<file-path>  
-                           Path to YAML file that contains object
+      --objstore-backup.config-file=<file-path>
+                           Path to YAML file that contains objec
                            store-backup configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
                            Used for repair logic to backup blocks before
                            removal.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                            Alternative to 'objstore.config-file' flag (mutually
                            exclusive). Content of YAML file that contains
                            object store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                           Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                           Path to YAML file that contains objec
                            store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
   -r, --repair             Attempt to repair blocks for which issues were
                            detected
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -411,24 +411,24 @@ Flags:
                            --help-man).
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                            Alternative to 'objstore.config-file' flag (mutually
                            exclusive). Content of YAML file that contains
                            object store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                           Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                           Path to YAML file that contains objec
                            store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
   -o, --output=""          Optional format in which to print each block's
                            information. Options are 'json', 'wide' or a custom
                            template.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -436,7 +436,7 @@ Flags:
 
 ```
 
-### Bucket inspect
+### Bucket inspec
 
 `tools bucket inspect` is used to inspect buckets in a detailed way using stdout in ASCII table format.
 
@@ -457,19 +457,19 @@ Flags:
       --log.format=logfmt    Log format to use. Possible options: logfmt or
                              json.
       --log.level=info       Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                              Alternative to 'objstore.config-file'
                              flag (mutually exclusive). Content of
                              YAML file that contains object store
                              configuration. See format details:
                              https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                             Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                             Path to YAML file that contains objec
                              store configuration. See format details:
                              https://thanos.io/tip/thanos/storage.md/#configuration
       --output=table         Output format for result. Currently supports table,
                              cvs, tsv.
-  -l, --selector=<name>=\"<value>\" ...  
+  -l, --selector=<name>=\"<value>\" ...
                              Selects blocks based on label, e.g. '-l
                              key1=\"value1\" -l key2=\"value2\"'. All key value
                              pairs must match.
@@ -478,12 +478,12 @@ Flags:
                              UNTIL'. I.e., if the 'FROM' value is equal the rows
                              are then further sorted by the 'UNTIL' value.
       --timeout=5m           Timeout to download metadata from remote storage
-      --tracing.config=<content>  
+      --tracing.config=<content>
                              Alternative to 'tracing.config-file' flag
                              (mutually exclusive). Content of YAML file
                              with tracing configuration. See format details:
                              https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                              Path to YAML file with tracing
                              configuration. See format details:
                              https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -510,7 +510,7 @@ Replicate data from one object storage to another. NOTE: Currently it works only
 with Thanos blocks (meta.json has to have Thanos metadata).
 
 Flags:
-      --compaction=COMPACTION ...  
+      --compaction=COMPACTION ...
                               Only blocks with these compaction levels
                               will be replicated. Repeated flag. Overrides
                               compaction-min and compaction-max if set.
@@ -520,7 +520,7 @@ Flags:
                               will be replicated.
   -h, --help                  Show context-sensitive help (also try --help-long
                               and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                               Listen host:port for HTTP endpoints.
       --http-grace-period=2m  Time to wait after an interrupt received for HTTP
                               Server.
@@ -532,7 +532,7 @@ Flags:
                               matchers will be ignored. When specified, this
                               command will be run only once after successful
                               replication. Repeated field
-      --ignore-marked-for-deletion  
+      --ignore-marked-for-deletion
                               Do not replicate blocks that have deletion mark.
       --log.format=logfmt     Log format to use. Possible options: logfmt or
                               json.
@@ -540,51 +540,51 @@ Flags:
       --matcher=MATCHER       blocks whose external labels match this matcher
                               will be replicated. All Prometheus matchers are
                               supported, including =, !=, =~ and !~.
-      --max-time=9999-12-31T23:59:59Z  
+      --max-time=9999-12-31T23:59:59Z
                               End of time range limit to replicate. Thanos
                               Replicate will replicate only metrics, which
                               happened earlier than this value. Option can be a
                               constant time in RFC3339 format or time duration
                               relative to current time, such as -1d or 2h45m.
                               Valid duration units are ms, s, m, h, d, w, y.
-      --min-time=0000-01-01T00:00:00Z  
+      --min-time=0000-01-01T00:00:00Z
                               Start of time range limit to replicate. Thanos
                               Replicate will replicate only metrics, which
                               happened later than this value. Option can be a
                               constant time in RFC3339 format or time duration
                               relative to current time, such as -1d or 2h45m.
                               Valid duration units are ms, s, m, h, d, w, y.
-      --objstore-to.config=<content>  
+      --objstore-to.config=<content>
                               Alternative to 'objstore-to.config-file'
                               flag (mutually exclusive). Content of
                               YAML file that contains object store-to
                               configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
                               The object storage which replicate data to.
-      --objstore-to.config-file=<file-path>  
-                              Path to YAML file that contains object
+      --objstore-to.config-file=<file-path>
+                              Path to YAML file that contains objec
                               store-to configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
                               The object storage which replicate data to.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                               Alternative to 'objstore.config-file'
                               flag (mutually exclusive). Content of
                               YAML file that contains object store
                               configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                              Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                              Path to YAML file that contains objec
                               store configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
       --resolution=0s... ...  Only blocks with these resolutions will be
                               replicated. Repeated flag.
       --single-run            Run replication only one time, then exit.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                               Alternative to 'tracing.config-file' flag
                               (mutually exclusive). Content of YAML file
                               with tracing configuration. See format details:
                               https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                               Path to YAML file with tracing
                               configuration. See format details:
                               https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -597,8 +597,8 @@ Flags:
 `tools bucket downsample` is used to downsample blocks in an object store bucket as a service. It implements the downsample API on top of historical data in an object storage bucket.
 
 ```bash
-thanos tools bucket downsample \
-    --data-dir        "/local/state/data/dir" \
+thanos tools bucket downsample
+    --data-dir        "/local/state/data/dir"
     --objstore.config-file "bucket.yml"
 ```
 
@@ -618,13 +618,13 @@ usage: thanos tools bucket downsample [<flags>]
 Continuously downsamples blocks in an object store bucket.
 
 Flags:
-      --block-files-concurrency=1  
+      --block-files-concurrency=1
                               Number of goroutines to use when
-                              fetching/uploading block files from object
+                              fetching/uploading block files from objec
                               storage.
       --data-dir="./data"     Data directory in which to cache blocks and
                               process downsamplings.
-      --downsample.concurrency=1  
+      --downsample.concurrency=1
                               Number of goroutines to use when downsampling
                               blocks.
       --hash-func=            Specify which hash function to use when
@@ -635,7 +635,7 @@ Flags:
                               are: "", "SHA256".
   -h, --help                  Show context-sensitive help (also try --help-long
                               and --help-man).
-      --http-address="0.0.0.0:10902"  
+      --http-address="0.0.0.0:10902"
                               Listen host:port for HTTP endpoints.
       --http-grace-period=2m  Time to wait after an interrupt received for HTTP
                               Server.
@@ -645,22 +645,22 @@ Flags:
       --log.format=logfmt     Log format to use. Possible options: logfmt or
                               json.
       --log.level=info        Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                               Alternative to 'objstore.config-file'
                               flag (mutually exclusive). Content of
                               YAML file that contains object store
                               configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                              Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                              Path to YAML file that contains objec
                               store configuration. See format details:
                               https://thanos.io/tip/thanos/storage.md/#configuration
-      --tracing.config=<content>  
+      --tracing.config=<content>
                               Alternative to 'tracing.config-file' flag
                               (mutually exclusive). Content of YAML file
                               with tracing configuration. See format details:
                               https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                               Path to YAML file with tracing
                               configuration. See format details:
                               https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -676,7 +676,7 @@ Flags:
 NOTE: If the [Compactor](compact.md) is currently running and compacting exactly same block, this operation would be potentially a noop."
 
 ```bash
-thanos tools bucket mark \
+thanos tools bucket mark
     --id "01C8320GCGEWBZF51Q46TTQEH9" --id "01C8J352831FXGZQMN2NTJ08DY"
     --objstore.config-file "bucket.yml"
 ```
@@ -707,22 +707,22 @@ Flags:
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
       --marker=MARKER      Marker to be put.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                            Alternative to 'objstore.config-file' flag (mutually
                            exclusive). Content of YAML file that contains
                            object store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                           Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                           Path to YAML file that contains objec
                            store configuration. See format details:
                            https://thanos.io/tip/thanos/storage.md/#configuration
       --remove             Remove the marker.
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -737,13 +737,13 @@ Flags:
 For example we can remove all non counters from the block you have on your disk (e.g in Prometheus dir):
 
 ```bash
-thanos tools bucket rewrite --no-dry-run \
-  --id 01DN3SK96XDAEKRB1AN30AAW6E \
+thanos tools bucket rewrite --no-dry-run
+  --id 01DN3SK96XDAEKRB1AN30AAW6E
   --objstore.config "
 type: FILESYSTEM
 config:
   directory: <local dir>
-" \
+"
   --rewrite.to-delete-config "
 - matchers: \"{__name__!~\\\".*total\\\"}\"
 "
@@ -782,7 +782,7 @@ Flags:
                                 Pass --no-dry-run to skip this.
       --hash-func=              Specify which hash function to use when
                                 calculating the hashes of produced files.
-                                If no function has been specified, it does not
+                                If no function has been specified, it does no
                                 happen. This permits avoiding downloading some
                                 files twice albeit at some performance cost.
                                 Possible values are: "", "SHA256".
@@ -793,14 +793,14 @@ Flags:
       --log.format=logfmt       Log format to use. Possible options: logfmt or
                                 json.
       --log.level=info          Log filtering level.
-      --objstore.config=<content>  
+      --objstore.config=<content>
                                 Alternative to 'objstore.config-file'
                                 flag (mutually exclusive). Content of
                                 YAML file that contains object store
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
-      --objstore.config-file=<file-path>  
-                                Path to YAML file that contains object
+      --objstore.config-file=<file-path>
+                                Path to YAML file that contains objec
                                 store configuration. See format details:
                                 https://thanos.io/tip/thanos/storage.md/#configuration
       --prom-blocks             If specified, we assume the blocks to be
@@ -809,31 +809,31 @@ Flags:
       --rewrite.add-change-log  If specified, all modifications are written to
                                 new block directory. Disable if latency is to
                                 high.
-      --rewrite.to-delete-config=<content>  
+      --rewrite.to-delete-config=<content>
                                 Alternative to 'rewrite.to-delete-config-file'
                                 flag (mutually exclusive). Content of YAML file
-                                that contains []metadata.DeletionRequest that
+                                that contains []metadata.DeletionRequest tha
                                 will be applied to blocks
-      --rewrite.to-delete-config-file=<file-path>  
+      --rewrite.to-delete-config-file=<file-path>
                                 Path to YAML file that contains
                                 []metadata.DeletionRequest that will be applied
                                 to blocks
-      --rewrite.to-relabel-config=<content>  
+      --rewrite.to-relabel-config=<content>
                                 Alternative to 'rewrite.to-relabel-config-file'
                                 flag (mutually exclusive). Content of YAML
                                 file that contains relabel configs that will be
                                 applied to blocks
-      --rewrite.to-relabel-config-file=<file-path>  
+      --rewrite.to-relabel-config-file=<file-path>
                                 Path to YAML file that contains relabel configs
                                 that will be applied to blocks
-      --tmp.dir="/var/folders/yn/c6y00yq11klbr1pk_92j61580000gn/T/thanos-rewrite"  
+      --tmp.dir="/var/folders/yn/c6y00yq11klbr1pk_92j61580000gn/T/thanos-rewrite"
                                 Working directory for temporary files
-      --tracing.config=<content>  
+      --tracing.config=<content>
                                 Alternative to 'tracing.config-file' flag
                                 (mutually exclusive). Content of YAML file
                                 with tracing configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                                 Path to YAML file with tracing
                                 configuration. See format details:
                                 https://thanos.io/tip/thanos/tracing.md/#configuration
@@ -868,12 +868,12 @@ Flags:
       --log.format=logfmt  Log format to use. Possible options: logfmt or json.
       --log.level=info     Log filtering level.
       --rules=RULES ...    The rule files glob to check (repeated).
-      --tracing.config=<content>  
+      --tracing.config=<content>
                            Alternative to 'tracing.config-file' flag
                            (mutually exclusive). Content of YAML file
                            with tracing configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
-      --tracing.config-file=<file-path>  
+      --tracing.config-file=<file-path>
                            Path to YAML file with tracing
                            configuration. See format details:
                            https://thanos.io/tip/thanos/tracing.md/#configuration
diff --git a/docs/contributing/coding-style-guide.md b/docs/contributing/coding-style-guide.md
index b50983d62b7..96fb96ad57f 100644
--- a/docs/contributing/coding-style-guide.md
+++ b/docs/contributing/coding-style-guide.md
@@ -922,13 +922,13 @@ It's very easy to forget to add Prometheus metrics (e.g a `prometheus.Counter`)
 
 Ensured [here](https://github.com/thanos-io/thanos/blob/40526f52f54d4501737e5246c0e71e56dd7e0b2d/Makefile#L308).
 
-#### go vet
+#### go ve
 
 Standard Go vet is quite strict, but for a good reason. Always vet your Go code!
 
 Ensured [here](https://github.com/thanos-io/thanos/blob/40526f52f54d4501737e5246c0e71e56dd7e0b2d/Makefile#L313).
 
-#### golangci-lint
+#### golangci-lin
 
 [golangci-lint](https://github.com/golangci/golangci-lint) is an amazing tool that allows running a set of different custom linters from the Go community against your code. Give it a star and use it. (:
 
diff --git a/docs/contributing/how-to-contribute-to-docs.md b/docs/contributing/how-to-contribute-to-docs.md
index 857c8023436..beba8f76dbd 100644
--- a/docs/contributing/how-to-contribute-to-docs.md
+++ b/docs/contributing/how-to-contribute-to-docs.md
@@ -94,7 +94,7 @@ To test the changes to the docs locally just start serving the website by runnin
 make web-serve
 ```
 
-## Deployment
+## Deploymen
 
 We use [Netlify](https://www.netlify.com/) for hosting. We are using Open Source license (PRO). Thanks Netlify for this!
 
diff --git a/docs/contributing/mentorship.md b/docs/contributing/mentorship.md
index 5fb0f501ede..c160307a5c2 100644
--- a/docs/contributing/mentorship.md
+++ b/docs/contributing/mentorship.md
@@ -14,7 +14,7 @@ Programs we participated / are participating:
 
 You have been selected for mentorship with Prometheus or Thanos? Congratulations! Here is some short quick information for a quick start!
 
-### Onboarding Check List
+### Onboarding Check Lis
 
 - [X] Please see and acknowledge our [Code of Conduct](../../CODE_OF_CONDUCT.md). A similar one is for the Prometheus project. TL;DR: Be nice and friendly!
 - [X] Create an account on the [CNCF Slack](https://slack.cncf.io/). Please add any profile photo to make it unique. (: This is Thanos's main chat provider. You can reach any of the mentors there.
diff --git a/docs/design.md b/docs/design.md
index 1b6ba731fab..a594fe656fa 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -141,7 +141,7 @@ For example, rule sets can be divided across multiple HA pairs of rule nodes. St
 
 Overall, first-class horizontal sharding is possible but will not be considered for the time being since there's no evidence that it is required in practical setups.
 
-## Cost
+## Cos
 
 The only extra cost Thanos adds to an existing Prometheus setup is essentially the price of storing and querying data from the object storage and running of the `store` node.
 
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 0b6f9667d1f..b6f2f4f1e33 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -43,7 +43,7 @@ Thanos uses the directive *replace*. The reason is to provide a way to unblock o
 If you want to build Thanos from source you would need a working installation of the Go 1.18+ [toolchain](https://github.com/golang/tools) (`GOPATH`, `PATH=${GOPATH}/bin:${PATH}`). Next one should make a clone of our repository:
 
 ```
-git clone git@github.com:thanos-io/thanos.git
+git clone git@github.com:thanos-io/thanos.gi
 ```
 
 When you have access to the source code locally, we have prepared a `Makefile`. Invoke this by using `make` in your CLI. For example `make help` will list all options. For building Thanos one could use `make build`
@@ -156,7 +156,7 @@ See up to date [jsonnet mixins](https://github.com/thanos-io/thanos/tree/main/mi
 
 See [Integrations page](integrations.md).
 
-## Testing Thanos on Single Host
+## Testing Thanos on Single Hos
 
 We don't recommend running Thanos on a single node on production. Thanos is designed and built to run as a distributed system. Vanilla Prometheus might be totally enough for small setups.
 
diff --git a/docs/operating/binary-index-header.md b/docs/operating/binary-index-header.md
index 1ab548073ee..b500862c163 100644
--- a/docs/operating/binary-index-header.md
+++ b/docs/operating/binary-index-header.md
@@ -53,7 +53,7 @@ The table of contents serves as an entry point to the entire index and points to
 └─────────────────────────────────────────┘
 ```
 
-## How the index-header is built
+## How the index-header is buil
 
 The [Store Gateway](../components/store.md) periodically scans the bucket to look for new and deleted blocks. For each new block found, the Gateway stores the index-header on the local disk, building it with specific sections of the block's index downloaded using GET byte range requests.
 
diff --git a/docs/operating/cross-cluster-tls-communication.md b/docs/operating/cross-cluster-tls-communication.md
index 77d370f7f51..17cb6e24a8d 100644
--- a/docs/operating/cross-cluster-tls-communication.md
+++ b/docs/operating/cross-cluster-tls-communication.md
@@ -35,7 +35,7 @@ Envoy can be implemented as a sidecar container (example shown here) within the
 You may need to change cluster.local depending on your cluster domain. The `--store` entries for thanos storegateway etc. may be named different in your setup
 
 ```yaml
-kind: Deployment
+kind: Deploymen
 apiVersion: apps/v1
 metadata:
   name: thanos-global-test-querier
@@ -111,7 +111,7 @@ metadata:
             failureThreshold: 3
           terminationMessagePath: /dev/termination-log
           terminationMessagePolicy: File
-          imagePullPolicy: IfNotPresent
+          imagePullPolicy: IfNotPresen
           securityContext:
             privileged: false
             runAsUser: 1001
@@ -143,10 +143,10 @@ metadata:
               mountPropagation: None
           terminationMessagePath: /dev/termination-log
           terminationMessagePolicy: File
-          imagePullPolicy: IfNotPresent
+          imagePullPolicy: IfNotPresen
       restartPolicy: Always
       terminationGracePeriodSeconds: 30
-      dnsPolicy: ClusterFirst
+      dnsPolicy: ClusterFirs
       serviceAccountName: thanos-global-test-querier-sa
       serviceAccount: thanos-global-test-querier-sa
       automountServiceAccountToken: false
@@ -224,7 +224,7 @@ static_resources:
       common_tls_context:
         validation_context:
           trusted_ca:
-            filename: /certs/ca.crt
+            filename: /certs/ca.cr
         alpn_protocols:
         - h2
         - http/1.1
@@ -240,7 +240,7 @@ static_resources:
       common_tls_context:
         validation_context:
           trusted_ca:
-            filename: /certs/ca.crt
+            filename: /certs/ca.cr
         alpn_protocols:
         - h2
         - http/1.1
@@ -274,7 +274,7 @@ static_resources:
           - name: envoy.access_loggers.file
             typed_config:
               "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
-              path: /dev/stdout
+              path: /dev/stdou
               log_format:
                 text_format: |
                   [%START_TIME%] "%REQ(:METHOD)% %REQ(X-ENVOY-ORIGINAL-PATH?:PATH)% %PROTOCOL%"
@@ -284,7 +284,7 @@ static_resources:
           - name: envoy.access_loggers.file
             typed_config:
               "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
-              path: /dev/stdout
+              path: /dev/stdou
           stat_prefix: ingress_http
           route_config:
             name: local_route
@@ -318,11 +318,11 @@ static_resources:
     transport_socket:
       name: envoy.transport_sockets.tls
       typed_config:
-        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
+        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContex
         common_tls_context:
           tls_certificates:
             - certificate_chain:
-                filename: /certs/tls.crt
+                filename: /certs/tls.cr
               private_key:
                 filename: /certs/tls.key
           validation_context:
diff --git a/docs/operating/https.md b/docs/operating/https.md
index 93fa5b398e9..52b50e7256e 100644
--- a/docs/operating/https.md
+++ b/docs/operating/https.md
@@ -73,7 +73,7 @@ An example configuration file is provided below,
 ```yaml
 # A certificate and a key file are needed.
 tls_server_config:
-  cert_file: server.crt
+  cert_file: server.cr
   key_file: server.key
 
 # Usernames and passwords required to connect to Thanos.
diff --git a/docs/proposals-accepted/202012-deletions-object-storage.md b/docs/proposals-accepted/202012-deletions-object-storage.md
index 090cdbbb67e..05a9e9da28d 100644
--- a/docs/proposals-accepted/202012-deletions-object-storage.md
+++ b/docs/proposals-accepted/202012-deletions-object-storage.md
@@ -73,7 +73,7 @@ The main motivation for considering deletions in the object storage are the foll
 * Pros: Does have quick access to querying or block indexes
 * Cons: There would be many writers, and store never was about to write things, it only needed read access
 
-#### How we store the tombstone and in what format
+#### How we store the tombstone and in what forma
 
 1. Prometheus Format per block
 2. Prometheus Format global
diff --git a/docs/proposals-accepted/202106-automated-per-endpoint-mTLS.md b/docs/proposals-accepted/202106-automated-per-endpoint-mTLS.md
index c3f9b3cf734..92425654e78 100644
--- a/docs/proposals-accepted/202106-automated-per-endpoint-mTLS.md
+++ b/docs/proposals-accepted/202106-automated-per-endpoint-mTLS.md
@@ -16,7 +16,7 @@ menu: proposals-accepted
 
   * [Per-Store TLS configuration in Thanos Query](https://github.com/thanos-io/thanos/issues/977)
 
-## What
+## Wha
 
 The Thanos Querier component supports basic mTLS configuration for internal gRPC communication. This works great for basic use cases but it still requires extra forward proxies to make it work for bigger deployments. It’s also hard to rotate certificates automatically and configure safe mTLS. This proposal aims to allow a better TLS story.
 
@@ -37,7 +37,7 @@ So it requires extra forward proxies to make it work for bigger (multi-cluster)
 ## Goals
 
 * To add support for per-endpoint TLS configuration in Thanos Query Component for internal gRPC communication
-* Automatic certificate rotation without restart
+* Automatic certificate rotation without restar
 
 ## Non-Goals
 
diff --git a/docs/proposals-accepted/202108-more-granular-query-performance-metrics.md b/docs/proposals-accepted/202108-more-granular-query-performance-metrics.md
index 04d1690617d..e609dc4fc26 100644
--- a/docs/proposals-accepted/202108-more-granular-query-performance-metrics.md
+++ b/docs/proposals-accepted/202108-more-granular-query-performance-metrics.md
@@ -114,7 +114,7 @@ Due to the limitations of the prom Querier API, we can instead use the reporter
 
 **tl;dr:** Longer term to capture the entire query path by amending the Prometheus Querier API to return some stats alongside the query, and creating this generic metric inside the Prometheus PromQL engine. Short term, pass a func parameter to the Queryable constructor for the proxy StoreAPI querier that will exfiltrate the `SeriesStats`, circumventing PromQL engine.
 
-### Measuring Thanos Query Latency with respect to query fanout
+### Measuring Thanos Query Latency with respect to query fanou
 
 First we would create a new `SeriesQueryPerformanceCalculator` for aggregating/tracking the `SeriesStatsCounters` for each fanned out query
 
@@ -157,7 +157,7 @@ func (s *SeriesQueryPerformanceMetricsAggregator) Observe(duration float64) {
 }
 
 // Determine the appropriate bucket for a given value relative to a set of quantiles
-func (s *SeriesQueryPerformanceMetricsAggregator) findBucket(value int, quantiles *[]float64) int
+func (s *SeriesQueryPerformanceMetricsAggregator) findBucket(value int, quantiles *[]float64) in
 ```
 
 Current query fanout logic:
@@ -178,7 +178,7 @@ for _, st := range s.stores() {
 type seriesServer struct {
 	// This field just exist to pseudo-implement the unused methods of the interface.
 	storepb.Store_SeriesServer
-	ctx context.Context
+	ctx context.Contex
 
 	seriesSet      []storepb.Series
 	seriesSetStats storepb.SeriesStatsCounter
@@ -262,10 +262,10 @@ Injecting the reporter into the qapi Queryable static constructor:
 ```
 
 In summary, we will:
-* Amend the `seriesServer` to keep track of all `SeriesStats` for each series pushed to it
+* Amend the `seriesServer` to keep track of all `SeriesStats` for each series pushed to i
 * Amend the static `qapi.queryableCreate` to take a `SeriesStatsReporter` func parameter that will exfiltrate the seriesStats from the Thanos Proxy StoreAPI
 * Add new runtime flags that will allow us to specify a) Query time quantiles b) Series size quantiles c) Sample size quantiles for our partitioned histogram
-* Start a query duration timer as soon as the handler is hit
+* Start a query duration timer as soon as the handler is hi
 * Create a new partitioned vector histogram called `thanos_query_duration_seconds` in the `queryRange` API handler
 * Propagate all exfiltrated `SeriesStats` to aforementioned metric
 * Record observations against the `thanos_query_duration_seconds` histogram after bucketing samples_le/series_le buckets
diff --git a/docs/proposals-accepted/202206-active-series-limiting-hashring.md b/docs/proposals-accepted/202206-active-series-limiting-hashring.md
index 8d88cbb339c..c1d69761b5f 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 write request
+* [Request-based limiting](https://github.com/thanos-io/thanos/issues/5404), i.e, number of samples in a remote write reques
 * 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
 
@@ -84,12 +84,12 @@ So if a user configures a *per-tenant* limit, say `globalSeriesLimit`, the resul
 
 #### 8.1.1 Pros:
 
-* Simpler as compared to other solutions and easier to implement
+* Simpler as compared to other solutions and easier to implemen
 * Lesser endpoint calls, so improved latency
 * Relies on "external to Thanos" system, and doesn’t increase load on Receive
 * Does not add much tenancy-based complexity to Thanos
 * No need to merge statistics across replicas, handled by meta-monitoring
-* Additional request-based rate limiting can be done within same component
+* Additional request-based rate limiting can be done within same componen
 * In case, external meta-monitoring solution is down, can fall back to per-replica-tenant limits
 * Growing our instrumentation to improve validator, improves our observability as well
 * Easy to iterate. We can move out of meta-monitoring to different standalone solution if needed later on.
@@ -98,7 +98,7 @@ So if a user configures a *per-tenant* limit, say `globalSeriesLimit`, the resul
 
 * Not very accurate
   * We do not know exact state of each TSDB, only know view of meta-monitoring solution, which gets updated on every scrape
-  * We do not account for how much a remote write request will increase the number of active series, only infer that from query result after the fact
+  * We do not account for how much a remote write request will increase the number of active series, only infer that from query result after the fac
 * Data replication (quorum-based) will likely cause inaccuracies in HEAD stat metrics
 * Dependence on an external meta-monitoring system that is Prometheus API compatible. It's fairly easy and reliable with local Prometheus setup, but if the user uses 3rd party system like central remote monitoring, this might be less trivial to setup.
 
@@ -129,7 +129,7 @@ This approach would add validation logic within Receive Router, which we can cal
 The implementation would be as follows,
 
 * Implement configuration option for global series limit (which would be the same for each tenant initially) i.e `globalSeriesLimit`
-* Implement validation logic in Receive Router mode, which can recognize other Receive replicas and call the `api/v1/status/tsdb` endpoint on each replica with `all_tenants=true` query parameter and merge the count of active series i.e `currentSeries` of a tenant
+* Implement validation logic in Receive Router mode, which can recognize other Receive replicas and call the `api/v1/status/tsdb` endpoint on each replica with `all_tenants=true` query parameter and merge the count of active series i.e `currentSeries` of a tenan
 * Implement an endpoint in Receive, `api/v1/getrefmap`, which when provided with a tenant id and a remote write request returns a map of SeriesRef and labelsets
 * We can then merge this with maps from other replicas, and get the number of series for which `SeriesRef == 0` for all replicas. This is the increase in the number of active series if the remote write request is ingested i.e `increaseOnRequest`. For example,
 
@@ -164,11 +164,11 @@ message SeriesRefMap {
 
 * Would result in more accurate measurements to limit on, however data replication would still make `api/v1/status/tsdb` [inaccurate](https://github.com/thanos-io/thanos/pull/5402#discussion_r893434246)
   * It considers the exact amount of current active series for a tenant as it calls status API each time
-  * It considers how much the number of active series would increase after a remote write request
-* No new TSDB-related changes, it utilizes interfaces that are already present
-* Simple proxy-like solution, as an optional component
+  * It considers how much the number of active series would increase after a remote write reques
+* No new TSDB-related changes, it utilizes interfaces that are already presen
+* Simple proxy-like solution, as an optional componen
 * Does not change existing way in which Receive nodes communicate with each other
-* Additional request-based rate limiting can be done within same component
+* Additional request-based rate limiting can be done within same componen
 
 #### 9.1.2 Cons:
 
@@ -201,8 +201,8 @@ The option of using gRPC instead of two API calls each time is also valid here.
 
 * Would result in more accurate measurements to limit on however data replication would still make `api/v1/status/tsdb` [inaccurate](https://github.com/thanos-io/thanos/pull/5402#discussion_r893434246)
   * It considers the exact amount of active series for a tenant as it calls status API each time
-  * It considers how much the number of active series would increase after a remote write request
-* No new TSDB-related changes, it utilizes interfaces that are already present
+  * It considers how much the number of active series would increase after a remote write reques
+* No new TSDB-related changes, it utilizes interfaces that are already presen
 
 #### 9.2.2 Cons:
 
diff --git a/docs/proposals-accepted/202209-receive-tenant-external-labels.md b/docs/proposals-accepted/202209-receive-tenant-external-labels.md
index b36c668151d..3220defd686 100644
--- a/docs/proposals-accepted/202209-receive-tenant-external-labels.md
+++ b/docs/proposals-accepted/202209-receive-tenant-external-labels.md
@@ -65,7 +65,7 @@ For the tests, the foremost ones are testing defining one or multiple tenants’
 ## 8 Implementation plan
 
 * Add a new `external_labels` field in the hashring config
-* Allow MultiTSDB to extend external labels to each corresponding tenant's label set
+* Allow MultiTSDB to extend external labels to each corresponding tenant's label se
 * Allow MultiTSDB to update each tenant's label set whenever its external labels change
 * Handle external labels in soft tenancy cases
 * Implement tenants’ external labels in RouterOnly
diff --git a/docs/proposals-accepted/20221129-avoid-global-sort.md b/docs/proposals-accepted/20221129-avoid-global-sort.md
index 1a56a74140d..71aa197ebfb 100644
--- a/docs/proposals-accepted/20221129-avoid-global-sort.md
+++ b/docs/proposals-accepted/20221129-avoid-global-sort.md
@@ -1,12 +1,12 @@
 ---
 type: proposal
-title: Avoid Global Sort on Querier Select
+title: Avoid Global Sort on Querier Selec
 status: approved
 owner: bwplotka,fpetkovski
 menu: proposals-accepted
 ---
 
-## Avoid Global Sort on Querier Select
+## Avoid Global Sort on Querier Selec
 
 * **Related Tickets:**
   * https://github.com/thanos-io/thanos/issues/5719
@@ -144,7 +144,7 @@ Cons:
 * Feels hacky. Proper way for preserving this information would be like alternative 4.
 * Debuggability might be not needed here - YAGNI
 
-4. Replica label struct
+4. Replica label struc
 
 We could make Store API response fully replica aware. This means that series response will now include an extra slice of replica labels that this series belongs to:
 
diff --git a/docs/proposals-done/201812-thanos-remote-receive.md b/docs/proposals-done/201812-thanos-remote-receive.md
index f72b078bada..084fbd26376 100644
--- a/docs/proposals-done/201812-thanos-remote-receive.md
+++ b/docs/proposals-done/201812-thanos-remote-receive.md
@@ -18,7 +18,7 @@ This component is only recommended for uses for whom pushing is the only viable
 
 This component is not recommended in order to achieve a global view of data of a single tenant, for those cases the sidecar based approach with layered Thanos queriers is recommended. Also, users are asked to note the [various pros and cons of pushing metrics](https://docs.google.com/document/d/1H47v7WfyKkSLMrR8_iku6u9VB73WrVzBHb2SB6dL9_g/edit#heading=h.2v27snv0lsur). Multi tenancy may also be achievable if ingestion is not user controlled, as then enforcing of labels, for example using the [prom-label-proxy](https://github.com/openshift/prom-label-proxy) (please thoroughly understand the mechanism if intending to employ this mechanism, as wrong configuration could leak data).
 
-## Technical summary of Thanos receiver component
+## Technical summary of Thanos receiver componen
 
 To solve the above mentioned problems, a new Thanos component is proposed: the Thanos receiver.
 
diff --git a/docs/proposals-done/201912-thanos-binary-index-header.md b/docs/proposals-done/201912-thanos-binary-index-header.md
index e016ce3da38..f1a0bb7823b 100644
--- a/docs/proposals-done/201912-thanos-binary-index-header.md
+++ b/docs/proposals-done/201912-thanos-binary-index-header.md
@@ -36,7 +36,7 @@ The `sync` process includes:
     * Download the whole TSDB index file, mmap all of it.
     * Build index-cache.json
   * else:
-    * Download index-cache.json from bucket
+    * Download index-cache.json from bucke
   * Delete downloaded TSDB index.
 * Load whole index-cache.json to memory and keep it for lifetime of the block.
 
diff --git a/docs/proposals-done/202001-thanos-query-health-handling.md b/docs/proposals-done/202001-thanos-query-health-handling.md
index 9585ec5cc73..fb95feb87c7 100644
--- a/docs/proposals-done/202001-thanos-query-health-handling.md
+++ b/docs/proposals-done/202001-thanos-query-health-handling.md
@@ -45,7 +45,7 @@ Lets look through their pros and cons:
 
 If we were to graph these choices in terms of their incisiveness and complexity it would look something like this:
 
-```text
+```tex
 Most incisive / Least Complex ------------ Least incisive / Most Complex
 #1           #2                                      #4
            #3    #5
diff --git a/docs/proposals-done/202003-thanos-rules-federation.md b/docs/proposals-done/202003-thanos-rules-federation.md
index c33bd98f1a9..eacd6300a09 100644
--- a/docs/proposals-done/202003-thanos-rules-federation.md
+++ b/docs/proposals-done/202003-thanos-rules-federation.md
@@ -84,7 +84,7 @@ As specified, the rule type and then rule name is used for deduplication.
 
 Given the following stream of incoming rule groups and containing recording/alerting rules:
 
-```text
+```tex
 group: a
    recording:<name:"r1" last_evaluation:<seconds:1 > >
    alert:    <name:"a1" last_evaluation:<seconds:1 > >
@@ -96,7 +96,7 @@ group: a
 
 The output becomes:
 
-```text
+```tex
 group: a
    alert:    <name:"a1" last_evaluation:<seconds:1 > >
    recording:<name:"r1" last_evaluation:<seconds:1 > >
@@ -113,7 +113,7 @@ The next level of deduplication is governed by the label/value set of the underl
 
 Given the following stream of incoming recording rules:
 
-```text
+```tex
 group: a
    recording:<name:"r1" labels:<labels:<name:"replica" value:"thanos-ruler-1" > > last_evaluation:<2006-01-02T10:00:00> >
 group: a
@@ -122,14 +122,14 @@ group: a
 
 The output becomes:
 
-```text
+```tex
 group: a
    recording:<name:"r1" labels:<labels:<name:"replica" value:"thanos-ruler-2" > > last_evaluation:<2006-01-02T10:01:00> >
 ```
 
 Given the following stream of incoming alerting rules:
 
-```text
+```tex
 group: a
    alert:<state:FIRING name:"a1" labels:<labels:<name:"replica" value:"thanos-ruler-1" > > last_evaluation:<2006-01-02T10:00:00> >
 group: a
@@ -138,7 +138,7 @@ group: a
 
 The output becomes:
 
-```text
+```tex
 group: a
    alert:<state:FIRING name:"a1" labels:<labels:<name:"replica" value:"thanos-ruler-1" > > last_evaluation:<2006-01-02T10:00:00> >
 ```
@@ -151,10 +151,10 @@ If, under the above conditions a rule is a candidate for deduplication, finally
 
 Given the following stream of incoming alerting rules will also result in two independent alerting rules as both the `expr` and `for` fields differ:
 
-```text
+```tex
   - alert: KubeAPIErrorBudgetBurn
     annotations:
-      message: The API server is burning too much error budget
+      message: The API server is burning too much error budge
     expr: |
       sum(apiserver_request:burnrate1h) > (14.40 * 0.01000)
       and
@@ -164,7 +164,7 @@ Given the following stream of incoming alerting rules will also result in two in
       severity: critical
   - alert: KubeAPIErrorBudgetBurn
     annotations:
-      message: The API server is burning too much error budget
+      message: The API server is burning too much error budge
     expr: |
       sum(apiserver_request:burnrate6h) > (6.00 * 0.01000)
       and
@@ -180,7 +180,7 @@ As specified, the group name and file fields are used for deduplication.
 
 Given the following stream of incoming rule groups:
 
-```text
+```tex
 group: a/file1
 group: b/file1
 group: a/file2
@@ -188,7 +188,7 @@ group: a/file2
 
 The output becomes:
 
-```text
+```tex
 group: a/file1
 group: a/file2
 group: b/file1
diff --git a/docs/proposals-done/202005-query-logging.md b/docs/proposals-done/202005-query-logging.md
index 9894fa2be31..d77e8b63edf 100644
--- a/docs/proposals-done/202005-query-logging.md
+++ b/docs/proposals-done/202005-query-logging.md
@@ -213,7 +213,7 @@ type ActiveQueryLogging struct {
 	// mmapped file to store the queries.
 	mmappedFile []byte
 	// channel to generate the next available index, much like Python’s generator indexing
-	getNextIndex chan int
+	getNextIndex chan in
 	// logger, different from the usual one
 	logger log.Logger
 }
@@ -221,7 +221,7 @@ type ActiveQueryLogging struct {
 
 This interface is designed with some ideas from a similar interface designed for *Prometheus Query Logger*[[2]](https://prometheus.io/docs/guides/query-log/). Here is a rough algorithm that would implement the Query Logging in Thanos -
 
-```txt
+```tx
 1) Thanos receives a query.
 2) It calls the index_generator, which is a Python-style generator that will generate natural numbers from 0(or 1) indicating the byte index at which to put the information about the query in the log file. This would ensure that the key remains unique for each of the queries logged.
 3) The log file would be a memory-mapped file, which would help in accessing a random position for logging the query in constant time.
diff --git a/docs/proposals-done/202005-scalable-rule-storage.md b/docs/proposals-done/202005-scalable-rule-storage.md
index b3f48ccd2b6..f3bdbb431c9 100644
--- a/docs/proposals-done/202005-scalable-rule-storage.md
+++ b/docs/proposals-done/202005-scalable-rule-storage.md
@@ -31,7 +31,7 @@ Allow specifying one of the following flags:
 
 * `--remote-write`
 * `--remote-write.config` or `--remote-write.config-file` flag following the same scheme as [`--query.config`, and `--query.config-file`](../components/rule.md#query-api)
-* `--remote-write.tenant-label-name` which label-value to use to set the tenant to be communicated to the receive component
+* `--remote-write.tenant-label-name` which label-value to use to set the tenant to be communicated to the receive componen
 
 If any of these are specified the ruler would run a stateless mode, without local storage, and instead writing samples to the configured remote server, which must implement the `storepb.WritableStore` gRPC service.
 
diff --git a/docs/proposals-done/202005-version-documentation.md b/docs/proposals-done/202005-version-documentation.md
index 830dc6d2c51..6f593cb7fdf 100644
--- a/docs/proposals-done/202005-version-documentation.md
+++ b/docs/proposals-done/202005-version-documentation.md
@@ -66,7 +66,7 @@ We want to propose a method called "Directory Sub Branching". Directory Sub bran
 
 ```|- website
     |- archetypes
-    |- layout
+    |- layou
     |- data
     |- static
     |- resources
@@ -79,7 +79,7 @@ We want to add an additional `versioned` folder within the website's `tmp` direc
 
 ```|- website
     |- archetypes
-    |- layout
+    |- layou
     |- data
     |- static
     |- resources
@@ -134,7 +134,7 @@ We could have this file on master, so the current `make web` will
 1. Parse `docs.yaml` from master and use this as a default.
 2. Check out each release (e.g. `release-0.10`)
 3. Is there docs.yaml?
-   * Yes - parse the file and use it
+   * Yes - parse the file and use i
    * No - use docs.yaml from master
 
 The design of docs.yaml will look like this:
diff --git a/docs/proposals-rejected/201807-config.md b/docs/proposals-rejected/201807-config.md
index f9a58359b70..0a0c3e940be 100644
--- a/docs/proposals-rejected/201807-config.md
+++ b/docs/proposals-rejected/201807-config.md
@@ -93,11 +93,11 @@ Currently we have the use case whereby a customer can deploy a game into our env
 The config component will read one or many Prometheus configuration files and dynamically allocate configuration to sidecars within the cluster. It initially joins a Thanos cluster mesh and can therefore find sidecars that it wishes to assign configuration.
 
 ```
-$ thanos config \
-    --http-address     "0.0.0.0:9090" \
-    --grpc-address     "0.0.0.0:9091" \
-    --cluster.peers    "thanos-cluster.example.org" \
-    --config           "promA.yaml;promB.yaml" \
+$ thanos config
+    --http-address     "0.0.0.0:9090"
+    --grpc-address     "0.0.0.0:9091"
+    --cluster.peers    "thanos-cluster.example.org"
+    --config           "promA.yaml;promB.yaml"
 ```
 
 The configuration supplied to the config component will then be distributed to the peers that config is aware of and exposed via a gRPC API so that each sidecar can get its configuration. The gRPC endpoint will take a request from a sidecar and based on the sidecar making the request it will give back the computed configuration.
@@ -113,12 +113,12 @@ With the addition of `thanos config` we will look to update the `thanos sidecar`
 To do this the sidecar will need to know the location of the config component to get its configuration.
 
 ```
-$ thanos sidecar \
-    --tsdb.path        "/path/to/prometheus/data/dir" \
-    --prometheus.url   "http://localhost:9090" \
-    --gcs.bucket       "example-bucket" \
-    --cluster.peers    "thanos-cluster.example.org" \
-    --config.url       "thanos-cluster.config.org" \
+$ thanos sidecar
+    --tsdb.path        "/path/to/prometheus/data/dir"
+    --prometheus.url   "http://localhost:9090"
+    --gcs.bucket       "example-bucket"
+    --cluster.peers    "thanos-cluster.example.org"
+    --config.url       "thanos-cluster.config.org"
 ```
 
 ### Client/Server Backwards/Forwards compatibility
diff --git a/docs/quick-tutorial.md b/docs/quick-tutorial.md
index c3455f9742e..f55e89e6a42 100644
--- a/docs/quick-tutorial.md
+++ b/docs/quick-tutorial.md
@@ -65,7 +65,7 @@ Sidecar makes use of Prometheus's `reload` endpoint. Make sure it's enabled with
 The following configures Sidecar to write Prometheus's data into a configured object storage bucket:
 
 ```bash
-thanos sidecar \
+thanos sidecar
     --tsdb.path            /var/prometheus \          # TSDB data directory of Prometheus
     --prometheus.url       "http://localhost:9090" \  # Be sure that Sidecar can use this URL!
     --objstore.config-file bucket_config.yaml \       # Storage configuration for uploading data
@@ -88,8 +88,8 @@ The Sidecar component implements and exposes a gRPC *[Store API](https://github.
 Let's extend the Sidecar from the previous section to connect to a Prometheus server, and expose the Store API:
 
 ```bash
-thanos sidecar \
-    --tsdb.path                 /var/prometheus \
+thanos sidecar
+    --tsdb.path                 /var/prometheus
     --objstore.config-file      bucket_config.yaml \       # Bucket config file to send data to
     --prometheus.url            http://localhost:9090 \    # Location of the Prometheus HTTP server
     --http-address              0.0.0.0:19191 \            # HTTP endpoint for collecting metrics on Sidecar
@@ -113,7 +113,7 @@ Every Prometheus instance must have a globally unique set of identifying labels.
 ```yaml
 global:
   external_labels:
-    region: eu-west
+    region: eu-wes
     monitor: infrastructure
     replica: A
 ```
@@ -129,7 +129,7 @@ Thanos Querier also implements Prometheus's official HTTP API and can thus be us
 Below, we will set up a Thanos Querier to connect to our Sidecars, and expose its HTTP UI:
 
 ```bash
-thanos query \
+thanos query
     --http-address 0.0.0.0:19192 \                                # HTTP Endpoint for Thanos Querier UI
     --endpoint     1.2.3.4:19090 \                                # Static gRPC Store API Address for the query node to query
     --endpoint     1.2.3.5:19090 \                                # Also repeatable
@@ -149,7 +149,7 @@ A typical configuration uses the label name "replica" with whatever value you ch
 ```yaml
 global:
   external_labels:
-    region: eu-west
+    region: eu-wes
     monitor: infrastructure
     replica: A
 # ...
@@ -160,10 +160,10 @@ In a Kubernetes stateful deployment, the replica label can also be the pod name.
 Ensure your Prometheus instances have been reloaded with the configuration you defined above. Then, in Thanos Querier, we will define `replica` as the label we want to enable deduplication on:
 
 ```bash
-thanos query \
-    --http-address        0.0.0.0:19192 \
-    --endpoint            1.2.3.4:19090 \
-    --endpoint            1.2.3.5:19090 \
+thanos query
+    --http-address        0.0.0.0:19192
+    --endpoint            1.2.3.4:19090
+    --endpoint            1.2.3.5:19090
     --query.replica-label replica          # Replica label for deduplication
     --query.replica-label replicaX         # Supports multiple replica labels for deduplication
 ```
@@ -179,7 +179,7 @@ The only required communication between nodes is for a Thanos Querier to be able
 There are various ways to tell Thanos Querier about the Store APIs it should query data from. The simplest way is to use a static list of well known addresses to query. These are repeatable, so you can add as many endpoints as you need. You can also put a DNS domain prefixed by `dns+` or `dnssrv+` to have a Thanos Querier do an `A` or `SRV` lookup to get all the required IPs it should communicate with.
 
 ```bash
-thanos query \
+thanos query
     --http-address 0.0.0.0:19192 \              # Endpoint for Thanos Querier UI
     --grpc-address 0.0.0.0:19092 \              # gRPC endpoint for Store API
     --endpoint     1.2.3.4:19090 \              # Static gRPC Store API Address for the query node to query
@@ -196,7 +196,7 @@ Read more details [here](service-discovery.md).
 As Thanos Sidecar backs up data into the object storage bucket of your choice, you can decrease Prometheus's retention in order to store less data locally. However, we need a way to query all that historical data again. Store Gateway does just that, by implementing the same gRPC data API as Sidecar, but backing it with data it can find in your object storage bucket. Just like sidecars and query nodes, Store Gateway exposes a Store API and needs to be discovered by Thanos Querier.
 
 ```bash
-thanos store \
+thanos store
     --data-dir             /var/thanos/store \   # Disk space for local caches
     --objstore.config-file bucket_config.yaml \  # Bucket to fetch data from
     --http-address         0.0.0.0:19191 \       # HTTP endpoint for collecting metrics on the Store Gateway
@@ -216,7 +216,7 @@ A local Prometheus installation periodically compacts older data to improve quer
 Thanos Compactor simply scans the object storage bucket and performs compaction where required. At the same time, it is responsible for creating downsampled copies of data in order to speed up queries.
 
 ```bash
-thanos compact \
+thanos compac
     --data-dir             /var/thanos/compact \  # Temporary workspace for data processing
     --objstore.config-file bucket_config.yaml \   # Bucket where compacting will be performed
     --http-address         0.0.0.0:19191          # HTTP endpoint for collecting metrics on the compactor
diff --git a/docs/storage.md b/docs/storage.md
index 24634ad3c77..d406b0c0864 100644
--- a/docs/storage.md
+++ b/docs/storage.md
@@ -1,4 +1,4 @@
-# Object Storage & Data Format
+# Object Storage & Data Forma
 
 Thanos uses object storage as primary storage for metrics and metadata related to them. In this document you can learn how to configure your object storage and what is the data layout and format for primary Thanos components that are "block" aware, like: `sidecar` `compact`, `receive` and `store gateway`.
 
@@ -125,7 +125,7 @@ Set `list_objects_version: "v1"` for S3 compatible APIs that don't support ListO
 
 `bucket_lookup_type` can be `auto`, `virtual-hosted` or `path`. Read more about it [here](https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html).
 
-For debug and testing purposes you can set
+For debug and testing purposes you can se
 
 * `insecure: true` to switch to plain insecure HTTP instead of HTTPS
 
@@ -247,7 +247,7 @@ With this policy you should be able to run set `THANOS_TEST_OBJSTORE_SKIP=GCS,AZ
 
 Details about AWS policies: https://docs.aws.amazon.com/AmazonS3/latest/dev/using-with-s3-actions.html
 
-##### STS Endpoint
+##### STS Endpoin
 
 If you want to use IAM credential retrieved from an instance profile, Thanos needs to authenticate through AWS STS. For this purposes you can specify your own STS Endpoint.
 
@@ -297,7 +297,7 @@ Application credentials are configured via JSON file and only the bucket needs t
 
 You can read more on how to get application credential json file in [https://cloud.google.com/docs/authentication/production](https://cloud.google.com/docs/authentication/production)
 
-##### Using inline a Service Account
+##### Using inline a Service Accoun
 
 Another possibility is to inline the ServiceAccount into the Thanos configuration and only maintain one file. This feature was added, so that the Prometheus Operator only needs to take care of one secret file.
 
@@ -394,7 +394,7 @@ If `user_assigned_id` is used, authentication is done via user-assigned managed
 
 The generic `max_retries` will be used as value for the `pipeline_config`'s `max_tries` and `reader_config`'s `max_retry_requests`. For more control, `max_retries` could be ignored (0) and one could set specific retry values.
 
-#### OpenStack Swift
+#### OpenStack Swif
 
 Thanos uses [ncw/swift](https://github.com/ncw/swift) client to upload Prometheus data into [OpenStack Swift](https://docs.openstack.org/swift/latest/).
 
@@ -1055,7 +1055,7 @@ The table of contents serves as an entry point to the entire index and points to
 └─────────────────────────────────────────┘
 ```
 
-#### Chunks File Format
+#### Chunks File Forma
 
 > NOTE: Currently supported index file versions: v1.
 
diff --git a/examples/alerts/alerts.md b/examples/alerts/alerts.md
index caa89ad0ef4..fb55e2c4123 100644
--- a/examples/alerts/alerts.md
+++ b/examples/alerts/alerts.md
@@ -5,7 +5,7 @@ Here are some example alerts configured for Kubernetes environment.
 ## Compaction
 
 ```yaml mdox-exec="cat examples/tmp/thanos-compact.yaml"
-name: thanos-compact
+name: thanos-compac
 rules:
 - alert: ThanosCompactMultipleRunning
   annotations:
@@ -572,7 +572,7 @@ rules:
   expr: |
     (
       sum by (job) (rate(thanos_replicate_replication_runs_total{result="error", job=~".*thanos-bucket-replicate.*"}[5m]))
-    / on (job) group_left
+    / on (job) group_lef
       sum by (job) (rate(thanos_replicate_replication_runs_total{job=~".*thanos-bucket-replicate.*"}[5m]))
     ) * 100 >= 10
   for: 5m
@@ -599,7 +599,7 @@ rules:
 ### Absent Rules
 
 ```yaml mdox-exec="cat examples/tmp/thanos-component-absent.yaml"
-name: thanos-component-absent
+name: thanos-component-absen
 rules:
 - alert: ThanosCompactIsDown
   annotations:
diff --git a/mixin/README.md b/mixin/README.md
index 53eb23bf481..52a0cd992b0 100644
--- a/mixin/README.md
+++ b/mixin/README.md
@@ -10,7 +10,7 @@ The content of this project is written in [jsonnet](http://jsonnet.org/). This p
 
 ## Requirements
 
-### jsonnet
+### jsonne
 
 The content of this project consists of a set of [jsonnet](http://jsonnet.org/) files making up a library to be consumed.
 
@@ -19,7 +19,7 @@ We recommend to use [go-jsonnet](https://github.com/google/go-jsonnet). It's an
 To install:
 
 ```shell
-go get github.com/google/go-jsonnet/cmd/jsonnet
+go get github.com/google/go-jsonnet/cmd/jsonne
 ```
 
 ### jsonnet-bundler
@@ -136,7 +136,7 @@ This project is intended to be used as a library. You can extend and customize d
 You can format your code using:
 
 ```shell
-$ make jsonnet-format
+$ make jsonnet-forma
 ```
 
 ## Examples
@@ -180,7 +180,7 @@ Make action runs the jsonnet code, then reads each key of the generated json and
 You validate your structural correctness of your Prometheus [alerting rules](https://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/) or [recording rules](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/) with:
 
 ```shell
-$ make example-rules-lint
+$ make example-rules-lin
 ```
 
 Check out [test.yaml](../examples/alerts/tests.yaml) to add/modify tests for the mixin. To learn more about how to write test for Prometheus, check out [official documentation](https://www.prometheus.io/docs/prometheus/latest/configuration/unit_testing_rules/).
@@ -188,7 +188,7 @@ Check out [test.yaml](../examples/alerts/tests.yaml) to add/modify tests for the
 You test alerts with:
 
 ```shell
-$ make alerts-test
+$ make alerts-tes
 ```
 
 ---
diff --git a/mixin/runbook.md b/mixin/runbook.md
index 48c9a5ada0f..ac5578ca1e3 100755
--- a/mixin/runbook.md
+++ b/mixin/runbook.md
@@ -18,7 +18,7 @@
 |ThanosBucketReplicateErrorRate|Thanos Replicate is failing to run.|Thanos Replicate is failing to run, {{$value  humanize}}% of attempts failed.|critical|[https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanosbucketreplicateerrorrate](https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanosbucketreplicateerrorrate)|
 |ThanosBucketReplicateRunLatency|Thanos Replicate has a high latency for replicate operations.|Thanos Replicate {{$labels.job}} has a 99th percentile latency of {{$value}} seconds for the replicate operations.|critical|[https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanosbucketreplicaterunlatency](https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanosbucketreplicaterunlatency)|
 
-## thanos-compact
+## thanos-compac
 
 |Name|Summary|Description|Severity|Runbook|
 |---|---|---|---|---|
@@ -28,7 +28,7 @@
 |ThanosCompactBucketHighOperationFailures|Thanos Compact Bucket is having a high number of operation failures.|Thanos Compact {{$labels.job}} Bucket is failing to execute {{$value  humanize}}% of operations.|warning|[https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanoscompactbuckethighoperationfailures](https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanoscompactbuckethighoperationfailures)|
 |ThanosCompactHasNotRun|Thanos Compact has not uploaded anything for last 24 hours.|Thanos Compact {{$labels.job}} has not uploaded anything for 24 hours.|warning|[https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanoscompacthasnotrun](https://github.com/thanos-io/thanos/tree/main/mixin/runbook.md#alert-name-thanoscompacthasnotrun)|
 
-## thanos-component-absent
+## thanos-component-absen
 
 |Name|Summary|Description|Severity|Runbook|
 |---|---|---|---|---|
diff --git a/pkg/ui/react-app/README.md b/pkg/ui/react-app/README.md
index 836fcbedaca..06a925ac2b2 100755
--- a/pkg/ui/react-app/README.md
+++ b/pkg/ui/react-app/README.md
@@ -8,7 +8,7 @@ The [React-based](https://reactjs.org/) Thanos UI was bootstrapped using [Create
 
 Instead of plain JavaScript, we use [TypeScript](https://www.typescriptlang.org/) to ensure typed code.
 
-## Development environment
+## Development environmen
 
 To work with the React UI code, you will need to have the following tools installed:
 
@@ -30,7 +30,7 @@ npm consults the `package.json` and `package-lock.json` files for dependencies t
 
 You can start a development server for the React UI outside of a running Thanos server by running:
 
-    npm start
+    npm star
 
 This will open a browser window with the React app running on http://localhost:3000/. The page will reload if you make edits to the source code. You will also see any lint errors in the console.
 
@@ -42,7 +42,7 @@ Due to a `"proxy": "http://localhost:10902"` setting in the `package.json` file,
 
 Create React App uses the [Jest](https://jestjs.io/) framework for running tests. To run tests in interactive watch mode:
 
-    npm test
+    npm tes
 
 To generate an HTML-based test coverage report, run:
 
@@ -60,7 +60,7 @@ We define linting rules for the [ESLint](https://eslint.org/) linter. We recomme
 
 To detect and automatically fix lint errors, run:
 
-    npm run lint
+    npm run lin
 
 This is also available via the `react-app-lint-fix` target in the main Thanos `Makefile`.
 
diff --git a/tutorials/killercoda/README.md b/tutorials/killercoda/README.md
index caacae6d30c..3872fab7515 100644
--- a/tutorials/killercoda/README.md
+++ b/tutorials/killercoda/README.md
@@ -2,7 +2,7 @@
 
 Our interactive, in-browser tutorials are available under https://killercoda.com/thanos.
 
-## Development
+## Developmen
 
 Process of adding / editing tutorials:
 
diff --git a/tutorials/kubernetes-helm/README.md b/tutorials/kubernetes-helm/README.md
index b11da9c4be8..ac523759a43 100644
--- a/tutorials/kubernetes-helm/README.md
+++ b/tutorials/kubernetes-helm/README.md
@@ -56,7 +56,7 @@ server:
             operator: In
             values:
             - prometheus
-          - key: component
+          - key: componen
             operator: In
             values:
             - server
@@ -95,8 +95,8 @@ server:
     volumeMounts:
     - name: storage-volume
       mountPath: /data
-    - name: thanos-storage-secret
-      mountPath: /etc/secret
+    - name: thanos-storage-secre
+      mountPath: /etc/secre
     - name: config-volume
       mountPath: /etc/prometheus-config
       readOnly: false
@@ -128,11 +128,11 @@ server:
       prometheus_replica: '$(HOSTNAME)'
     evaluation_interval: 5s
   extraSecretMounts:
-  - name: thanos-storage-secret
+  - name: thanos-storage-secre
     mountPath: /etc/secret/
     subPath: sa
     readOnly: false
-    secretName: thanos-storage-secret
+    secretName: thanos-storage-secre
 
 configmapReload:
   image: