diff --git a/modules/oadp-release-notes-1-2-0.adoc b/modules/oadp-release-notes-1-2-0.adoc
index c84cb5299e63..bef5ce093e9e 100644
--- a/modules/oadp-release-notes-1-2-0.adoc
+++ b/modules/oadp-release-notes-1-2-0.adoc
@@ -15,13 +15,14 @@ The OADP 1.2.0 release notes include information about new features, bug fixes,
 The new `resourceTimeout` option specifies the timeout duration in minutes for waiting on various Velero resources. This option applies to resources such as Velero CRD availability, `volumeSnapshot` deletion, and backup repository availability. The default duration is 10 minutes.
 
 .AWS S3 compatible backup storage providers
-You can back up objects and snapshots on AWS S3 compatible providers.
+You can back up objects and snapshots on AWS S3 compatible providers. For more details, see xref:../../backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.adoc#migration-configuring-aws-s3_installing-oadp-aws[Configuring Amazon Web Services].
+
 
 [id="new-features-tech-preview-1-2-0_{context}"]
 === Technical preview features
 
 .Data Mover
-The OADP Data Mover enables you to back up Container Storage Interface (CSI) volume snapshots to a remote object store. When you enable Data Mover, you can restore stateful applications using CSI volume snapshots pulled from the object store in case of accidental cluster deletion, cluster failure, or data corruption.
+The OADP Data Mover enables you to back up Container Storage Interface (CSI) volume snapshots to a remote object store. When you enable Data Mover, you can restore stateful applications using CSI volume snapshots pulled from the object store in case of accidental cluster deletion, cluster failure, or data corruption. For more information, see xref:../../backup_and_restore/application_backup_and_restore/installing/oadp-using-data-mover-for-csi-snapshots-doc.adoc#oadp-using-data-mover-for-csi-snapshots-doc[Using Data Mover for CSI snapshots].
 
 :FeatureName: OADP Data Mover
 include::snippets/technology-preview.adoc[]
@@ -38,12 +39,20 @@ The following issues have been highlighted as known issues in the release of OAD
 
 .Multiple HTTP/2 enabled web servers are vulnerable to a DDoS attack (Rapid Reset Attack)
 
-The HTTP/2 protocol is susceptible to a denial of service attack because request cancellation can reset multiple streams quickly. The server has to set up and tear down the streams while not hitting any server-side limit for the maximum number of active streams per connection. This results in a denial of service due to server resource consumption. For a list of all OADP issues associated with this CVE, see the following link:https://issues.redhat.com/browse/OADP-2868?filter=12421248[Jira list].
+The HTTP/2 protocol is susceptible to a denial of service attack because request cancellation can reset multiple streams quickly. The server has to set up and tear down the streams while not hitting any server-side limit for the maximum number of active streams per connection. This results in a denial of service due to server resource consumption.
 
 It is advised to upgrade to OADP 1.2.3, which resolves this issue.
 
 For more information, see link:https://access.redhat.com/security/cve/cve-2023-39325[CVE-2023-39325 (Rapid Reset Attack)].
 
+.An incorrect hostname can be created when changing a hostname in a generated route.
+
+By default, the {product-title} cluster makes sure that the `openshift.io/host.generated: true` annotation is turned on and fills in the field for both the routes that are generated and those that are not generated.
+
+You cannot modify the value for the `.spec.host` field based on the base domain name of your cluster in the generated and non-generated routes.
+
+If you modify the value for the `.spec.host` field, it is not possible to restore the default value that was generated by the {product-title} cluster. After you restore your {product-title} cluster, the Operator resets the value for the field.
+
 [id="Upgrade-notes-1-2-0_{context}"]
 == Upgrade notes