diff --git a/migration_toolkit_for_containers/mtc-release-notes.adoc b/migration_toolkit_for_containers/mtc-release-notes.adoc
index 59dd2e7673..eea37433d7 100644
--- a/migration_toolkit_for_containers/mtc-release-notes.adoc
+++ b/migration_toolkit_for_containers/mtc-release-notes.adoc
@@ -5,11 +5,12 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-The {mtc-full} ({mtc-short}) enables you to migrate stateful application workloads between {product-title} clusters at the granularity of a namespace.
+The {mtc-full} ({mtc-short}) enables you to migrate application workloads between {product-title} clusters at the granularity of a namespace.
 
-You can migrate from xref:../migrating_from_ocp_3_to_4/about-migrating-from-3-to-4.adoc[{product-title} 3.7, 3.9, 3.10, or 3.11 to {product-version}] and between {product-title} 4 clusters.
+You can migrate from xref:../migrating_from_ocp_3_to_4/about-migrating-from-3-to-4.adoc[{product-title} 3 to {product-version}] and between {product-title} 4 clusters.
 
 {mtc-short} provides a web console and an API, based on Kubernetes custom resources, to help you control the migration and minimize application downtime.
 
+// include::modules/migration-mtc-release-notes-1-6.adoc[leveloffset=+1]
 include::modules/migration-mtc-release-notes-1-5.adoc[leveloffset=+1]
 include::modules/migration-mtc-release-notes-1-4.adoc[leveloffset=+1]
diff --git a/modules/common-attributes.adoc b/modules/common-attributes.adoc
index 575a729900..6a0bbeef98 100644
--- a/modules/common-attributes.adoc
+++ b/modules/common-attributes.adoc
@@ -42,4 +42,3 @@ endif::[]
 :mtc-short: MTC
 :mtc-full: Migration Toolkit for Containers
 :mtc-version: 1.5
-:mtc-version-z: 1.5.1
diff --git a/modules/migration-mtc-release-notes-1-5.adoc b/modules/migration-mtc-release-notes-1-5.adoc
index 11e188a6e9..e9a187a489 100644
--- a/modules/migration-mtc-release-notes-1-5.adoc
+++ b/modules/migration-mtc-release-notes-1-5.adoc
@@ -5,7 +5,7 @@
 [id="migration-mtc-release-notes-1-5_{context}"]
 = {mtc-full} 1.5 release notes
 
-The release notes for {mtc-full} ({mtc-short}) version {mtc-version} describe new features, enhancements, and known issues.
+The release notes for {mtc-full} ({mtc-short}) version 1.5 describe new features, enhancements, and known issues.
 
 [id="new-features-and-enhancements-1-5_{context}"]
 == New features and enhancements
diff --git a/modules/migration-mtc-release-notes-1-6.adoc b/modules/migration-mtc-release-notes-1-6.adoc
new file mode 100644
index 0000000000..7e6e801a3c
--- /dev/null
+++ b/modules/migration-mtc-release-notes-1-6.adoc
@@ -0,0 +1,35 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+
+[id="migration-mtc-release-notes-1-6_{context}"]
+= {mtc-full} 1.6 release notes
+
+The release notes for {mtc-full} ({mtc-short}) version 1.6 describe new features and enhancements, deprecated features, and known issues.
+
+[id="new-features-and-enhancements-1-6_{context}"]
+== New features and enhancements
+
+This release has the following new features and enhancements:
+
+* State migration: You can perform repeatable, state-only migrations by selecting specific persistent volume claims (PVCs).
+
+* "New operator version available" notification: The Clusters page of the {mtc-short} web console displays a notification when a new {mtc-full} Operator is available.
+
+[id="deprecated-features-1-6_{context}"]
+== Deprecated features
+
+The following features are deprecated:
+
+* {mtc-short} version 1.4 is no longer supported.
+
+[id="known-issues-1-6_{context}"]
+== Known issues
+
+This release has the following known issues:
+
+* On {product-title} 3.10, the `MigrationController` pod takes too long to restart. The Bugzilla report contains a workaround. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1986796[*BZ#1986796*])
+
+* `Stage` pods fail during direct volume migration from a classic {product-title} source cluster on IBM Cloud. The IBM block storage plugin does not allow the same volume to be mounted on multiple pods of the same node. As a result, the PVCs cannot be mounted on the Rsync pods and on the application pods simultaneously. To resolve this issue, stop the application pods before migration. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1887526[*BZ#1887526*])
+
+* `MigPlan` custom resource does not display a warning when an AWS gp2 PVC has no available space. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1963927[*BZ#1963927*])