all: consistency renaming Victoria Metrics -> VictoriaMetrics

VMInsert -> vminsert
VMSelect -> vmselect
VMStorage -> vmstorage

README.md

@@ -8,7 +8,7 @@
 [![Build Status](https://github.com/VictoriaMetrics/VictoriaMetrics/workflows/main/badge.svg)](https://github.com/VictoriaMetrics/VictoriaMetrics/actions)
 [![codecov](https://codecov.io/gh/VictoriaMetrics/VictoriaMetrics/branch/master/graph/badge.svg)](https://codecov.io/gh/VictoriaMetrics/VictoriaMetrics)
 
-<img src="logo.png" width="300" alt="Victoria Metrics logo">
+<img src="logo.png" width="300" alt="VictoriaMetrics logo">
 
 VictoriaMetrics is a fast, cost-effective and scalable monitoring solution and time series database.
 
@@ -166,7 +166,7 @@ Alphabetically sorted links to case studies:
 * [Contacts](#contacts)
 * [Community and contributions](#community-and-contributions)
 * [Reporting bugs](#reporting-bugs)
-* [Victoria Metrics Logo](#victoria-metrics-logo)
+* [VictoriaMetrics Logo](#victoria-metrics-logo)
   * [Logo Usage Guidelines](#logo-usage-guidelines)
     * [Font used](#font-used)
     * [Color Palette](#color-palette)
@@ -1528,7 +1528,7 @@ Adhering `KISS` principle simplifies the resulting code and architecture, so it
 Report bugs and propose new features [here](https://github.com/VictoriaMetrics/VictoriaMetrics/issues).
 
 
-## Victoria Metrics Logo
+## VictoriaMetrics Logo
 
 [Zip](VM_logo.zip) contains three folders with different image orientations (main color and inverted version).
 

app/vmalert/README.md

@@ -164,11 +164,11 @@ For recording rules to work `-remoteWrite.url` must specified.
 
 `vmalert` has no local storage, so alerts state is stored in the process memory. Hence, after reloading of `vmalert`
 the process alerts state will be lost. To avoid this situation, `vmalert` should be configured via the following flags:
-* `-remoteWrite.url` - URL to VictoriaMetrics (Single) or VMInsert (Cluster). `vmalert` will persist alerts state
+* `-remoteWrite.url` - URL to VictoriaMetrics (Single) or vminsert (Cluster). `vmalert` will persist alerts state
 into the configured address in the form of time series named `ALERTS` and `ALERTS_FOR_STATE` via remote-write protocol.
 These are regular time series and may be queried from VM just as any other time series.
 The state stored to the configured address on every rule evaluation.
-* `-remoteRead.url` - URL to VictoriaMetrics (Single) or VMSelect (Cluster). `vmalert` will try to restore alerts state
+* `-remoteRead.url` - URL to VictoriaMetrics (Single) or vmselect (Cluster). `vmalert` will try to restore alerts state
 from configured address by querying time series with name `ALERTS_FOR_STATE`.
 
 Both flags are required for the proper state restoring. Restore process may fail if time series are missing
@@ -201,7 +201,7 @@ to set `-datasource.appendTypePrefix` flag to `true`, so vmalert can adjust URL
 The shortlist of configuration flags is the following:
 ```
   -datasource.appendTypePrefix
-    	Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the VMSelect URL.
+    	Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the vmselect URL.
   -datasource.basicAuth.password string
     	Optional basic auth password for -datasource.url
   -datasource.basicAuth.username string
@@ -223,7 +223,7 @@ The shortlist of configuration flags is the following:
   -datasource.tlsServerName string
     	Optional TLS server name to use for connections to -datasource.url. By default, the server name from -datasource.url is used
   -datasource.url string
-    	Victoria Metrics or VMSelect url. Required parameter. E.g. http://127.0.0.1:8428
+    	VictoriaMetrics or vmselect url. Required parameter. E.g. http://127.0.0.1:8428
   -dryRun -rule
     	Whether to check only config files without running vmalert. The rules file are validated. The -rule flag must be specified.
   -enableTCP6
@@ -326,7 +326,7 @@ The shortlist of configuration flags is the following:
   -remoteRead.tlsServerName string
     	Optional TLS server name to use for connections to -remoteRead.url. By default the server name from -remoteRead.url is used
   -remoteRead.url vmalert
-    	Optional URL to Victoria Metrics or VMSelect that will be used to restore alerts state. This configuration makes sense only if vmalert was configured with `remoteWrite.url` before and has been successfully persisted its state. E.g. http://127.0.0.1:8428
+    	Optional URL to VictoriaMetrics or vmselect that will be used to restore alerts state. This configuration makes sense only if vmalert was configured with `remoteWrite.url` before and has been successfully persisted its state. E.g. http://127.0.0.1:8428
   -remoteWrite.basicAuth.password string
     	Optional basic auth password for -remoteWrite.url
   -remoteWrite.basicAuth.username string
@@ -350,7 +350,7 @@ The shortlist of configuration flags is the following:
   -remoteWrite.tlsServerName string
     	Optional TLS server name to use for connections to -remoteWrite.url. By default the server name from -remoteWrite.url is used
   -remoteWrite.url string
-    	Optional URL to Victoria Metrics or VMInsert where to persist alerts state and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428
+    	Optional URL to VictoriaMetrics or vminsert where to persist alerts state and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428
   -rule array
     	Path to the file with alert rules.
     	Supports patterns. Flag can be specified multiple times.

app/vmalert/datasource/init.go

@@ -9,9 +9,9 @@ import (
 )
 
 var (
-	addr = flag.String("datasource.url", "", "Victoria Metrics or VMSelect url. Required parameter."+
+	addr = flag.String("datasource.url", "", "VictoriaMetrics or vmselect url. Required parameter. "+
-		" E.g. http://127.0.0.1:8428")
+		"E.g. http://127.0.0.1:8428")
-	appendTypePrefix  = flag.Bool("datasource.appendTypePrefix", false, "Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the VMSelect URL.")
+	appendTypePrefix  = flag.Bool("datasource.appendTypePrefix", false, "Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the vmselect URL.")
 	basicAuthUsername = flag.String("datasource.basicAuth.username", "", "Optional basic auth username for -datasource.url")
 	basicAuthPassword = flag.String("datasource.basicAuth.password", "", "Optional basic auth password for -datasource.url")
 

app/vmalert/remoteread/init.go

@@ -10,9 +10,9 @@ import (
 )
 
 var (
-	addr = flag.String("remoteRead.url", "", "Optional URL to Victoria Metrics or VMSelect that will be used to restore alerts"+
+	addr = flag.String("remoteRead.url", "", "Optional URL to VictoriaMetrics or vmselect that will be used to restore alerts "+
-		" state. This configuration makes sense only if `vmalert` was configured with `remoteWrite.url` before and has been successfully persisted its state."+
+		"state. This configuration makes sense only if `vmalert` was configured with `remoteWrite.url` before and has been successfully persisted its state. "+
-		" E.g. http://127.0.0.1:8428")
+		"E.g. http://127.0.0.1:8428")
 	basicAuthUsername     = flag.String("remoteRead.basicAuth.username", "", "Optional basic auth username for -remoteRead.url")
 	basicAuthPassword     = flag.String("remoteRead.basicAuth.password", "", "Optional basic auth password for -remoteRead.url")
 	tlsInsecureSkipVerify = flag.Bool("remoteRead.tlsInsecureSkipVerify", false, "Whether to skip tls verification when connecting to -remoteRead.url")

app/vmalert/remotewrite/init.go

@@ -10,8 +10,8 @@ import (
 )
 
 var (
-	addr = flag.String("remoteWrite.url", "", "Optional URL to Victoria Metrics or VMInsert where to persist alerts state"+
+	addr = flag.String("remoteWrite.url", "", "Optional URL to VictoriaMetrics or vminsert where to persist alerts state "+
-		" and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428")
+		"and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428")
 	basicAuthUsername = flag.String("remoteWrite.basicAuth.username", "", "Optional basic auth username for -remoteWrite.url")
 	basicAuthPassword = flag.String("remoteWrite.basicAuth.password", "", "Optional basic auth password for -remoteWrite.url")
 

app/vmbackupmanager/README.md

@@ -1,4 +1,6 @@
-## Victoria Metrics Backup Manager
+## vmbackupmanager
+
+VictoriaMetrics backup manager
 
 This service automates regular backup procedures. It supports the following backup intervals: **hourly**, **daily**, **weekly** and **monthly**. Multiple backup intervals may be configured simultaneously. I.e. the backup manager creates hourly backups every hour, while it creates daily backups every day, etc. Backup manager must have read access to the storage data, so best practice is to install it on the same machine (or as a sidecar) where the storage node is installed.
 The backup service makes a backup every hour and puts it to the latest folder and then copies data to the folders which represent the backup intervals (hourly, daily, weekly and monthly)

app/vmctl/README.md

@@ -1,6 +1,6 @@
 # vmctl
 
-Victoria metrics command-line tool
+VictoriaMetrics command-line tool
 
 Features:
 - [x] Prometheus: migrate data from Prometheus to VictoriaMetrics using snapshot API
@@ -175,7 +175,7 @@ See `./vmctl influx --help` for details and full list of flags.
 
 To use migration tool please specify the InfluxDB address `--influx-addr`, the database `--influx-database` and VictoriaMetrics address `--vm-addr`.
 Flag `--vm-addr` for single-node VM is usually equal to `--httpListenAddr`, and for cluster version
-is equal to `--httpListenAddr` flag of VMInsert component. Please note, that vmctl performs initial readiness check for the given address 
+is equal to `--httpListenAddr` flag of vminsert component. Please note, that vmctl performs initial readiness check for the given address 
 by checking `/health` endpoint. For cluster version it is additionally required to specify the `--vm-account-id` flag. 
 See more details for cluster version [here](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster).
 
@@ -277,7 +277,7 @@ See `./vmctl prometheus --help` for details and full list of flags. Also see Pro
 To use migration tool please specify the file path to Prometheus snapshot `--prom-snapshot` (see how to make a snapshot [here](https://www.robustperception.io/taking-snapshots-of-prometheus-data)) and VictoriaMetrics address `--vm-addr`.
 Please note, that `vmctl` *do not make a snapshot from Prometheus*, it uses an already prepared snapshot. More about Prometheus snapshots may be found [here](https://www.robustperception.io/taking-snapshots-of-prometheus-data) and [here](https://medium.com/@romanhavronenko/victoriametrics-how-to-migrate-data-from-prometheus-d44a6728f043).
 Flag `--vm-addr` for single-node VM is usually equal to `--httpListenAddr`, and for cluster version
-is equal to `--httpListenAddr` flag of VMInsert component. Please note, that vmctl performs initial readiness check for the given address 
+is equal to `--httpListenAddr` flag of vminsert component. Please note, that vmctl performs initial readiness check for the given address 
 by checking `/health` endpoint. For cluster version it is additionally required to specify the `--vm-account-id` flag. 
 See more details for cluster version [here](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster).
 

app/vmctl/flags.go

@@ -39,7 +39,7 @@ var (
 			Name:  vmAddr,
 			Value: "http://localhost:8428",
 			Usage: "VictoriaMetrics address to perform import requests. \n" +
-				"Should be the same as --httpListenAddr value for single-node version or VMInsert component. \n" +
+				"Should be the same as --httpListenAddr value for single-node version or vminsert component. \n" +
 				"Please note, that `vmctl` performs initial readiness check for the given address by checking `/health` endpoint.",
 		},
 		&cli.StringFlag{
@@ -315,7 +315,7 @@ var (
 		&cli.StringFlag{
 			Name: vmNativeSrcAddr,
 			Usage: "VictoriaMetrics address to perform export from. \n" +
-				" Should be the same as --httpListenAddr value for single-node version or VMSelect component." +
+				" Should be the same as --httpListenAddr value for single-node version or vmselect component." +
 				" If exporting from cluster version - include the tenet token in address.",
 			Required: true,
 		},
@@ -332,7 +332,7 @@ var (
 		&cli.StringFlag{
 			Name: vmNativeDstAddr,
 			Usage: "VictoriaMetrics address to perform import to. \n" +
-				" Should be the same as --httpListenAddr value for single-node version or VMInsert component." +
+				" Should be the same as --httpListenAddr value for single-node version or vminsert component." +
 				" If importing into cluster version - include the tenet token in address.",
 			Required: true,
 		},

app/vmctl/main.go

@@ -21,7 +21,7 @@ func main() {
 	start := time.Now()
 	app := &cli.App{
 		Name:    "vmctl",
-		Usage:   "Victoria metrics command-line tool",
+		Usage:   "VictoriaMetrics command-line tool",
 		Version: buildinfo.Version,
 		Commands: []*cli.Command{
 			{

app/vmctl/vm/vm.go

@@ -21,7 +21,7 @@ import (
 type Config struct {
 	// VictoriaMetrics address to perform import requests
 	//   --httpListenAddr value for single node version
-	//   --httpListenAddr value of VMSelect  component for cluster version
+	//   --httpListenAddr value of vmselect  component for cluster version
 	Addr string
 	// Concurrency defines number of worker
 	// performing the import requests concurrently

app/vmgateway/README.md

@@ -3,12 +3,12 @@
 
 <img alt="vmgateway" src="vmgateway-overview.jpeg">
 
-`vmgateway` is a proxy for the Victoria Metrics Time Series Database (TSDB). It provides the following features:
+`vmgateway` is a proxy for the VictoriaMetrics Time Series Database (TSDB). It provides the following features:
 
 * Rate Limiter
   * Based on cluster tenant's utilization, it supports multiple time interval limits for both the ingestion and retrieval of metrics
 * Token Access Control
-  * Supports additional per-label access control for both the Single and Cluster versions of the Victoria Metrics TSDB
+  * Supports additional per-label access control for both the Single and Cluster versions of the VictoriaMetrics TSDB
   * Provides access by tenantID in the Cluster version
   * Allows for separate write/read/admin access to data
 
@@ -47,7 +47,7 @@ Where:
 
 ## QuickStart
 
-Start the single version of Victoria Metrics
+Start the single version of VictoriaMetrics
 
 ```bash
 # single
@@ -169,7 +169,7 @@ The shortlist of configuration flags include the following:
   -clusterMode
         enable this for the cluster version
   -datasource.appendTypePrefix
-        Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the VMSelect URL.
+        Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the vmselect URL.
   -datasource.basicAuth.password string
         Optional basic auth password for -datasource.url
   -datasource.basicAuth.username string
@@ -191,7 +191,7 @@ The shortlist of configuration flags include the following:
   -datasource.tlsServerName string
         Optional TLS server name to use for connections to -datasource.url. By default, the server name from -datasource.url is used
   -datasource.url string
-        Victoria Metrics or VMSelect url. Required parameter. E.g. http://127.0.0.1:8428
+        VictoriaMetrics or vmselect url. Required parameter. E.g. http://127.0.0.1:8428
   -enable.auth
         enables auth with jwt token
   -enable.rateLimit

docs/Articles.md

@@ -30,7 +30,7 @@ sort: 17
 * [Cloud Native Model Driven Telemetry Stack on OpenShift](https://cer6erus.medium.com/cloud-native-model-driven-telemetry-stack-on-openshift-80712621f5bc)
 * [Observability, Availability & DORA’s Research Program](https://medium.com/alteos-tech-blog/observability-availability-and-doras-research-program-85deb6680e78)
 * [Tame Kubernetes Costs with Percona Monitoring and Management and Prometheus Operator](https://www.percona.com/blog/2021/02/12/tame-kubernetes-costs-with-percona-monitoring-and-management-and-prometheus-operator/)
-* [Prometheus Victoria Metrics On AWS ECS](https://dalefro.medium.com/prometheus-victoria-metrics-on-aws-ecs-62448e266090)
+* [Prometheus VictoriaMetrics On AWS ECS](https://dalefro.medium.com/prometheus-victoria-metrics-on-aws-ecs-62448e266090)
 * [Monitoring with Prometheus, Grafana, AlertManager and VictoriaMetrics](https://www.sensedia.com/post/monitoring-with-prometheus-alertmanager)
 * [Solving Metrics at scale with VictoriaMetrics](https://www.youtube.com/watch?v=QgLMztnj7-8)
 * [Monitoring Kubernetes clusters with VictoriaMetrics and Grafana](https://blog.cybozu.io/entry/2021/03/18/115743)

docs/Cluster-VictoriaMetrics.md

@@ -4,7 +4,7 @@ sort: 9
 
 # Cluster version
 
-<img alt="Victoria Metrics" src="logo.png">
+<img alt="VictoriaMetrics" src="logo.png">
 
 VictoriaMetrics is a fast, cost-effective and scalable time series database. It can be used as a long-term remote storage for Prometheus.
 
@@ -445,7 +445,7 @@ Due to `KISS`, cluster version of VictoriaMetrics has no the following "features
 Report bugs and propose new features [here](https://github.com/VictoriaMetrics/VictoriaMetrics/issues).
 
 
-## Victoria Metrics Logo
+## VictoriaMetrics Logo
 
 [Zip](VM_logo.zip) contains three folders with different image orientation (main color and inverted version).
 

docs/Single-server-VictoriaMetrics.md

@@ -12,7 +12,7 @@ sort: 1
 [![Build Status](https://github.com/VictoriaMetrics/VictoriaMetrics/workflows/main/badge.svg)](https://github.com/VictoriaMetrics/VictoriaMetrics/actions)
 [![codecov](https://codecov.io/gh/VictoriaMetrics/VictoriaMetrics/branch/master/graph/badge.svg)](https://codecov.io/gh/VictoriaMetrics/VictoriaMetrics)
 
-<img src="logo.png" width="300" alt="Victoria Metrics logo">
+<img src="logo.png" width="300" alt="VictoriaMetrics logo">
 
 VictoriaMetrics is a fast, cost-effective and scalable monitoring solution and time series database.
 
@@ -170,7 +170,7 @@ Alphabetically sorted links to case studies:
 * [Contacts](#contacts)
 * [Community and contributions](#community-and-contributions)
 * [Reporting bugs](#reporting-bugs)
-* [Victoria Metrics Logo](#victoria-metrics-logo)
+* [VictoriaMetrics Logo](#victoria-metrics-logo)
   * [Logo Usage Guidelines](#logo-usage-guidelines)
     * [Font used](#font-used)
     * [Color Palette](#color-palette)
@@ -1532,7 +1532,7 @@ Adhering `KISS` principle simplifies the resulting code and architecture, so it
 Report bugs and propose new features [here](https://github.com/VictoriaMetrics/VictoriaMetrics/issues).
 
 
-## Victoria Metrics Logo
+## VictoriaMetrics Logo
 
 [Zip](VM_logo.zip) contains three folders with different image orientations (main color and inverted version).
 

docs/vmalert.md

@@ -168,11 +168,11 @@ For recording rules to work `-remoteWrite.url` must specified.
 
 `vmalert` has no local storage, so alerts state is stored in the process memory. Hence, after reloading of `vmalert`
 the process alerts state will be lost. To avoid this situation, `vmalert` should be configured via the following flags:
-* `-remoteWrite.url` - URL to VictoriaMetrics (Single) or VMInsert (Cluster). `vmalert` will persist alerts state
+* `-remoteWrite.url` - URL to VictoriaMetrics (Single) or vminsert (Cluster). `vmalert` will persist alerts state
 into the configured address in the form of time series named `ALERTS` and `ALERTS_FOR_STATE` via remote-write protocol.
 These are regular time series and may be queried from VM just as any other time series.
 The state stored to the configured address on every rule evaluation.
-* `-remoteRead.url` - URL to VictoriaMetrics (Single) or VMSelect (Cluster). `vmalert` will try to restore alerts state
+* `-remoteRead.url` - URL to VictoriaMetrics (Single) or vmselect (Cluster). `vmalert` will try to restore alerts state
 from configured address by querying time series with name `ALERTS_FOR_STATE`.
 
 Both flags are required for the proper state restoring. Restore process may fail if time series are missing
@@ -205,7 +205,7 @@ to set `-datasource.appendTypePrefix` flag to `true`, so vmalert can adjust URL
 The shortlist of configuration flags is the following:
 ```
   -datasource.appendTypePrefix
-    	Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the VMSelect URL.
+    	Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the vmselect URL.
   -datasource.basicAuth.password string
     	Optional basic auth password for -datasource.url
   -datasource.basicAuth.username string
@@ -227,7 +227,7 @@ The shortlist of configuration flags is the following:
   -datasource.tlsServerName string
     	Optional TLS server name to use for connections to -datasource.url. By default, the server name from -datasource.url is used
   -datasource.url string
-    	Victoria Metrics or VMSelect url. Required parameter. E.g. http://127.0.0.1:8428
+    	VictoriaMetrics or vmselect url. Required parameter. E.g. http://127.0.0.1:8428
   -dryRun -rule
     	Whether to check only config files without running vmalert. The rules file are validated. The -rule flag must be specified.
   -enableTCP6
@@ -330,7 +330,7 @@ The shortlist of configuration flags is the following:
   -remoteRead.tlsServerName string
     	Optional TLS server name to use for connections to -remoteRead.url. By default the server name from -remoteRead.url is used
   -remoteRead.url vmalert
-    	Optional URL to Victoria Metrics or VMSelect that will be used to restore alerts state. This configuration makes sense only if vmalert was configured with `remoteWrite.url` before and has been successfully persisted its state. E.g. http://127.0.0.1:8428
+    	Optional URL to VictoriaMetrics or vmselect that will be used to restore alerts state. This configuration makes sense only if vmalert was configured with `remoteWrite.url` before and has been successfully persisted its state. E.g. http://127.0.0.1:8428
   -remoteWrite.basicAuth.password string
     	Optional basic auth password for -remoteWrite.url
   -remoteWrite.basicAuth.username string
@@ -354,7 +354,7 @@ The shortlist of configuration flags is the following:
   -remoteWrite.tlsServerName string
     	Optional TLS server name to use for connections to -remoteWrite.url. By default the server name from -remoteWrite.url is used
   -remoteWrite.url string
-    	Optional URL to Victoria Metrics or VMInsert where to persist alerts state and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428
+    	Optional URL to VictoriaMetrics or vminsert where to persist alerts state and recording rules results in form of timeseries. E.g. http://127.0.0.1:8428
   -rule array
     	Path to the file with alert rules.
     	Supports patterns. Flag can be specified multiple times.

docs/vmctl.md

@@ -4,7 +4,7 @@ sort: 7
 
 # vmctl
 
-Victoria metrics command-line tool
+VictoriaMetrics command-line tool
 
 Features:
 - [x] Prometheus: migrate data from Prometheus to VictoriaMetrics using snapshot API
@@ -179,7 +179,7 @@ See `./vmctl influx --help` for details and full list of flags.
 
 To use migration tool please specify the InfluxDB address `--influx-addr`, the database `--influx-database` and VictoriaMetrics address `--vm-addr`.
 Flag `--vm-addr` for single-node VM is usually equal to `--httpListenAddr`, and for cluster version
-is equal to `--httpListenAddr` flag of VMInsert component. Please note, that vmctl performs initial readiness check for the given address 
+is equal to `--httpListenAddr` flag of vminsert component. Please note, that vmctl performs initial readiness check for the given address 
 by checking `/health` endpoint. For cluster version it is additionally required to specify the `--vm-account-id` flag. 
 See more details for cluster version [here](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster).
 
@@ -281,7 +281,7 @@ See `./vmctl prometheus --help` for details and full list of flags. Also see Pro
 To use migration tool please specify the file path to Prometheus snapshot `--prom-snapshot` (see how to make a snapshot [here](https://www.robustperception.io/taking-snapshots-of-prometheus-data)) and VictoriaMetrics address `--vm-addr`.
 Please note, that `vmctl` *do not make a snapshot from Prometheus*, it uses an already prepared snapshot. More about Prometheus snapshots may be found [here](https://www.robustperception.io/taking-snapshots-of-prometheus-data) and [here](https://medium.com/@romanhavronenko/victoriametrics-how-to-migrate-data-from-prometheus-d44a6728f043).
 Flag `--vm-addr` for single-node VM is usually equal to `--httpListenAddr`, and for cluster version
-is equal to `--httpListenAddr` flag of VMInsert component. Please note, that vmctl performs initial readiness check for the given address 
+is equal to `--httpListenAddr` flag of vminsert component. Please note, that vmctl performs initial readiness check for the given address 
 by checking `/health` endpoint. For cluster version it is additionally required to specify the `--vm-account-id` flag. 
 See more details for cluster version [here](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster).
 

docs/vmgateway.md

@@ -7,12 +7,12 @@ sort: 8
 
 <img alt="vmgateway" src="vmgateway-overview.jpeg">
 
-`vmgateway` is a proxy for the Victoria Metrics Time Series Database (TSDB). It provides the following features:
+`vmgateway` is a proxy for the VictoriaMetrics Time Series Database (TSDB). It provides the following features:
 
 * Rate Limiter
   * Based on cluster tenant's utilization, it supports multiple time interval limits for both the ingestion and retrieval of metrics
 * Token Access Control
-  * Supports additional per-label access control for both the Single and Cluster versions of the Victoria Metrics TSDB
+  * Supports additional per-label access control for both the Single and Cluster versions of the VictoriaMetrics TSDB
   * Provides access by tenantID in the Cluster version
   * Allows for separate write/read/admin access to data
 
@@ -51,7 +51,7 @@ Where:
 
 ## QuickStart
 
-Start the single version of Victoria Metrics
+Start the single version of VictoriaMetrics
 
 ```bash
 # single
@@ -173,7 +173,7 @@ The shortlist of configuration flags include the following:
   -clusterMode
         enable this for the cluster version
   -datasource.appendTypePrefix
-        Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the VMSelect URL.
+        Whether to add type prefix to -datasource.url based on the query type. Set to true if sending different query types to the vmselect URL.
   -datasource.basicAuth.password string
         Optional basic auth password for -datasource.url
   -datasource.basicAuth.username string
@@ -195,7 +195,7 @@ The shortlist of configuration flags include the following:
   -datasource.tlsServerName string
         Optional TLS server name to use for connections to -datasource.url. By default, the server name from -datasource.url is used
   -datasource.url string
-        Victoria Metrics or VMSelect url. Required parameter. E.g. http://127.0.0.1:8428
+        VictoriaMetrics or vmselect url. Required parameter. E.g. http://127.0.0.1:8428
   -enable.auth
         enables auth with jwt token
   -enable.rateLimit