Change references to HTTP in native

elastic · Sep 25, 2023 · 735fb85 · 735fb85
1 parent e24092a
commit 735fb85
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/static/ls-ls-config.asciidoc b/docs/static/ls-ls-config.asciidoc
@@ -18,7 +18,7 @@ Logstash-to-Logstash communication can be achieved in one of two ways:
 This is the preferred method to implement Logstash-to-Logstash. It replaces <<ls-to-ls-http>> and has these considerations:
 
 * It relies on HTTP as the communication protocol between the Input and Output.
-* It does not provide built-in high availability. You will need to implement your own load balancer in between the HTTP output and the HTTP input.
+* It does not provide built-in high availability. You will need to implement your own load balancer in between the Logstash output and the Logstash input.
 * If you need a proxy between the Logstash instances, you can use any HTTP proxy.
 * No connection information is added to events.
 

diff --git a/docs/static/ls-ls-native.asciidoc b/docs/static/ls-ls-native.asciidoc
@@ -60,7 +60,7 @@ Use SSL/TLS mutual authentication in order to ensure that the upstream Logstash
 TIP: We recommend you use the {ref}/certutil.html[elasticsearch-certutil] tool to generate your certificates.
 
 . Configure the downstream (receiving) Logstash to use SSL.
-Add these settings to the HTTP Input configuration:
+Add these settings to the Logstash input configuration:
 +
  * `ssl_enabled`: When set to `true`, it enables Logstash use of SSL/TLS
  * `ssl_key`: Specifies the key that Logstash uses to authenticate with the client.