Addresses feedback.

Author: szabosteve

explore-analyze/elastic-inference.md

@@ -10,10 +10,15 @@ navigation_title: Elastic Inference
 ## Overview
 
 {{infer-cap}} is a process of using a {{ml}} trained model to make predictions or operations - such as text embedding, or reranking - on your data.
-You can use {{infer}} during ingest time (for example, to create embeddings from textual data you ingest) or search time (to perform [semantic search](/solutions/search/semantic-search.md)).
-There are several ways to perform {{infer}} in the {{stack}}:
+You can use {{infer}} during ingest time (for example, to create embeddings from textual data you ingest) or search time (to perform [semantic search](/solutions/search/semantic-search.md) based on the embeddings created previously).
+There are several ways to perform {{infer}} in the {{stack}}, depending on the underlying {{infer}} infrastructure and the interface you use:
 
-* [Using the Elastic {{infer-cap}} Service](elastic-inference/eis.md)
-* [Using `semantic_text` if you want to perform semantic search](/solutions/search/semantic-search/semantic-search-semantic-text.md)
-* [Using the {{infer}} API](elastic-inference/inference-api.md)
-* [Trained models deployed in your cluster](machine-learning/nlp/ml-nlp-overview.md)
+- **{{infer-cap}} infrastructure:**
+
+  - [Elastic {{infer-cap}} Service](elastic-inference/eis.md): a managed service that runs {infer} outside your cluster resources.
+  - [Trained models deployed in your cluster](machine-learning/nlp/ml-nlp-overview.md): models run on your own {{ml}} nodes
+
+- **Access methods:**
+
+  - [The `semantic_text` workflow](/solutions/search/semantic-search/semantic-search-semantic-text.md): a simplified method that uses the {{infer}} API behind the scenes to enable semantic search.
+  - [The {{infer}} API](elastic-inference/inference-api.md): a general-purpose API that enables you to run {{infer}} using EIS, your own models, or third-party services.

explore-analyze/elastic-inference/eis.md

@@ -19,10 +19,10 @@ Instead, you can use {{ml}} models for ingest, search, and chat independently of
 
 ## Region and hosting [eis-regions]
 
-Requests through the Elastic Managed LLM are currently proxying to AWS Bedrock in AWS US regions, beginning with `us-east-1`.
+Requests through the `Elastic Managed LLM` are currently proxying to AWS Bedrock in AWS US regions, beginning with `us-east-1`.
 The request routing does not restrict the location of your deployments.
 
-ELSER requests are managed by Elastic own EIS infrastructure.
+ELSER requests are managed by Elastic's own EIS infrastructure.
 
 ## ELSER via Elastic {{infer-cap}} Service (ELSER on EIS)