Merge pull request #52058 from codyhoag/typo2

Hacktoberfest: Fix Elasticsearch product name

Author: bergerhoffer

modules/upi-installation-considerations.adoc

@@ -24,6 +24,6 @@ It is not possible to enable cloud provider integration in {product-title} envir
 
 * Check whether your chosen cloud provider offers a method to inject Ignition configuration files into hosts as part of their initial deployment. If they do not, you will need to host Ignition configuration files by using an HTTP server. The steps taken to troubleshoot Ignition configuration file issues will differ depending on which of these two methods is deployed.
 
-* Storage needs to be manually provisioned if you want to leverage optional framework components such as the embedded container registry, ElasticSearch, or Prometheus. Default storage classes are not defined in user-provisioned infrastructure installations unless explicitly configured.
+* Storage needs to be manually provisioned if you want to leverage optional framework components such as the embedded container registry, Elasticsearch, or Prometheus. Default storage classes are not defined in user-provisioned infrastructure installations unless explicitly configured.
 
 * A load balancer is required to distribute API requests across all control plane nodes in highly available {product-title} environments. You can use any TCP-based load balancing solution that meets {product-title} DNS routing and port requirements.