diff --git a/guides/doc-Release_Notes/topics/katello.adoc b/guides/doc-Release_Notes/topics/katello.adoc
index bdd576a7aa5..13c47204f29 100644
--- a/guides/doc-Release_Notes/topics/katello.adoc
+++ b/guides/doc-Release_Notes/topics/katello.adoc
@@ -4,12 +4,25 @@
 [id="katello-headline-features"]
 == Headline features
 
-There are no headline features with Katello {KatelloVersion}.
+=== Structured APT for deb content
+
+With {KatelloVersion} all deb content will start using "structured APT" mode.
+This means that deb content published in APT repos on Katello, will no longer publish Release files under the `dists/default/` path.
+Instead, all APT repository publications will exclusively use the same repository structure (releases/distributions and components) as the remote upstream repositories they are synced from.
+
 
 [id="katello-upgrade-warnings"]
 == Upgrade warnings
 
-There are no upgrade warnings with Katello {KatelloVersion}.
+=== Strucutred APT migration for deb content
+
+For all users with deb type content, we recommend migrating that content to "structured APT" enabled mode *before* upgrading to {KatelloVersion}.
+Instructions for how to do this can be found here: https://docs.theforeman.org/3.16/Managing_Content/index-katello.html#enabling-structured-apt-content
+
+If you do not migrate your deb content before upgrading, it will be automatically migrated by the foreman-installer run after upgrading.
+However, if this automatic migration run is not fully successfull, or omitted, some of your deb type content may be left in an inconsistent state.
+This is why we recommend migrating before the upgrade, at which point you can easily re-run the migration or get help in case there is an issue.
+
 
 [id="katello-deprecations"]
 == Deprecations