Apply suggestions from code review

Co-authored-by: Max Jakob <[email protected]>

Author: szabosteve

explore-analyze/elastic-inference/eis.md

@@ -8,46 +8,45 @@ navigation_title: Elastic Inference Service (EIS)
 # Elastic {{infer-cap}} Service [elastic-inference-service-eis]
 
 The Elastic {{infer-cap}} Service (EIS) enables you to leverage AI-powered search as a service without deploying a model in your cluster.
-With EIS, you don't need to manage the infrastructure and resources required for large language models (LLMs) by adding, configuring, and scaling {{ml}} nodes.
-Instead, you can use {{ml}} models in high-throughput, low-latency scenarios independently of your {{es}} infrastructure.
+With EIS, you don't need to manage the infrastructure and resources required for {{ml}} {{infer}} by adding, configuring, and scaling {{ml}} nodes.
+Instead, you can use {{ml}} models for ingest, search and chat independently of your {{es}} infrastructure.
 
 % TO DO: Link to the EIS inference endpoint reference docs when it's added to the OpenAPI spec. (Comming soon) %
 
 ## Available task types
 
 EIS offers the following {{infer}} task types to perform:
 
-* Chat completion
+* `chat_completion`
 
-## How to use EIS [using-eis]
+## AI features powered by EIS [ai-features-powered-by-eis]
 
-Your Elastic deployment comes with default endpoints for EIS that you can use performing {{infer}} tasks.
-You can either do it by calling the {{infer}} API or using the default `Elastic LLM` model in the AI Assistant, Attack Discovery UI, and Search Playground.
+Your Elastic deployment or project comes with a default `Elastic LLM` connector. This connector is used in the AI Assistant, Attack Discovery, Automatic Import and Search Playground.
 
 % TO DO: Link to the EIS inference endpoint reference docs when it's added to the OpenAPI spec. (Comming soon) %
 
 ## Default EIS endpoints [default-eis-inference-endpoints]
 
 Your {{es}} deployment includes a preconfigured EIS endpoint, making it easier to use chat completion via the {{infer}} API:
 
-* `rainbow-sprinkles-elastic`
+* `.rainbow-sprinkles-elastic`
 
 ::::{note}
 
-* The model appears as `Elastic LLM` in the AI Assistant, Attack Discovery UI, preconfigured connectors list, and the Search Playground.
+* This endpoint is used by the `Elastic LLM` AI connector, which in turn powers the AI Assistant, Attack Discovery, Automatic Import, and the Search Playground.
 
 ::::
 
 % TO DO: Link to the AI assistant documentation in the different solutions and possibly connector docs. %
 
 ## Regions [eis-regions]
 
-EIS runs on AWS in the following regions:
+All EIS requests are handled by one of these AWS regions:
 
 * `us-east-1`
 * `us-west-2`
 
-For more details on AWS regions, refer to the [AWS Global Infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) and the [supported cross-region {{infer}} profiles](https://docs.aws.amazon.com/bedrock/latest/userguide/inference-profiles-support.html) documentation.
+For more details on AWS regions, refer to the [AWS Global Infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/).
 
 ## Examples
 
@@ -67,15 +66,14 @@ POST /_inference/chat_completion/.rainbow-sprinkles-elastic/_stream
 }
 ```
 
-The request returns the following response:
+The request returns the following response as a stream:
 
 ```json
 (...)
 {
   "role" : "assistant",
   "content": "Yes",
   "model" : "rainbow-sprinkles",
-  "object" : "chat.completion.chunk",
   "usage" : {
     "completion_tokens" : 4,
     "prompt_tokens" : 13,