diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 562e52d..50f947f 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -47,6 +47,7 @@
 *** xref:release_guide:final_freeze.adoc[Final freeze]
 *** xref:release_guide:final_RC_compose.adoc[Final RC compose]
 *** xref:release_guide:final_release.adoc[Final release]
+*** xref:release_guide:release_post_cleanup.adoc[Release Post Cleanup]
 *** xref:release_guide:release_eol.adoc[End Of Life]
 *** xref:release_guide:torrentrelease.adoc[Torrent releases]
 ** xref:releng_misc_guide:index.adoc[Releng Miscellaneous guide]
diff --git a/modules/release_guide/pages/release_post_cleanup.adoc b/modules/release_guide/pages/release_post_cleanup.adoc
new file mode 100644
index 0000000..cb13476
--- /dev/null
+++ b/modules/release_guide/pages/release_post_cleanup.adoc
@@ -0,0 +1,81 @@
+include::_partials/attributes.adoc[]
+
+= Post-Release Clean-up Documentation
+
+:page-description: Steps to clean up resources after a Fedora final release, including removing outdated content, updating configurations, and closing issues.
+
+== Overview
+
+This document outlines the necessary steps for cleaning up resources after the release of a Fedora version. It includes actions such as removing outdated content from servers, updating mirroring configurations, and closing open issues related to the release process.
+
+== Removing N_Beta from Torrents
+
+.Post-release clean-up of torrents
+[discrete]
+=== Description
+
+Remove beta versions of the Fedora release from the torrent server to prevent them from being distributed. This helps focus resources on the stable release.
+
+[discrete]
+=== Steps
+
+. SSH into `torrent01.fedoraproject.org`.
+. Navigate to the directory containing the {branched}_Beta torrents.
+. Delete the beta torrents for the {branched} version.
+. Regenerate the whitelist to exclude these torrents.
+
+== Update MirrorManager Configuration
+
+.MirrorManager redirection post-release
+[discrete]
+=== Description
+
+After the release, update MirrorManager to redirect requests from the development directory to the releases directory.
+
+[discrete]
+=== Steps
+
+. SSH into `mm-backend01.iad2.fedoraproject.org`.
+. Run the following commands to update the paths in MirrorManager:
++
+[source,subs="attributes+"]
+....
+sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Linux"
+sudo -u mirrormanager mm2_move-devel-to-release --version={branched} --category="Fedora Secondary Arches"
+....
+
+== Cleanup of RCs and Unnecessary Composes
+
+.Cleanup of unnecessary composes and RCs
+[discrete]
+=== Description
+
+Remove release candidates and unnecessary composes that are no longer needed to free up storage.
+
+[discrete]
+=== Steps
+
+. SSH into `bodhi-backend01.iad2.fedoraproject.org` or any server where Koji is mounted.
+. Perform the following:
+** Remove all directories related to Beta and Final RCs in `/pub/alt/stage/`.
+** Clean up old composes by removing all but the latest in `/mnt/koji/compose/branched/` and `/mnt/koji/compose/{branched}/`.
+** Two weeks after release: Remove directories at `/pub/fedora/linux/development/{branched}` and `/pub/fedora-secondary/development/{branched}`.
+
+== Closure of Failed Composes Issues
+
+.Closure of open issues related to failed composes
+[discrete]
+=== Description
+
+Address and close any open issues related to failed composes to maintain the health of the Fedora release process infrastructure.
+
+[discrete]
+=== Steps
+
+. Use the script available in the Fedora RelEng repository: https://pagure.io/releng/blob/main/f/scripts/misc/failed_composes_cleanup.py
++
+[source,subs="attributes+"]
+....
+python3 failed_composes_cleanup.py
+....
+. Run the script to automatically identify and close open issues.