Incorporated Ben's comments

Author: pabel-rh

modules/model-context-protocol-tools/con-understanding-model-context-protocol.adoc

@@ -5,6 +5,6 @@
 
 include::{docdir}/artifacts/snip-developer-preview-mcp.adoc[]
 
-Model Context Protocol (MCP) offers a standardized method for linking AI models and applications (MCP clients) with external systems. This connection facilitates access to information and workflows residing on those systems. MCP servers are responsible for defining the tools that AI applications can utilize to retrieve this data.
+*Model Context Protocol* (*MCP*) offers a standardized method for linking AI models and applications (*MCP clients*) with external systems (*MCP servers*). This connection facilitates access to information and workflows residing on those systems. *MCP servers* are responsible for defining the tools that MCP clients can interact with.
 
 {product} supports running MCP tools through the `mcp-actions-backend` plugin available in {backstage} 1.40 or later. 

modules/model-context-protocol-tools/proc-accessing-and-analyzing-doc-using-techdocs-mcp-tools.adoc

@@ -3,7 +3,7 @@
 [id="proc-accessing-and-analyzing-doc-using-techdocs-mcp-tools_{context}"]
 = Accessing and analyzing documentation using the TechDocs MCP tools
 
-The TechDocs Model Context Protocol (MCP) tool enables AI clients to search and retrieve documentation directly from {product-very-short} TechDocs instances. Use this tool to query documentation content and integrate it as context into your AI applications.
+The TechDocs MCP tool enables MCP clients to search and retrieve documentation directly from TechDocs registered in your {product-very-short} instance. Use this tool to query documentation content and integrate it as context into your AI applications.
 
 The following TechDocs MCP tools are supported:
 * `fetch-techdocs`

modules/model-context-protocol-tools/proc-configuring-mcp-clients-to-access-the-rhdh-server.adoc

@@ -3,7 +3,7 @@
 [id="proc-configuring-mpc-clients-to-access-the-rhdh-server_{context}"]
 = Configuring MCP clients to access the {product-very-short} server
 
-You must configure an MCP client to interact with the MCP server. For more information on the list of clients and their respective configurations, see https://modelcontextprotocol.io/clients[Example Clients].
+You must configure an MCP client before it can interact with the MCP server. For more information on the list of clients and their respective configurations, see https://modelcontextprotocol.io/clients[Example Clients].
 
 .Prerequisites
 
@@ -17,27 +17,9 @@ You must configure an MCP client to interact with the MCP server. For more infor
 Some clients do not yet support the Streamable endpoint, and you might need to use the SSE endpoint instead. 
 ====
 
-.Procedure
+* You have set the ${MCP_TOKEN} in your MCP server configuration as the bearer token when authenticating with the MCP server. 
 
-. Set the ${MCP_TOKEN} in your MCP server configuration as the bearer token when authenticating with the MCP server by completing the following steps:
-.. In the {ocp-short} web console, go to *Secrets*.
-.. Click *Create > Key/value secret*.
-.. In the *Create key/value secret* page, select the *YAML view* option in *Configure via*, and add the following example:
-+
-[source,yaml]
-----
-kind: Secret
-apiVersion: v1
-metadata:
-  name: MCP_TOKEN
-  namespace: _<namespace>_ #
-stringData:
-  LLM_SERVER_ID: _<server_id>_
-  LLM_SERVER_TOKEN: _<token>_
-  LLM_SERVER_URL: _<server_url>_
-type: Opaque
-----
-.. Click *Create*.
+.Procedure
 
 . Configure the *Cursor* client.
 .. From your Desktop app, navigate to *Cursor Settings* and select *MCP Tools > New MCP Server*.

modules/model-context-protocol-tools/proc-configuring-model-context-protocol.adoc

@@ -3,7 +3,7 @@
 [id="proc-configuring-model-context-protocol_{context}"]
 = Configuring Model Context Protocol in {product}
 
-You can enable your AI client applications to access {product-very-short} information and workflows. This configuration is a prerequisite for AI clients to use the defined MCP tools and leverage {product-very-short} data.
+You can enable your MCP client applications to use the MCP protocol to access {product-very-short} information and workflows. This configuration is a prerequisite for MCP clients to use the defined MCP tools and access the exposed capabilities of {product-very-short}.
 
 .Prerequisite
 
@@ -25,7 +25,7 @@ backend:
 ----
 where:
 
-`${MCP_TOKEN}`:: Set the token value that you generate.
+`${MCP_TOKEN}`:: Set the token value that you generate manually and share with your MCP clients
 +
 [NOTE]
 ====
@@ -49,7 +49,7 @@ backend:
       - techdocs-mcp-tool
 ----
 +
-.`{my-app-config-file}` file with MCP configuration example
+.Full `{my-app-config-file}` file example with MCP configuration
 [source,yaml,subs="+attributes,+quotes"]
 ----
 app:

modules/model-context-protocol-tools/proc-installing-the-mcp-server-and-tool-plugins.adoc

@@ -5,8 +5,8 @@
 
 To enable MCP support in {product}, you need to install the following components:
 
-Backend MCP server plugin:: Runs the MCP tools.
-MCP tool plugins:: Facilitates integration with the Software Catalog and TechDocs.
+Backend MCP server plugin:: Responsible for running MCP tools.
+MCP tool plugins:: Individual MCP plugins that expose capabilities relating to the Software Catalog and TechDocs features in {product-very-short}.
 
 .Prerequisites