Incorporate pre-review comments

Author: karenzone

docs/static/ea-integration-tutorial.asciidoc

@@ -1,13 +1,12 @@
 [[ea-integrations-tutorial]]
-== Using {ls} with Elastic {integrations} (Beta) tutorial
-
-
-Logstash elastic-integration Filter
-Plugin Guide
-Ingest node pipelines in Logstash
+== Tutorial: {ls} `elastic_integration filter` to extend Elastic {integrations} (Beta)
+++++
+<titleabbrev>Tutorial: {ls} `elastic_integration filter`</titleabbrev>
+++++
 
 
 Process overview
+
 * Configure Fleet to send data from Elastic Agent to Logstash
 * Create an Elastic Agent policy with the necessary integrations
 * Configure Logstash to use the elastic_integration filter plugin
@@ -16,13 +15,12 @@ Process overview
 Logstash elastic-integration Filter Plugin Guide
 
 Overview
-The purpose of this guide is to walk through the steps necessary to configure Logstash to transform events
-collected by the Elastic Agent using our pre-built ingest node pipelines that normalize data to the Elastic
-Common Schema. This is possible with a new beta feature in Logstash known as the elastic-integration
+The purpose of this guide is to walk through the steps necessary to configure {ls} to transform events
+collected by the Elastic Agent using our pre-built Elastic Integrations that normalize data to the Elastic Common Schema (ECS).
+This is possible with a new beta feature in Logstash known as the elastic-integration
 filter plugin.
-Using this new plugin, Logstash reads certain field values generated by the Elastic Agent that tells Logstash to
-fetch pipeline definitions from an Elasticsearch cluster which Logstash can then use to process events before
-sending them to thier configured destinations.
+Using this new plugin, Logstash reads certain field values generated by the Elastic Agent, and uses them to apply the transformations from Elastic Integrations so that it can further process events before
+sending them to their configured destinations.
 
 Prerequisites/Requirements
 
@@ -72,9 +70,8 @@ Figure 4: policy-output
 . Click “Create agent policy” at the bottom of the flyout.
 . The new policy should be listed on the Agent policies page now.
 . Click on the policy name so that we can start configuring an integration.
-. On the policy page, click “Add integration”. This will take you to the integrations browser, where you
-can select an integration that will have data stream definitions (mappings, pipelines, etc.), dashboards,
-and data normalization pipelines that convert the source data into Elastic Common Schema.
+. On the policy page, click “Add integration”. 
+  This will take you to the integrations browser, where you can select an integration that will have everything necessary to _integrate_ that data source with your other data in the Elastic stack.
 
 Figure 5: add-integration-to-policy
 In this example we will search for and select the Crowdstrike integration.
@@ -118,7 +115,6 @@ filter {
  elastic_integration {
   hosts => "{es-host}:9200"
   ssl_enabled => true
-  ssl_verification_mode => "certificate"
   ssl_certificate_authorities => ["/usr/share/logstash/config/certs/ca-cert.pem"]
   auth_basic_username => "elastic"
   auth_basic_password => "changeme"
@@ -136,7 +132,6 @@ output {
   password => "changeme"
   user => "elastic"
   cacert => "/usr/share/logstash/config/certs/ca-cert.pem"
-  ssl_certificate_verification => false
  }
 }
 -----
@@ -167,19 +162,15 @@ output {
  }
 -----
 
-Every event sent from the Elastic Agent to Logstash contains specific meta-fields. Input event are expected
-to have data_stream.type, data_stream.dataset, and data_stream.namespace . This tells Logstash which pipelines
-to fetch from Elasticsearch to correctly process the event before sending that event to it’s destination output.
-Logstash performs a check quickly and often to see if an integrations associated ingest pipeline has had updates
-or changes so that events are processed with the most recent version of the ingest pipeline.
+Every event sent from the Elastic Agent to Logstash contains specific meta-fields. 
+Input event are expected to have data_stream.type, data_stream.dataset, and data_stream.namespace.
+Logstash uses this information and its connection to Elasticsearch to determine which Integrations to apply to the event before sending that event to its destination output.
+Logstash frequently synchronizes with Elasticsearch to ensure it has the most recent versions of the enabled Integrations.
 
 
 All processing occurs in Logstash.
 
 
-The user or credentials specified in the elastic_integration plugin needs to have sufficient privileges to get
-
-the appropriate monitoring, pipeline definitions, and index templates necessary to transform the events. Mini-
-mum required privileges can be found here: https://www.elastic.co/guide/en/logstash/current/plugins-filters-
-elastic_integration.html#plugins-filters-elastic_integration-minimum_required_privileges
+The user or credentials specified in the elastic_integration plugin needs to have sufficient privileges to get information about Elasticsearch and the Integrations that are enabled.
+Minimum required privileges can be found here: https://www.elastic.co/guide/en/logstash/current/plugins-filters-elastic_integration.html#plugins-filters-elastic_integration-minimum_required_privileges.
 

docs/static/ea-integrations.asciidoc

@@ -78,7 +78,7 @@ output { <3>
 -----
 
 <1> Use `filter-elastic_integration` as the first filter in your pipeline 
-<2> You can use additional filters as long as they follow `filter-elastic_integration`
+<2> You can use additional filters as long as they follow `filter-elastic_integration`. They will have access to the event as-transformed by your enabled integrations.
 <3> Sample config to output data to multiple destinations