Fixed the variables in the release notes.

Author: EricPonvelle

rosa_release_notes/rosa-release-notes.adoc

@@ -19,15 +19,15 @@ toc::[]
 // [id="rosa-q3-2025_{context}"]
 // === Q3 2025
 
-// * **Updated ROSA product titles**. Previously, the product names for {rosa-classic} and {rosa-first} in the documentation were inconsistent, potentially causing confusion for users. This release updates the product names as follows:
+// * **Updated ROSA product titles**. Previously, the product names for {rosa-classic-short} and {rosa-first} in the documentation were inconsistent, potentially causing confusion for users. This release updates the product names as follows:
 // +
-// ** "Red Hat OpenShift on AWS (ROSA)" is now **{rosa-classic}** and abbreviated as {rosa-classic-short}
+// ** "Red Hat OpenShift on AWS (ROSA)" is now **{rosa-classic-short}** and abbreviated as {rosa-classic-short}
 // ** "Red Hat OpenShift on AWS (ROSA) with hosted control planes" is now **{rosa-first}** and abbreviated as **{rosa-short}**
 
 [id="rosa-q2-2025_{context}"]
 === Q2 2025
 ifdef::openshift-rosa[]
-* **AWS Trainium and Inferentia instance types now supported.** You can now use {AWS} Trainium and Inferentia instance types for your {rosa-classic} clusters. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-instance-types.adoc#rosa-sdpolicy-aws-instance-types[Red Hat OpenShift Service on AWS instance types].
+* **AWS Trainium and Inferentia instance types now supported.** You can now use {AWS} Trainium and Inferentia instance types for your {rosa-classic-short} clusters. For more information, see xref:../rosa_architecture/rosa_policy_service_definition/rosa-instance-types.adoc#rosa-sdpolicy-aws-instance-types[Red Hat OpenShift Service on AWS instance types].
 endif::openshift-rosa[]
 
 ifdef::openshift-rosa-hcp[]
@@ -99,7 +99,7 @@ endif::openshift-rosa-hcp[]
 
 // These notes need to be duplicated until the ROSA with HCP split out is completed.
 ifdef::openshift-rosa[]
-* **{rosa-classic} cluster node limit update.** {rosa-classic} clusters versions 4.14.14 and greater can now scale to 249 worker nodes. This is an increase from the previous limit of 180 nodes.
+* **{rosa-classic-short} cluster node limit update.** {rosa-classic-short} clusters versions 4.14.14 and greater can now scale to 249 worker nodes. This is an increase from the previous limit of 180 nodes.
 // Removed as part of OSDOCS-13310, until figures are verified.
 //For more information, see xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability].
 
@@ -113,7 +113,7 @@ If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to fut
 +
 For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
 
-* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {rosa-classic} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {rosa-classic} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster.
+* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {rosa-classic-short} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {rosa-classic-short} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster.
 endif::openshift-rosa[]
 
 ifdef::openshift-rosa-hcp[]