all: replace ElasticSearch -> Elasticsearch for the sake of consistency

This is a follow-up for 7f6b5dc47b

app/vlinsert/elasticsearch/elasticsearch.go

@@ -24,30 +24,30 @@ import (
 	"github.com/VictoriaMetrics/metrics"
 )
 
-// RequestHandler processes ElasticSearch insert requests
+// RequestHandler processes Elasticsearch insert requests
 func RequestHandler(path string, w http.ResponseWriter, r *http.Request) bool {
 	w.Header().Add("Content-Type", "application/json")
 	// This header is needed for Logstash
 	w.Header().Set("X-Elastic-Product", "Elasticsearch")
 
 	if strings.HasPrefix(path, "/_ilm/policy") {
-		// Return fake response for ElasticSearch ilm request.
+		// Return fake response for Elasticsearch ilm request.
 		fmt.Fprintf(w, `{}`)
 		return true
 	}
 	if strings.HasPrefix(path, "/_index_template") {
-		// Return fake response for ElasticSearch index template request.
+		// Return fake response for Elasticsearch index template request.
 		fmt.Fprintf(w, `{}`)
 		return true
 	}
 	if strings.HasPrefix(path, "/_ingest") {
-		// Return fake response for ElasticSearch ingest pipeline request.
+		// Return fake response for Elasticsearch ingest pipeline request.
 		// See: https://www.elastic.co/guide/en/elasticsearch/reference/8.8/put-pipeline-api.html
 		fmt.Fprintf(w, `{}`)
 		return true
 	}
 	if strings.HasPrefix(path, "/_nodes") {
-		// Return fake response for ElasticSearch nodes discovery request.
+		// Return fake response for Elasticsearch nodes discovery request.
 		// See: https://www.elastic.co/guide/en/elasticsearch/reference/8.8/cluster.html
 		fmt.Fprintf(w, `{}`)
 		return true
@@ -56,8 +56,8 @@ func RequestHandler(path string, w http.ResponseWriter, r *http.Request) bool {
 	case "/":
 		switch r.Method {
 		case http.MethodGet:
-			// Return fake response for ElasticSearch ping request.
+			// Return fake response for Elasticsearch ping request.
-			// See the latest available version for ElasticSearch at https://github.com/elastic/elasticsearch/releases
+			// See the latest available version for Elasticsearch at https://github.com/elastic/elasticsearch/releases
 			fmt.Fprintf(w, `{
 			"version": {
 				"number": "8.8.0"
@@ -69,7 +69,7 @@ func RequestHandler(path string, w http.ResponseWriter, r *http.Request) bool {
 
 		return true
 	case "/_license":
-		// Return fake response for ElasticSearch license request.
+		// Return fake response for Elasticsearch license request.
 		fmt.Fprintf(w, `{
 			"license": {
 				"uid": "cbff45e7-c553-41f7-ae4f-9205eabd80xx",

docs/CaseStudies.md

@@ -488,7 +488,7 @@ See more details [in this article](https://www.datanami.com/2023/05/30/why-roblo
 
 > Our initial requirements for monitoring solution: the metrics must be stored for 15 days, the solution must be scalable and must offer high availability of the metrics. It must being integrated into Grafana and allowing the use of PromQL when creating/editing dashboards in Grafana to obtain metrics from the Prometheus datasource. The solution also needs to receive data from Prometheus using HTTPS and needs to request a login and password to write/read the metrics. Details are available [in this article](https://nordicapis.com/api-monitoring-with-prometheus-grafana-alertmanager-and-victoriametrics/).
 
-> We evaluated VictoriaMetrics, InfluxDB OpenSource and Enterprise, ElasticSearch, Thanos, Cortex, TimescaleDB/PostgreSQL and M3DB. We selected VictoriaMetrics because it has [good community support](https://slack.victoriametrics.com/), [good documentation](https://docs.victoriametrics.com/) and it just works.
+> We evaluated VictoriaMetrics, InfluxDB OpenSource and Enterprise, Elasticsearch, Thanos, Cortex, TimescaleDB/PostgreSQL and M3DB. We selected VictoriaMetrics because it has [good community support](https://slack.victoriametrics.com/), [good documentation](https://docs.victoriametrics.com/) and it just works.
 
 > We started using VictoriaMetrics in the production environment days before the start of BlackFriday in 2020, the period of greatest use of the Sensedia API-Platform by customers. There was a record in the generation of metrics and there was no instability with the monitoring stack.
 

docs/VictoriaLogs/FAQ.md

@@ -29,8 +29,8 @@ VictoriaLogs is optimized specifically for logs. So it provides the following fe
 
 - Easy to setup and operate. There is no need in tuning configuration for optimal performance or in creating any indexes for various log types.
   Just run VictoriaLogs on the most suitable hardware - and it automatically provides the best performance.
-- Up to 30x less RAM usage than ElasticSearch for the same workload.
+- Up to 30x less RAM usage than Elasticsearch for the same workload.
-- Up to 15x less disk space usage than ElasticSearch for the same amounts of stored logs.
+- Up to 15x less disk space usage than Elasticsearch for the same amounts of stored logs.
 - Ability to work with hundreds of terabytes of logs on a single node.
 - Very easy to use query language optimized for typical log analysis tasks - [LogsQL](https://docs.victoriametrics.com/VictoriaLogs/LogsQL.html).
 - Fast full-text search over all the [log fields](https://docs.victoriametrics.com/VictoriaLogs/keyConcepts.html#data-model) out of the box.

docs/VictoriaLogs/Roadmap.md

@@ -13,7 +13,7 @@ aliases:
 # VictoriaLogs roadmap
 
 The [VictoriaLogs](https://docs.victoriametrics.com/VictoriaLogs/) Preview is ready for evaluation in production.
-It is recommended running it alongside the existing solutions such as ElasticSearch and Grafana Loki
+It is recommended running it alongside the existing solutions such as Elasticsearch and Grafana Loki
 and comparing their resource usage and usability.
 It isn't recommended migrating from existing solutions to VictoriaLogs Preview yet.