Update endpoint-related terminology (#160) (#184)

* Update endpoint-related terminology

* Fix attribute

* Remove Elastic from integration name.

* Remove link to endpoint repo

docs/en/ingest-management/faq.asciidoc

@@ -120,12 +120,12 @@ you did previously with {beats} modules.
 == Does {agent} download anything from the Internet?
 
 In most cases, the data collection software required by {agent} is bundled
-with the agent. There is one special exception: {elastic-endpoint}. When an
-{agent} policy is set to include {elastic-endpoint}, {agent} must download
-software from the Elastic download site.
+with the agent. There is one special exception: endpoint security. When an
+{agent} policy is set to include the {elastic-endpoint-integration} integration,
+{agent} must download software from the Elastic download site.
 
-NOTE: Bundling {elastic-endpoint} with {agent} is a known feature request scoped
-for a future release. 
+NOTE: Bundling endpoint security capabilities with {agent} is a known
+feature request scoped for a future release. 
 
 [discrete]
 [[do-i-need-to-setup-elastic-agent]]
@@ -144,12 +144,11 @@ downloads from the {package-registry} at `epr.elastic.co`. This means that
 
 [discrete]
 [[what-is-the-endpoint-package]]
-== What is the Elastic {endpoint-sec} integration in {ingest-manager}?
+== What is the {elastic-endpoint-integration} integration in {ingest-manager}?
 
-The Elastic {endpoint-sec} integration provides protection on your {agent}
+The {elastic-endpoint-integration} integration provides protection on your {agent}
 controlled host. The integration monitors your host for security-related events,
-allowing for investigation of security data through the Elastic Security
-application in {kib}. The Elastic {endpoint-sec} integration is managed by
-{agent} in in the same way as other integrations. Try it out! For more
-information, see the {security-guide}/index.html[Elastic Security solution
-documentation].
+allowing for investigation of security data through the {security-app} in {kib}.
+The {elastic-endpoint-integration} integration is managed by {agent} in the
+same way as other integrations. Try it out! For more information, see the
+{security-guide}/index.html[{elastic-sec} solution documentation].

docs/en/ingest-management/index.asciidoc

@@ -2,6 +2,7 @@
 :beats-repo-dir: {beats-root}
 :im-forum: https://discuss.elastic.co/tags/c/elastic-stack/81/stack-ingest-management
 :code-path: {beats-repo-dir}/libbeat/docs/tab-widgets/code
+:elastic-endpoint-integration: Endpoint Security
 
 = Ingest Management Guide
 
@@ -22,4 +23,3 @@ include::troubleshooting.asciidoc[leveloffset=+1]
 include::faq.asciidoc[leveloffset=+1]
 
 
-

docs/en/ingest-management/troubleshooting.asciidoc

@@ -10,7 +10,6 @@ described here, please review open issues in the following GitHub repositories:
 * https://github.com/elastic/kibana/issues[{kib}]
 * https://github.com/elastic/beats/issues[{beats}]
 * https://github.com/elastic/package-registry/issues[{package-registry}]
-* https://github.com/elastic/endpoint/issues[Elastic {endpoint-sec}]
 
 Have a question? Read our <<ingest-management-faq,FAQ>>, or contact us in the
 {im-forum}[discuss forum]. Your feedback is very valuable to us.
@@ -146,7 +145,7 @@ Make sure the user running {agent} has root privileges. If you're running
 agent under the root user, for example, `sudo` or `su`. Some integrations
 require root privileges to collect sensitive data.
 
-If you're using the {elastic-endpoint} integration, also make sure you're
+If you're using the {elastic-endpoint-integration} integration, also make sure you're
 running {agent} under the SYSTEM account.
 
 TIP: If you install {agent} as a service as described in