diff --git a/docs/becoming-devops.md b/docs/becoming-devops.md
index 505317bef5b1ae64f2fa7d20a3865997365123eb..0c1768a91e88ded2e045a2ea80c66b500270b826 100644
--- a/docs/becoming-devops.md
+++ b/docs/becoming-devops.md
@@ -6,17 +6,21 @@ members.
 
 ## Junior DevOps program
 
-In order be able to onboard lesser-known members of the community who still want to help out with
-DevOps topics, we started the Junior DevOps program. This program requires applicants to
+In order to become a full DevOps, the applicant must first join the Junior DevOps program. This
+program requires applicants to
 
 0) have contributed to Arch multiple times in some meaningful ways,
 1) find two sponsors, and
 2) write an application to the arch-devops mailing list.
 
 The idea of Junior DevOps is that they don't get full access to all secrets and machines as opposed
-to full DevOps and have to make operational changes in pairing session with a full DevOps.
+to full DevOps but access within the limited scope on which they have been assigned rights to work
+on. As trust grows the scope on which the Junior DevOps operates may be extended, while their
+sponsors are expected to help them learn and should feel responsible to review any meaningful
+changes.
 
 However, Junior DevOps can already help with many tasks and are expected to take charge of a given
 topic.
 
-After a lot of trust is built up, Junior DevOps may graduate to become full DevOps.
+After a lot of trust is built up, Junior DevOps may graduate to become full DevOps. This usually
+takes 3-9 months.