minor update

Author: eedugon

deploy-manage/production-guidance/general-recommendations.md

@@ -11,12 +11,12 @@ applies_to:
 
 # General recommendations [general-recommendations]
 
+This page offers general best practices to improve performance and avoid common issues when working with Elasticsearch.
 
 ## Don’t return large result sets [large-size]
 
 Elasticsearch is designed as a search engine, which makes it very good at getting back the top documents that match a query. However, it is not as good for workloads that fall into the database domain, such as retrieving all documents that match a particular query. If you need to do this, make sure to use the [Scroll](elasticsearch://reference/elasticsearch/rest-apis/paginate-search-results.md#scroll-search-results) API.
 
-
 ## Avoid large documents [maximum-document-size]
 
 Given that the default [`http.max_content_length`](elasticsearch://reference/elasticsearch/configuration-reference/networking-settings.md#http-settings) is set to 100MB, Elasticsearch will refuse to index any document that is larger than that. You might decide to increase that particular setting, but Lucene still has a limit of about 2GB.

deploy-manage/production-guidance/kibana-load-balance-traffic.md

@@ -88,7 +88,7 @@ elasticsearch.hosts:
 Related configurations include `elasticsearch.sniffInterval`, `elasticsearch.sniffOnStart`, and `elasticsearch.sniffOnConnectionFault`. These can be used to automatically update the list of hosts as a cluster is resized.  Parameters can be found in the [{{kib}} configuration reference](kibana://reference/configuration-reference/general-settings.md).
 
 ::::{note}
-The previous configuration can be useful when there is no load balancer or reverse proxy in front of {{es}}. If a load balancer is in place to distribute traffic among {{es}} instances, Kibana should be configured to connect to it instead. 
+This configuration can be useful when there is no load balancer or reverse proxy in front of {{es}}. If a load balancer is in place to distribute traffic among {{es}} instances, {{kib}} should be configured to connect to it instead. 
 
 In [orchestrated deployments](/deploy-manage/deploy.md#about-orchestration), {{kib}} is automatically configured to connect to {{es}} through load-balanced services—such as platform proxies in ECE or ECH, or Kubernetes services in the case of ECK.
 ::::