diff --git a/modules/sysadmin_guide/pages/bodhi-deploy.adoc b/modules/sysadmin_guide/pages/bodhi-deploy.adoc
index acf4956..7de7830 100644
--- a/modules/sysadmin_guide/pages/bodhi-deploy.adoc
+++ b/modules/sysadmin_guide/pages/bodhi-deploy.adoc
@@ -9,9 +9,13 @@ Bodhi production instance: https://bodhi.fedoraproject.org
 
 Bodhi project page: https://github.com/fedora-infra/bodhi
 
+See also: xref:bodhi.adoc[Bodhi Infrastructure - Releng SOP]
+
+== Performing a bodhi upgrade
+
 === Necessary permissions
 
-Groups to be member in
+Groups to be member in:
 
 * https://github.com/orgs/fedora-infra/teams/bodhi
 * https://src.fedoraproject.org/group/infra-sig
@@ -23,8 +27,6 @@ Groups to be member in
 
 In addition you should be named as app-owner in the bodhi os playbook.
 
-== Performing a bodhi upgrade
-
 === Have the release in the official Bodhi repository ready
 
 Following steps were taken from
diff --git a/modules/sysadmin_guide/pages/fedorawebsites.adoc b/modules/sysadmin_guide/pages/fedorawebsites.adoc
index 614c407..1ff611f 100644
--- a/modules/sysadmin_guide/pages/fedorawebsites.adoc
+++ b/modules/sysadmin_guide/pages/fedorawebsites.adoc
@@ -36,7 +36,7 @@ use these keys:
 * https://labs.fedoraproject.org/
 * https://spins.fedoraproject.org/
 
-===== Steps
+==== Steps
 
 [loweralpha]
 . Get a copy of the new key(s) from the fedora-release repo, you will
diff --git a/modules/sysadmin_guide/pages/mini_initiatives.adoc b/modules/sysadmin_guide/pages/mini_initiatives.adoc
index cb81131..b415964 100644
--- a/modules/sysadmin_guide/pages/mini_initiatives.adoc
+++ b/modules/sysadmin_guide/pages/mini_initiatives.adoc
@@ -1,9 +1,9 @@
 = Mini iniative process
 
-=== How is a mini initiative created?
+== How is a mini initiative created?
 A ticket should come in to the relevant issue tracker as usual. This ticket will then be triaged as per the normal process in the daily stand up. If the amount of work involved is more than a couple of days of person hours then it will be put forward and tagged as a mini intiative with more information requested if needed.
 
-=== How to find a mini initiative?
+== How to find a mini initiative?
 Search for the mini initiative tag on the relevant tracker 
 
 * https://pagure.io/releng/issues?status=Open&tags=mini-initiative&close_status=[Releng]
@@ -11,14 +11,14 @@ Search for the mini initiative tag on the relevant tracker
 * https://pagure.io/centos-infra/issues?status=Open&tags=mini-initiative&close_status=[CentOS Infra]
 
 
-=== How is this scoped?
+== How is this scoped?
 The requester should be asked to provide as much info as possible when the ticket is first being triaged. The team will discuss it at daily stand up and estimate if it fits as a mini initiative. If the workload seems to big it can be changed to an initiative request.
 
 
-=== How are the mini initiatives prioritised?
+== How are the mini initiatives prioritised?
 The infra &  releng team have regular planning meetings, prior to each of these a poll will be carried out in the CPE team to determine the priority of the mini-initiatives and they will be worked on based on that order.
 
-=== How is the work carried out?
+== How is the work carried out?
 When a mini-initiative is started there should be a Person of Contact assigned to the ticket. This person may not necessarily do all the work but should be responsible for tracking the work and answering questions on the ticket, they will essentially act as the owner of the ticket.
 
 It is also desirable that this person should post to the appropriate lists that they are going to start work on the mini-initiative. This might allow interested people who want to help or just learn about it to join in and work on it too. Community involvemennt is encouraged.