fixing docs ci

.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?

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.

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.
 

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.

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.
 

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
 

docs/blog/2022-09-08-thanos-at-medallia.md

@@ -20,15 +20,15 @@ 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.
 
 Observability is largely a practice of capturing a variety of health and performance signals from software and hardware, ingesting those signals into appropriate data storage systems, and providing tools for analysis and alerting on that data. Analogously, Medallia captures feedback signals from its customers’ customers and employees, ingests those signals into its data storage systems, and provides analysis and alerting tools for use by its customers.
 
 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:
 

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