OLS-1628: Remove TP language from OLS docs

Author: rh-tokeefe

about/ols-about-openshift-lightspeed.adoc

@@ -11,7 +11,13 @@ The following topics provide an overview of {ols-official} and discuss functiona
 include::modules/ols-openshift-lightspeed-overview.adoc[leveloffset=+1]
 include::modules/ols-about-product-coverage.adoc[leveloffset=+2]
 include::modules/ols-openshift-requirements.adoc[leveloffset=+1]
-include::modules/ols-large-language-model-overview.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/support/remote-health-monitoring-with-connected-clusters#about-remote-health-monitoring[About remote health monitoring]
+
+include::modules/ols-large-language-model-requirements.adoc[leveloffset=+1]
 //Xavier wanted to remove vLLM until further testing is performed.
 //include::modules/ols-about-openshift-ai-vllm.adoc[leveloffset=+2]
 include::modules/ols-supported-platforms.adoc[leveloffset=+1]

modules/ols-about-data-use.adoc

@@ -5,8 +5,8 @@
 
 {ols-official} is a virtual assistant you interact with using natural language. Using the {ols-long} interface, you send chat messages that {ols-long} transforms and sends to the Large Language Model (LLM) provider you have configured for your environment. These messages can contain information about your cluster, cluster resources, or other aspects of your environment.
 
-The {ols-long} {ols-release} release has limited capabilities to filter or redact the information you provide to the LLM. Do not enter information into the {ols-long} interface that you do not want to send to the LLM provider.
+The {ols-long} service has limited capabilities to filter or redact the information you provide to the LLM. Do not enter information into the {ols-long} interface that you do not want to send to the LLM provider.
 
-By using the {ols-long} as part of the {ols-release} release, you agree that Red Hat may use all of the messages that you exchange with the LLM provider for any purpose. The transcript recording data uses the Red Hat Insights system’s back-end, and is subject to the same access restrictions and other security policies. 
+By sending transcripts or feedback to Red{nbsp}Hat you agree that Red{nbsp}Hat can use the data for quality assurance purposes. The transcript recording data uses the back-end of the Red{nbsp}Hat{nbsp}Insights system, and is subject to the same access restrictions and other security policies. 
 
-You may email mailto:[email protected][Red Hat] and request that your data be deleted at the end of the {ols-release} release period.
+You can email mailto:[email protected][Red Hat] and request that your data be deleted.

modules/ols-large-language-model-overview.adoc renamed to modules/ols-large-language-model-requirements.adoc

@@ -3,41 +3,38 @@
 // * about/ols-about-openshift-lightspeed.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="ols-large-language-model-overview"]
-= Large Language Model (LLM) overview 
-:context: ols-large-language-model-overview
+[id="ols-large-language-model-requirements"]
+= Large Language Model (LLM) requirements
+:context: ols-large-language-model-requirements
 
 A large language model (LLM) is a type of machine learning model that can interpret and generate human-like language. When an LLM is used with a virtual assistant the LLM can interpret questions accurately and provide helpful answers in a conversational manner.
 
-As part of the {ols-release} release, {ols-long} can rely on the following Software as a Service (SaaS) LLM providers: 
+The {ols-long} service must have access to an LLM provider. The service does not provide an LLM for you, so the LLM must be configured prior to installing the {ols-long} Operator. 
+
+The {ols-long} service can rely on the following Software as a Service (SaaS) LLM providers: 
 
 * OpenAI
 
 * {azure-openai}
 
 * {watsonx}
 
-[NOTE]
-====
-Many self-hosted or self-managed model servers claim API compatibility with OpenAI. It is possible to configure the {ols-long} OpenAI provider to point to an API-compatible model server. If the model server is truly API-compatible, especially with respect to authentication, then it may work. These configurations have not been tested by Red Hat, and issues related to their use are outside the scope of {ols-release} support.
-====
-
-For {ols-long} configurations with {rhoai} or {rhelai}, you must host your own LLM provider rather than use a SaaS LLM provider.
+If you want to self-host a model, you can use {rhoai} or {rhelai} as your model provider.
 
 [id="ibm-watsonx_{context}"]
 == {watsonx}
 
-To use {watsonx} with {ols-official}, you need an account with link:https://www.ibm.com/products/watsonx-ai[IBM Cloud's watsonx].
+To use {watsonx} with {ols-official}, you need an account with link:https://www.ibm.com/products/watsonx-ai[IBM Cloud watsonx]. For more information, see the link:https://dataplatform.cloud.ibm.com/docs/content/wsj/getting-started/welcome-main.html?context=wx[Documentation for IBM watsonx as a Service].
 
 [id="open-ai_{context}"]
 == Open AI
 
-To use {openai} with {ols-official}, you need access to the {openai} link:https://openai.com/api/[API platform].
+To use {openai} with {ols-official}, you need access to the {openai} link:https://openai.com/api/[API platform]. For more information, see the link:https://platform.openai.com/docs/overview[OpenAI developer platform] documentation.
 
 [id="azure-open-ai_{context}"]
 == {azure-openai}
 
-To use {azure-official} with {ols-official}, you need access to {azure-openai}.
+To use {azure-official} with {ols-official}, you need access to link:https://azure.microsoft.com/en-us/[{azure-openai}]. For more information, see the link:https://learn.microsoft.com/en-us/azure/ai-services/openai/[Azure OpenAI documentation].
 
 [id="rhelai_{context}"]
 == {rhelai} 

modules/ols-openshift-requirements.adoc

@@ -1,8 +1,16 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/about/ols-about-openshift-lightspeed.adoc
+
 :_mod-docs-content-type: CONCEPT
-[id="ols-openshift-requirements"]
+[id="ols-openshift-requirements_context"]
 = OpenShift Requirements 
-:context: ols-openshift-requirements
 
 {ols-long} requires {ocp-product-title} 4.15 or later running on x86 hardware. Any installation type or deployment architecture is supported so long as the cluster is 4.15+ and x86-based.
 
-For the {ols-long} {ols-release} release, the cluster you use must be connected to the Internet and it must have telemetry enabled. Telemetry is enabled by default. If you are using a standard installation process for {ocp-short-name} confirm that it does not disable telemetry.
+Telemetry is enabled on {ocp-product-title} clusters by default. 
+
+* If the cluster has telemetry enabled, the {ols-long} service sends conversations and feedback to Red{nbsp}Hat by default.
+
+* If the cluster has telemetry disabled, the {ols-long} service does not send conversations and feedback to Red{nbsp}Hat.
+
+* If the cluster has telemetry enabled, and you do not want the {ols-long} service to send conversations and feedback to Red{nbsp}Hat, you must disable telemetry.