Update jr-dev-rules.md

docs/developer-docs/jr-dev-rules.md

@@ -9,7 +9,7 @@ description: Comprehensive guidelines for the Junior Developer Program, includin
 
 ## Overview
 
-The purpose of the Junior Developer Program is to assist interested people with learning how to create and maintain high quality achievement sets for RetroAchievements. Junior Developers are required to understand and abide by the [Developer Code of Conduct](https://docs.retroachievements.org/guidelines/users/code-of-conduct.html) except where specifically addressed by this document.
+The purpose of the Junior Developer Program is to assist interested people with learning how to create and maintain high quality achievement sets for RetroAchievements. Junior Developers are required to understand and abide by the [Developer Code of Conduct](/guidelines/users/code-of-conduct) except where specifically addressed by this document.
 
 ### Entry Requirements
 
@@ -20,7 +20,7 @@ To join the Junior Developer Program, the following requirements must be met:
 - Request the Junior Developer role in #role-request channel in the General section of the RA Discord server
   - Include your RA profile link
   - State the game for which you intend to create a set and link its RA set page or request that it be made if it does not exist
-  - Read through all [RetroAchievements Developer Docs](https://docs.retroachievements.org/developer-docs/) and fill out and post a [Set Design Plan](https://docs.google.com/spreadsheets/d/1VC2phJ9AUcZK5Ll4bVuMpJXED8QdM_nw8OdSAuLc3bI/edit#gid=0)
+  - Read through all [RetroAchievements Developer Docs](/developer-docs/) and fill out and post a [Set Design Plan](https://docs.google.com/spreadsheets/d/1VC2phJ9AUcZK5Ll4bVuMpJXED8QdM_nw8OdSAuLc3bI/edit#gid=0)
 - Unless specifically authorized by [Developer Compliance](https://retroachievements.org/messages/create?to=DevCompliance), all requirements in this section must be met to gain entry to the Junior Developer Program regardless of previous RA experience
 
 ### Rules and Restrictions
@@ -33,12 +33,12 @@ The following rules apply to all Junior Developers:
 - May not make a new claim while they have any unaddressed tickets
 - Will prioritize resolving open tickets over development of a new set. For additional information on ticket handling, see [Ticket Handling](#ticket-handling), below.
 - Not eligible to participate in collaborations
-- Not eligible to [revise](https://docs.retroachievements.org/guidelines/content/achievement-set-revisions.html) sets other than ones they've solely authored
+- Not eligible to [revise](/guidelines/content/achievement-set-revisions) sets other than ones they've solely authored
   - Must make a revision request in #jr-dev-forum detailing the revision plan. The Code Reviewer team will consider the request for approval
 - May not make a claim without Code Reviewer approval on a Dreamcast set using the [Windows CE firmware](https://retroachievements.org/game/24833), PlayStation 2, or future 6th+ generation consoles at the discretion of the Code Review team
   - Must make a development request in #jr-dev-forum after at least 1 set has been published
-- May not make a subset without Code Reviewer approval
-  - Must make subset request in #jr-dev-forum. If approved, subset is subject to [Subset Rules](https://docs.retroachievements.org/guidelines/content/subsets.html)
+- May only create a subset for games where the Junior Developer is the sole author
+  - Must make a subset request in ⁠#jr-dev-forum which includes a set plan. If approved, the subset is subject to [Subset Rules](/guidelines/content/subsets)
     - May request to create a subset in addition to a primary claim if both are for the same game
 - May make a maximum of 2 sets for hacks during the program
 
@@ -55,7 +55,7 @@ Junior Developers are expected to prioritize resolving open tickets over develop
 Junior Developers are required to ensure sets they submit for Code Review are of the highest quality they can make. If a set has known issues, Junior Developers must resolve them prior to requesting a Code Review. Code Reviewers are available to answer questions and offer guidance to assist Junior Developers with resolving issues. The following rules apply to all Junior Developers intending to submit a Code Review request:
 
 - Must follow the ["Am I Ready for Review"](https://docs.google.com/document/d/e/2PACX-1vSYRcYpyN0W8oP9Ho0YMiUutZEs-np4JDL-Be5IfuR5oyG_92wVwgwA5BkTHywK_olmzRBjpZGehKM6/pub) guide prior to requesting a Code Review
-- May not submit sets that fail to conform to the [Writing Policy](https://docs.retroachievements.org/guidelines/content/writing-policy.html) or [Code Note Standards](https://docs.retroachievements.org/guidelines/content/code-notes.html)
+- May not submit sets that fail to conform to the [Writing Policy](/guidelines/content/writing-policy) or [Code Note Standards](/guidelines/content/code-notes)
 - May not submit sets that do not have original achievement badges
 - May not submit sets that do not have Rich Presence
 - May not request a code review until at least 7 days after claiming a set
@@ -68,7 +68,7 @@ Junior Developers are required to ensure sets they submit for Code Review are of
 Participation in the Junior Developer Program is not an entitlement or right. Junior Developers are expected to take the program seriously, put forth significant effort, seek assistance when unable to figure something out, strive to make the highest quality set possible and maturely accept and apply Code Reviewer feedback. Junior developers may be temporarily or permanently removed from the program for the following reasons:
 
 - Violations of the RA Developer Code of Conduct or the rules set forth within this document
-- 1 month of [inactivity](https://docs.retroachievements.org/guidelines/developers/code-of-conduct.html#inactivity) in either active development or RA in general
+- 1 month of [inactivity](/guidelines/developers/code-of-conduct#inactivity) in either active development or RA in general
   - First time inactivity removals may request immediate restoration of Junior Developer role
   - Subsequent inactivity removals will be subject to a 30-day cool down, beginning upon demotion action. After cool down, must submit a full rejoin request per [Entry Requirements](#entry-requirements)