Incorporated Judy's comments and Ben's

Author: pabel-rh

modules/openshift-ai-connector-for-rhdh/proc-populating-the-api-definition-tab.adoc

@@ -1,9 +1,9 @@
 :_mod-docs-content-type: PROCEDURE
 
 [id="proc-populating-the-api-definition-tab_{context}"]
-= Populating the API Definition tab
+= Populating the API Definition tab in {product-very-short} API entities
 
-The AI platform engineer must follow these steps to provide this valuable information because {rhoai-short} does not expose the OpenAPI specification by default.
+Since {rhoai-short} does not expose the OpenAPI specification by default, the AI platform engineer can take the following steps to provide this valuable information:
 
 .Procedure
 
@@ -24,4 +24,4 @@ We recommend using *Model Version* instead of *Registered Model* to maintain sta
 
 .. In the **Properties** section, set a key/value pair where the key is `API Spec` and the value is the entire JSON content from the `open-api.json` file.
 
-. Propagation: The {openshift-ai-connector-name} periodically polls the {rhoai-short} Model Registry, propagates this JSON, and renders the interactive API documentation in the {product-very-short} API Entity *Definition* tab.
+. Propagation: The {openshift-ai-connector-name} periodically polls the {rhoai-short} Model Registry, propagates this JSON, and renders the interactive API documentation in the *Definition* tab of the {product-very-short} API entity.

modules/openshift-ai-connector-for-rhdh/proc-troubleshooting-connector-functionality.adoc

@@ -3,7 +3,7 @@
 [id="proc-troubleshooting-connector-functionality_{context}"]
 = Troubleshooting Connector functionality
 
-The connector system consists of the two dynamic plugins and the three model catalog bridge sidecar containers. Generally speaking, the logs collected must be provided to {company-name} Support for analysis.
+The connector system consists of the two dynamic plugins and the three {openshift-ai-connector-name-short} sidecar containers. Generally speaking, the logs collected must be provided to {company-name} Support for analysis.
 
 The actual contents of the diagnostic data are not part of any product guaranteed specification, and can change at any time.
 
@@ -40,14 +40,9 @@ View the {openshift-ai-connector-name}plugins in the `backstage-backend` contain
 
 To enable debug logging, set the `LOG_LEVEL` environment variable to `debug` on the `backstage-backend` container. For more information, see {monitoring-and-logging-book-link}[{monitoring-and-logging-book-title}].
 
-== Inspecting the Model Catalog Bridge
+== Inspecting the {openshift-ai-connector-name-short}
 
-The Model Catalog Bridge sidecars manage the data fetching and storage:
-
-[IMPORTANT]
-====
-{openshift-ai-connector-name} collects feedback from users who engage with the feedback feature. If a user submits feedback, the feedback score (thumbs up or down), text feedback (if entered), the user query, and the LLM provider response are stored locally in the file system of the Pod. {company-name} does not have access to the collected feedback data.
-====
+The {openshift-ai-connector-name-short} sidecars manage the data fetching and storage:
 
 . Check Cached Data (ConfigMap): The processed AI Model metadata is stored in a `ConfigMap`.
 +

modules/openshift-ai-connector-for-rhdh/ref-enrich-ai-model-metadata.adoc

@@ -3,7 +3,7 @@
 [id="ref-enrich-ai-model-metadata_{context}"]
 = Enrich AI model metadata for enhanced {product} experience
 
-While {rhoai-short} provides essential data, an AI platform engineer using {rhoai-short} can enrich the {backstage}/{product-very-short} experience by adding custom properties to the `ModelVersion` or `RegisteredModel` (or annotations to the `KServe InferenceService` if the model registry is not used) so that the {openshift-ai-connector-name} can add the information to the {product-very-short} entities it creates. For more details, see {rhoai-docs-link}/working_with_model_registries/index#editing-model-version-metadata-in-a-model-registry_model-registry[Editing model version metadata in a model registry].
+While {rhoai-short} provides essential data, an AI platform engineer using {rhoai-short} can enrich the {backstage}/{product-very-short} experience by adding `custom properties` to the `ModelVersion` or `RegisteredModel` (or annotations to the `KServe InferenceService` if the model registry is not used) so that the {openshift-ai-connector-name} can add the information to the {product-very-short} entities it creates. For more details, see {rhoai-docs-link}/working_with_model_registries/index#editing-model-version-metadata-in-a-model-registry_model-registry[Editing model version metadata in a model registry].
 
 |===
 |Property Key |Entity Field Populated |Description

modules/openshift-ai-connector-for-rhdh/ref-model-to-entity-mapping.adoc

@@ -3,6 +3,8 @@
 [id="ref-model-to-entity-mapping_{context}"]
 = Model-to-Entity mapping
 
+{openshift-ai-connector-name-short} integrates with {openshift-ai-connector-name-short}, the model catalog, and KServe-based Model Deployments (InferenceServices). This integration automatically converts your AI/ML artifacts into familiar {backstage} entities, simplifying management and providing a unified view of your models.
+
 This offering interfaces with the {openshift-ai-connector-name-short}, model catalog, and KServe-based Model Deployments (InferenceServices) to create familiar {backstage} entities.
 
 |===

modules/openshift-ai-connector-for-rhdh/ref-openshift-ai-model-registry-and-model-catalog-queries.adoc

@@ -5,42 +5,42 @@
 
 To access the same {rhoai-short} data as the connector, use `curl` to query the {rhoai-short} model registry and model catalog APIs, ensuring the `ServiceAccount` token has correct access control:
 
-* Example: Fetch registered models
+* Example showing how to fetch registered models
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/registered_models | jq
 ----
 
-* Example: Fetch model versions
+* Example showing how to fetch model versions
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/model_versions | jq
 ----
 
-* Example: Fetch model artifacts
+* Example showing how to fetch model artifacts
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/model_artifacts | jq
 ----
 
-* Example: Fetch inference services
+* Example showing how to fetch inference services
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/inference_services | jq
 ----
 
-* Example: Fetch serving environments
+* Example showing how to fetch serving environments
 +
 [source,bash]
 ----
 curl -k -H "Authorization: Bearer $TOKEN" $RHOAI_MODEL_REGISTRY_URL/api/model_registry/v1alpha3/serving_environments | jq
 ----
 
-* Example: Fetch catalog sources
+* Example showing how to fetch catalog sources
 +
 [source,bash]
 ----