diff --git a/modules/release_guide/pages/sop_epel_minor_mass_branching.adoc b/modules/release_guide/pages/sop_epel_minor_mass_branching.adoc
index d1f2563..8d4d033 100644
--- a/modules/release_guide/pages/sop_epel_minor_mass_branching.adoc
+++ b/modules/release_guide/pages/sop_epel_minor_mass_branching.adoc
@@ -186,16 +186,6 @@ $ bodhi releases create \
     --no-create-automatic-updates
 ----
 
-You need to run the `bodhi openshift` playbook, so that UI will know
-about the new release. Then, you need to restart
-*fm-consumer@config.service* and *bodhi-celery.service* services on
-*bodhi-backend01.phx2.fedoraproject.org*:
-
-```
-$ sudo rbac-playbook openshift-apps/bodhi.yml
-$ sudo systemctl restart fm-consumer@config.service bodhi-celery.service
-```
-
 === Recreate targets
 
 Once mass-branching is complete and the new release exists in bodhi,
@@ -207,16 +197,6 @@ $ koji add-target epel${release_major}           epel${release}-build epel${rele
 $ koji add-target epel${release_major}-candidate epel${release}-build epel${release}-testing-candidate
 ----
 
-=== Update block_retired.py script
-
-https://pagure.io/releng/blob/main/f/scripts/block_retired.py[block_retired.py]
-script in releng repo should be updated with EPEL{epel_major} release and also
-branched release should be added to the script.
-
-Please look at this
-https://pagure.io/releng/c/9eb97f491f7a767ab8b90498adfa3b34ee235247?branch=main[block_retired.py
-commit] as an example.
-
 === Updating MirrorManager
 
 We need to update the mirrormanager so that it will point EPEL{epel_major} to the