Merge branch 'main' into k8-onboarding-known-issue

Author: mdbirnstiehl

explore-analyze/machine-learning/nlp/ml-nlp-model-ref.md

@@ -15,9 +15,7 @@ products:
 The minimum dedicated ML node size for deploying and using the {{nlp}} models is 16 GB in {{ech}} if [deployment autoscaling](../../../deploy-manage/autoscaling.md) is turned off. Turning on autoscaling is recommended because it allows your deployment to dynamically adjust resources based on demand. Better performance can be achieved by using more allocations or more threads per allocation, which requires bigger ML nodes. Autoscaling provides bigger nodes when required. If autoscaling is turned off, you must provide suitably sized nodes yourself.
 ::::
 
-The {{stack-ml-features}} support transformer models that conform to the standard BERT model interface and use the WordPiece tokenization algorithm.
-
-The current list of supported architectures is:
+The {{stack-ml-features}} support transformer models with the following architectures:
 
 * BERT
 * BART

reference/fleet/logstash-output.md

@@ -37,11 +37,11 @@ input {
   elastic_agent {
     port => 5044
     enrich => none <1>
-    ssl => true
+    ssl_enabled => true
     ssl_certificate_authorities => ["<ca_path>"]
     ssl_certificate => "<server_cert_path>"
     ssl_key => "<server_cert_key_in_pkcs8>"
-    ssl_verify_mode => "force_peer"
+    ssl_client_authentication => "required"
   }
 }
 
@@ -52,8 +52,8 @@ output {
     data_stream => "true"
     api_key => "<api_key>" <3>
     data_stream => true
-    ssl => true
-    # cacert => "<elasticsearch_ca_path>"
+    ssl_enabled => true
+    ssl_certificate_authorities => "<elasticsearch_ca_path>"
   }
 }
 ```