From 43835704b7674bc4b01d9cc08a09280d4ecdd55b Mon Sep 17 00:00:00 2001 From: yudrywet <166895665+yudrywet@users.noreply.github.com> Date: Tue, 16 Apr 2024 15:48:52 +0800 Subject: [PATCH] chore: fix some typos in comments (#6103) Signed-off-by: yudrywet --- README.md | 4 ++-- docs/README.md | 4 ++-- docs/Release-Guide.md | 2 +- docs/Single-server-VictoriaMetrics.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index fced4745c..90d17bfb1 100644 --- a/README.md +++ b/README.md @@ -116,7 +116,7 @@ VictoriaMetrics ecosystem contains the following components additionally to [sin - [vmalert](https://docs.victoriametrics.com/vmalert/) - a service for processing Prometheus-compatible alerting and recording rules. - [vmalert-tool](https://docs.victoriametrics.com/vmalert-tool/) - a tool for validating alerting and recording rules. - [vmauth](https://docs.victoriametrics.com/vmauth/) - authorization proxy and load balancer optimized for VictoriaMetrics products. -- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - auhtorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. +- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - authorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. - [vmctl](https://docs.victoriametrics.com/vmctl/) - a tool for migrating and copying data between different storage systems for metrics. - [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmrestore](https://docs.victoriametrics.com/vmrestore/) and [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/) - tools for creating backups and restoring from backups for VictoriaMetrics data. @@ -2417,7 +2417,7 @@ It is also possible removing [rollup result cache](#rollup-result-cache) on star ## Rollup result cache -VictoriaMetrics caches query reponses by default. This allows increasing performance for repated queries +VictoriaMetrics caches query responses by default. This allows increasing performance for repated queries to [`/api/v1/query`](https://docs.victoriametrics.com/keyconcepts/#instant-query) and [`/api/v1/query_range`](https://docs.victoriametrics.com/keyconcepts/#range-query) with the increasing `time`, `start` and `end` query args. diff --git a/docs/README.md b/docs/README.md index d10bef10b..e30f3f499 100644 --- a/docs/README.md +++ b/docs/README.md @@ -119,7 +119,7 @@ VictoriaMetrics ecosystem contains the following components additionally to [sin - [vmalert](https://docs.victoriametrics.com/vmalert/) - a service for processing Prometheus-compatible alerting and recording rules. - [vmalert-tool](https://docs.victoriametrics.com/vmalert-tool/) - a tool for validating alerting and recording rules. - [vmauth](https://docs.victoriametrics.com/vmauth/) - authorization proxy and load balancer optimized for VictoriaMetrics products. -- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - auhtorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. +- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - authorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. - [vmctl](https://docs.victoriametrics.com/vmctl/) - a tool for migrating and copying data between different storage systems for metrics. - [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmrestore](https://docs.victoriametrics.com/vmrestore/) and [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/) - tools for creating backups and restoring from backups for VictoriaMetrics data. @@ -2420,7 +2420,7 @@ It is also possible removing [rollup result cache](#rollup-result-cache) on star ## Rollup result cache -VictoriaMetrics caches query reponses by default. This allows increasing performance for repated queries +VictoriaMetrics caches query responses by default. This allows increasing performance for repated queries to [`/api/v1/query`](https://docs.victoriametrics.com/keyconcepts/#instant-query) and [`/api/v1/query_range`](https://docs.victoriametrics.com/keyconcepts/#range-query) with the increasing `time`, `start` and `end` query args. diff --git a/docs/Release-Guide.md b/docs/Release-Guide.md index 3620bcc97..f73bf55b3 100644 --- a/docs/Release-Guide.md +++ b/docs/Release-Guide.md @@ -52,7 +52,7 @@ Bumping the limits may significantly improve build speed. Ideally, every change must be documented in the commit with the change. Alternatively, the change must be documented immediately after the commit, which adds the change. 1. Make sure all the changes are synced between `master`, `cluster`, `enterprise-single-node` and `enteprise-cluster` branches. - Changes in these branches must be synced immediately after they are commited in at least a single branch. + Changes in these branches must be synced immediately after they are committed in at least a single branch. 1. Make sure that the release branches have no security issues. 1. Update release versions if needed in [SECURITY.md](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/SECURITY.md). 1. Add `(available starting from v1.xx.y)` line to feature docs introduced in the upcoming release. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index c5e1d24eb..51f29ce50 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -127,7 +127,7 @@ VictoriaMetrics ecosystem contains the following components additionally to [sin - [vmalert](https://docs.victoriametrics.com/vmalert/) - a service for processing Prometheus-compatible alerting and recording rules. - [vmalert-tool](https://docs.victoriametrics.com/vmalert-tool/) - a tool for validating alerting and recording rules. - [vmauth](https://docs.victoriametrics.com/vmauth/) - authorization proxy and load balancer optimized for VictoriaMetrics products. -- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - auhtorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. +- [vmgateway](https://docs.victoriametrics.com/vmgateway/) - authorization proxy with per-[tenant](https://docs.victoriametrics.com/cluster-victoriametrics/#multitenancy) rate limiting cababilities. - [vmctl](https://docs.victoriametrics.com/vmctl/) - a tool for migrating and copying data between different storage systems for metrics. - [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmrestore](https://docs.victoriametrics.com/vmrestore/) and [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/) - tools for creating backups and restoring from backups for VictoriaMetrics data. @@ -2428,7 +2428,7 @@ It is also possible removing [rollup result cache](#rollup-result-cache) on star ## Rollup result cache -VictoriaMetrics caches query reponses by default. This allows increasing performance for repated queries +VictoriaMetrics caches query responses by default. This allows increasing performance for repated queries to [`/api/v1/query`](https://docs.victoriametrics.com/keyconcepts/#instant-query) and [`/api/v1/query_range`](https://docs.victoriametrics.com/keyconcepts/#range-query) with the increasing `time`, `start` and `end` query args.