diff --git a/.catalog-onboard-pipeline.yaml b/.catalog-onboard-pipeline.yaml
index d89fea83..4c9003c4 100644
--- a/.catalog-onboard-pipeline.yaml
+++ b/.catalog-onboard-pipeline.yaml
@@ -2,10 +2,10 @@
 apiVersion: v1
 offerings:
 # below is an example of a Deployable Architecture (DA) solution
-- name: deploy-arch-ibm-hpc # must match the offering name in the ibm_catalog.json
+- name: deploy-arch-ibm-hpc-lsf # must match the offering name in the ibm_catalog.json
   kind: solution
-  catalog_id: 8611e025-10b2-488e-8261-a7f584a5114b
-  offering_id: bf3c07f8-5a62-4289-8ea0-94dbb2b410e6
+  catalog_id: 0d89ec0d-d39a-494d-ac5b-9d940d8cc65f
+  offering_id: 1444e20a-af22-40d1-af98-c880918849cb
   # list all of the variations (flavors) you have included in the ibm_catalog.json
   variations:
     - name: Cluster-with-LSF
diff --git a/samples/configs/hpc_schematics_values.json b/samples/configs/hpc_schematics_values.json
index 7e3bc426..89273f7c 100644
--- a/samples/configs/hpc_schematics_values.json
+++ b/samples/configs/hpc_schematics_values.json
@@ -269,7 +269,7 @@
           "value": "__NULL__",
           "type": "string",
           "secure": false,
-          "description": "Provide the existing kms key name that you want to use for the IBM Cloud HPC cluster. Note: kms_key_name to be considered only if key_management value is set as key_protect.(for example kms_key_name: my-encryption-key)."
+          "description": "Provide the existing kms key name that you want to use for the IBM Spectrum LSF cluster. Note: kms_key_name to be considered only if key_management value is set as key_protect.(for example kms_key_name: my-encryption-key)."
         },
         {
           "name": "enable_vpc_flow_logs",
diff --git a/solutions/lsf/variables.tf b/solutions/lsf/variables.tf
index 0cde4d3e..ec91cf0f 100644
--- a/solutions/lsf/variables.tf
+++ b/solutions/lsf/variables.tf
@@ -475,7 +475,7 @@ variable "kms_instance_name" {
 variable "kms_key_name" {
   type        = string
   default     = null
-  description = "Provide the existing kms key name that you want to use for the IBM Cloud HPC cluster. Note: kms_key_name to be considered only if key_management value is set as key_protect.(for example kms_key_name: my-encryption-key)."
+  description = "Provide the existing kms key name that you want to use for the IBM Spectrum LSF cluster. Note: kms_key_name to be considered only if key_management value is set as key_protect.(for example kms_key_name: my-encryption-key)."
   validation {
     condition     = anytrue([alltrue([var.kms_key_name != null, var.kms_instance_name != null]), (var.kms_key_name == null), (var.key_management != "key_protect")])
     error_message = "Please make sure you are passing the kms_instance_name if you are passing kms_key_name."
diff --git a/variables.tf b/variables.tf
index 61014fff..6cef5666 100644
--- a/variables.tf
+++ b/variables.tf
@@ -1071,7 +1071,7 @@ variable "login_instance" {
     profile = "bx2-2x8"
     image   = "hpcaas-lsf10-rhel810-compute-v8"
   }]
-  description = "Number of instances to be launched for login node."
+  description = "Specify the list of login node configurations, including instance profile, image name. By default, login node is created using Fix Pack 15. If deploying with Fix Pack 14, set lsf_version to fixpack_14 and use the corresponding image hpc-lsf-fp14-compute-rhel810-v1. The selected image must align with the specified lsf_version, any mismatch may lead to deployment failures."
 }
 
 ##############################################################################
@@ -1101,7 +1101,7 @@ variable "TF_PARALLELISM" {
 ##############################################################################
 
 variable "sccwp_service_plan" {
-  description = "IBM service pricing plan."
+  description = "Specify the plan type for the Security and Compliance Center (SCC) Workload Protection instance. Valid values are free-trial and graduated-tier only."
   type        = string
   default     = "free-trial"
   validation {
@@ -1116,11 +1116,11 @@ variable "sccwp_service_plan" {
 variable "sccwp_enable" {
   type        = bool
   default     = true
-  description = "Flag to enable SCC instance creation. If true, an instance of SCC (Security and Compliance Center) will be created."
+  description = "Set this flag to true to create an instance of IBM Security and Compliance Center (SCC) Workload Protection. When enabled, it provides tools to discover and prioritize vulnerabilities, monitor for security threats, and enforce configuration, permission, and compliance policies across the full lifecycle of your workloads. To view the data on the dashboard, enable the cspm to create the app configuration and required trusted profile policies.[Learn more](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-about)."
 }
 
 variable "cspm_enabled" {
-  description = "Enable Cloud Security Posture Management (CSPM) for the Workload Protection instance. This will create a trusted profile associated with the SCC Workload Protection instance that has viewer / reader access to the App Config service and viewer access to the Enterprise service. [Learn more](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-about)."
+  description = "CSPM (Cloud Security Posture Management) is a set of tools and practices that continuously monitor and secure cloud infrastructure. When enabled, it creates a trusted profile with viewer access to the App Configuration and Enterprise services for the SCC Workload Protection instance. Make sure the required IAM permissions are in place, as missing permissions will cause deployment to fail. If CSPM is disabled, dashboard data will not be available.[Learn more](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-about)."
   type        = bool
   default     = false
   nullable    = false