From d1a2411a2ee25b61c283e78e17f3f7f201eaab39 Mon Sep 17 00:00:00 2001 From: KiwiTaco <122469357+kiwitaco@users.noreply.github.com> Date: Thu, 8 Jan 2026 14:59:05 -0500 Subject: [PATCH] Update jr-dev-rules.md Fixing a typo to repair a link. --- docs/developer-docs/jr-dev-rules.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/developer-docs/jr-dev-rules.md b/docs/developer-docs/jr-dev-rules.md index ba0cb212..86bf5652 100644 --- a/docs/developer-docs/jr-dev-rules.md +++ b/docs/developer-docs/jr-dev-rules.md @@ -30,11 +30,11 @@ The process to work on sets as a junior follows the roadmap below. In particular - If this is your first set as a junior, you have to submit this set plan in the #role-request forum on the [RetroAchievements Discord server](https://discord.gg/dq2E4hE), along with a link to your RA profile, a link to the page of the game you wish to work on, and a ping to @Code-Reviewer. - If you already are in the junior program, you have to submit this set plan on #jr-devs-requests. As a junior developer with at least one set published, you may claim the game while you work on your set plan, but no work is allowed prior to having your plan approved. - Once your plan is approved, develop your set. This includes RAM digging, making assets, creating achievement badges, writing clear descriptions and unique titles as well as thoroughly testing your assets. Code reviewers and fellow juniors are available to help in #jr-devs! -- [Request a review}(/developer-docs/am-i-ready-for-review) by making a **Ready for Review** post on #jr-devs-requests. Do this only when you think your set is as close to publishable as you can get it. +- [Request a review](/developer-docs/am-i-ready-for-review) by making a **Ready for Review** post on #jr-devs-requests. Do this only when you think your set is as close to publishable as you can get it. - To get approved at this step, your set must be clear of bad practices flagged by AutoCR. - Once approved at this step, your set is added to the review backlog, and you wait for an in-depth code review. During that time, it is highly recommended to read the reviews of other juniors and improve your own set awaiting review whenever you read feedback that could equally apply to your work. - Work through the **Code Review** with your code reviewer. Be ready to rework logic and learn the best practices. This is arguably your best opportunity to learn as well as to show your proficiency and understanding. -- Potentially graduate and become a developer. This cannot happen after a first set and depends on multiple factors including proficiency and trust as described below. +- [Potentially graduate](#graduation-consideration) and become a developer. This cannot happen after a first set and depends on multiple factors including proficiency and trust as described below. - Publish your set for all RA users to enjoy! ### Rules and Restrictions