Added Maysun's and Stephanie's comments

Author: pabel-rh

modules/developer-lightspeed/con-about-lightspeed-stack-and-llama-stack.adoc

@@ -7,7 +7,7 @@ The {lcs-name} and Llama Stack deploy together as sidecar containers to augment
 
 The {lcs-name} serves as the Llama Stack service intermediary, managing configurations for key components. These components include the large language model (LLM) inference providers, Model Context Protocol (MCP) or retrieval augmented generation (RAG) tool runtime providers, safety providers, and vector database settings.
 
-* {lcs-name} manages authentication, user feedback collection, MCP server configuration, and caching.
+* {lcs-name} manages user feedback collection, MCP server configuration, and conversation history.
 
 * Llama Stack provides the inference functionality that {lcs-short} uses to process requests. For more information, see https://llamastack.github.io/docs#what-is-llama-stack[What is Llama Stack].
 

modules/developer-lightspeed/proc-customizing-the-chat-history-storage.adoc

@@ -3,23 +3,17 @@
 [id="proc-customizing-the-chat-history-storage_{context}"]
 = Customizing the chat history storage in {ls-short}
 
-By default, the {ls-short} service stores chat history using an in-memory database. This means that if you restart the Pod containing the server, the chat history is lost. You can manually configure {ls-short} to store the chat history persistently as a long-term backup with PostgreSQL by any of the following methods:
-
-* {product-very-short} Operator
-* {product-very-short} Helm chart
+By default, the {ls-short} service stores chat history in a non-persistent local SQL database within in the {lcs-short} container. This means that chat history is lost if you create and use a new {lcs-short} sidecar. You can manually configure {ls-short} to store the chat history persistently as a long-term backup with PostgreSQL by updating your {lcs-short} service configuration.
 
 +
 [WARNING]
 ====
-If you configure {ls-short} to store chat history using PostgreSQL, prompts and responses are recorded and can be reviewed by your platform administrators. If any of your user's chat history contains any private, sensitive, or confidential information, this might have data privacy and security implications that you need to assess. For users that wish to have their chat data removed, they must request their respective platform administrator to perform this action. {company-name} does not collect (or have access to) any of this chat history data.
+Configuring {ls-short} to use PostgreSQL records prompts and responses, which platform administrators can review. You must assess any data privacy and security implications if user chat history contains private, sensitive, or confidential information. For users that wish to have their chat data removed, they must request their respective platform administrator to perform this action. {company-name} does not collect or access this chat history data.
 ====
 
 .Procedure
-Customize the chat history storage using any of the following methods:
-
-* Update your {product-very-short} config file.
-** If you are using {ls-short} on an Operator-installed {product-very-short} instance, update `conversation_cache` in your {product-very-short} ConfigMap.
-** If you are using {ls-short} on a Helm-installed {product-very-short} instance, update `conversation_cache` in your `values.yaml` file.
+. Configure the chat history storage type in the {lcs-short} configuration file (`lightspeed-stack.yaml`) using any of the relevant options:
+** To enable persistent storage with PostgreSQL, add the following configuration:
 + 
 [source,yaml]
 ----
@@ -29,18 +23,17 @@ Customize the chat history storage using any of the following methods:
       host: _<your_database_host>_
       port: _<your_database_port>_
       db: _<your_database_name>_
-   	  user: _<your_user_name>_
-	    password: _<postgres_password>_
-	    ca_cert_path: postgres_cert.crt
-      ssl_mode: "require"
+      user: _<your_user_name>_
+      password: _<postgres_password>_
 ----
-
-* Update `conversation_cache` in your {lcs-short} config file:
+* To retain the default, non-persistent SQLite storage, make sure the configuration is set as shown in the following example:
 +
 [source,yaml]
 ----
- conversation_cache:
-   type: "sqlite"
-   sqlite:
-     db_path: "/tmp/cache.db"
+conversation_cache:
+  type: "sqlite"
+  sqlite:
+    db_path: "/tmp/cache.db"
 ----
+
+. Restart your {lcs-short} service to apply the new configuration.

modules/developer-lightspeed/proc-installing-and-configuring-lightspeed.adoc

@@ -34,7 +34,7 @@ You must manually install and configure the {ls-short} plugin, the {lcs-name} ({
 
 .. In the {ocp-short} web console, navigate to your {product-very-short} instance and select the *ConfigMaps* tab.
 .. Click *Create ConfigMaps*.
-.. From the *Create ConfigMap* page, select the *YAML view* option and edit the file using the following structure. This example demonstrates the configuration for the LCS ConfigMap, typically named `lightspeed-stack`, which connects to the Llama Stack service locally on port `8321`:
+.. From the *Create ConfigMap* page, select the *YAML view* option and edit the file using the following structure. This example demonstrates the configuration for the {lcs-short} ConfigMap, typically named `lightspeed-stack`, which connects to the Llama Stack service locally on port `8321`:
 +
 [source,yaml]
 ----
@@ -47,7 +47,7 @@ data:
     name: Lightspeed Core Service (LCS)
     service:
       host: 0.0.0.0
-      port: 8080
+      port: ${LIGHTSPEED_SERVICE_PORT}
       auth_enabled: false
       workers: 1
       color_log: true
@@ -376,7 +376,7 @@ You must replace the older single container configuration found in source with t
 ----
 ... Click *Save* and then Helm upgrade.
 
-. Manage authorization (RBAC): If you have users who are not administrators, you must define permissions and roles for them to use {ls-short}. The Lightspeed Backend plugin uses {backstage} RBAC for authorization.
+. Optional: Manage authorization (RBAC): If you have users who are not administrators, you must {authorization-book-link}##enabling-and-giving-access-to-rbac[define permissions and roles] for them to use {ls-short}. The Lightspeed Backend plugin uses {backstage} RBAC for authorization.
 
 ** For an Operator-installed {product-very-short} instance:
 

modules/developer-lightspeed/proc-using-developer-lightspeed-to-start-a-chat-for-the-first-time.adoc

@@ -5,7 +5,7 @@
 
 You can start a chat with {ls-short} for quick answers on a number of topics depending on your settings. You can manually start a chat with the {ls-short} or use the following sample prompts we have provided to help you get started:
 
-* *Getting Started with {product-custom-resource-type}*
+* *Getting Started with Red Hat Developer Hub*
 * *Deploy with Tekton*
 * *Create an OpenShift Deployment*