docs: change to specify that ecctl is no longer ECE specific (#190)

Documentation change to specify that ecctl is no longer ECE specific.

The docs have also been slightly modified to cater to our largest user base which will be ESS.

Author: karencfv

README.md

@@ -4,11 +4,9 @@
 
 NOTE: **You are looking at the documentation for a beta release. Please keep in mind that backwards-incompatible changes might be introduced in future releases.**
 
-`ecctl` is the CLI on steroids for the Elastic Cloud Enterprise API. It wraps typical operations commonly needed by ECE operators within a single command line tool.
+`ecctl` is the CLI on steroids for the Elasticsearch Service and Elastic Cloud Enterprise APIs. It wraps typical operations commonly needed by operators within a single command line tool.
 
-The goal of this project is to provide an easier way to interact with the ECE API, ensuring each one of the provided commands is thoroughly tested.
-
-Note that, right now, `ecctl` targets ECE installations only. There are, however, plans to support public Elasticsearch Service API in the future.
+The goal of this project is to provide an easier way to interact with the Elasticsearch Service and Elastic Cloud Enterprise APIs, ensuring each one of the provided commands is thoroughly tested.
 
 To get started with Elastic Cloud Control, see the [official documentation](https://www.elastic.co/guide/en/ecctl/current/index.html). 
 

docs/ecctl-getting-started.asciidoc

@@ -3,20 +3,15 @@
 
 beta[]
 
-{p} is the CLI on steroids for the Elastic Cloud Enterprise API. It wraps
-typical operations commonly needed by ECE operators within a
-single command line tool.
+{p} is the CLI on steroids for the Elasticsearch Service and Elastic Cloud Enterprise APIs. 
+It wraps typical operations commonly needed by operators within a single command line tool.
 
 Benefits of {p}:
 
 * Easier to use than the Cloud UI or using the RESTful API directly
 * Helps you automate the deployment lifecycle
 * Provides a foundation for integration with other tools, such as Terraform and Ansible
 
-Right now, {p} supports ECE installations only.
-
-//, but we plan to support a public Elasticsearch Service API in the future.
-
 [id="{p}-installing"]
 == Installing
 
@@ -123,21 +118,14 @@ Please enter your choice: 1
 
 Using "https://api.elastic-cloud.com" as the API endpoint.
 
+Paste your API Key and press enter: xxxxx
+
 What default output format would you like?
   [1] text - Human-readable output format, commands with no output templates defined will fall back to JSON.
   [2] json - JSON formatted output API responses.
 
 Please enter a choice: 1
 
-
-Which authentication mechanism would you like to use?
-  [1] API Keys (Recommended).
-  [2] Username and Password login.
-
-Please enter your choice: 1
-
-Paste your API Key and press enter: xxxxx
-
 Your credentials seem to be valid, and show you're authenticated as "user".
 
 You're all set! Here is a command to try:
@@ -151,7 +139,7 @@ Elastic Cloud uses API keys to authenticate users against its API.
 Additionally, it supports the usage of https://jwt.io/[JWT] to validate
 authenticated clients. The preferred authentication method is API keys.
 
-There are two ways to authenticate against the Elastic Cloud API using
+There are two ways to authenticate against the Elasticsearch Service or the Elastic Cloud Enterprise APIs
 {p}:
 
 * By specifying an API key using the `--apikey` flag
@@ -176,7 +164,7 @@ the binary for Elastic Cloud:
 
 [source,yaml]
 ----
-host: https://api.elastic-cloud.com # URL of your ECE API endpoint
+host: https://api.elastic-cloud.com # URL of your Elasticsearch Service or Elastic Cloud Enterprise API endpoint
 
 # Credentials
 ## apikey is the preferred authentication mechanism.
@@ -327,10 +315,8 @@ $ unset EC_FORMAT
 
 {n} includes commands to administer:
 
-* Platform components
-* Platform authentication
-* Platform users
 * Elastic Stack deployments
+* Platform components
 * And more
 
 :leveloffset: +1