RetroAchievements · wescopeland · Jun 13, 2025 · Jun 13, 2025
diff --git a/docs/developer-docs/am-i-ready-for-review.md b/docs/developer-docs/am-i-ready-for-review.md
diff --git a/docs/developer-docs/developer-welcome.md b/docs/developer-docs/developer-welcome.md
diff --git a/docs/developer-docs/devjam.md b/docs/developer-docs/devjam.md
@@ -61,7 +61,7 @@ Check the links here for console-specific guidelines and info:
 |   04   | 2024-05-01 - 2024-08-31 |       [Arcade](/developer-docs/devjam/4-arcade)        |           33           |      80       |
 |   05   | 2024-09-01 - 2024-11-30 |    [PC-8001/PC-8801](/developer-docs/devjam/5-pc88)    |           25           |      40       |
 |   06   | 2024-12-01 - 2025-03-16 |      [Apple II](/developer-docs/devjam/6-appleii)      |           20           |      40       |
-|   07   | 2025-04-01 - 2025-06-30 |   [Sega CD/32X](/developer-docs/devjam/7-segacd-32x)   |           TBA          |      TBA      |
+|   07   | 2025-04-01 - 2025-06-30 |   [Sega CD/32X](/developer-docs/devjam/7-segacd-32x)   |          TBA           |      TBA      |
 
 ## Planned DevJams
 

diff --git a/docs/developer-docs/devquests.md b/docs/developer-docs/devquests.md
@@ -207,7 +207,9 @@ An English release is considered a game released in English in US, Canada, UK, o
 1. Set must have a fair share of the work done by each dev - For example, sets with extreme splits like 80%/20% would not allow credit.
 2. Must be a full set covering every aspect of the game.
 3. Each Dev must publish at least 20 achievements each.
-  - For compilations, this requirement is waived if you make a full set for one or more games in a compilation.
+
+- For compilations, this requirement is waived if you make a full set for one or more games in a compilation.
+
 4. Achievements must make sense, no fluff to fulfill requirement.
 
 ### 011 [The Genesis of RA](https://retroachievements.org/game/1280)
@@ -427,7 +429,7 @@ You must have made sets for at least 15 subgenres before opt-in. To opt-in, make
 3. Misc Tasks: Update a set in order to remove it from the following QA Hubs. Doesn't stack with a Full Set Clearing.
    - [No Dynamic RP](https://retroachievements.org/game/3083)
    - [Player-Input RP](https://retroachievements.org/game/28506)
-   - [Single Save Support](https://retroachievements.org/game/28449) 
+   - [Single Save Support](https://retroachievements.org/game/28449)
 4. No collaboration allowed.
 5. This quest does not stack with other revision DevQuests. If a set would also be eligible to DQ2 or DQ13 those quests will take priority.
 6. Sets are subject to DevQuest team approval, along with a small plan on what the dust-off will be about. Sets already in the approved DQ22 list do not require approval, only notification.
@@ -451,7 +453,6 @@ You must have made sets for at least 15 subgenres before opt-in. To opt-in, make
    - You can see this list on the `Quest23: Elligible Games Lists` sheet within the DevQuest Sheets document.
 6. You may swap lists with other participants. All participants must confirm the swap before it is performed. Muti-way swaps (three or more developers) are allowed. Swapping will reset your three-month respin timer.
 
-
 ## Wheel Spin DevQuest Rules
 
 1. You may respin 3 months after you spin. This requires and consumes your respin token for that quest

diff --git a/docs/developer-docs/emulator-setup-for-developers.md b/docs/developer-docs/emulator-setup-for-developers.md
@@ -41,7 +41,7 @@ With DuckStation, the file may be named either `RA_Integration-x64.dll` or `RA_I
 
 ![RAIntegration in DuckStation folder](/public/duckstation-raintegration-folder.png)
 
-When you run the emulator for the first time, a setup wizard will guide you through various options, including enabling and logging into RetroAchievements. Otherwise, you can find these options under Tools -> Achievements. 
+When you run the emulator for the first time, a setup wizard will guide you through various options, including enabling and logging into RetroAchievements. Otherwise, you can find these options under Tools -> Achievements.
 
 ![Achievement settings in DuckStation](/public/duckstation-achievement-settings.png)
 

diff --git a/docs/developer-docs/how-to-become-an-achievement-developer.md b/docs/developer-docs/how-to-become-an-achievement-developer.md
@@ -19,7 +19,7 @@ Follow the [guidelines on the Developer's Code of Conduct](/guidelines/developer
 
 ## Planning your Achievement Set
 
-Once you find a game to work on you need to plan your Achievement Set. Before claiming a game on site, Junior Developers must submit a set plan for approval in the `#jr-dev-forum`. 
+Once you find a game to work on you need to plan your Achievement Set. Before claiming a game on site, Junior Developers must submit a set plan for approval in the `#jr-devs-requests`.
 
 Be sure you know enough about the game to make a good set. Check the GameFAQs, wikias, watch longplay videos and try to learn more about the game, its secrets and details.
 
@@ -31,9 +31,9 @@ It's recommended that you post your plans on the official game's forum topic, so
 
 ## Claiming a Game and Beginning Development
 
-Once a set plan has been approved by a Code Reviewer, Junior Developers may claim the game and begin development. To claim a game, it must have a forum topic. If it doesn't have one already, you can ask a Code Reviewer to make one in the `#jr-dev-forum` in our Discord server.
+Once a set plan has been approved by a Code Reviewer, Junior Developers may claim the game and begin development. To claim a game, it must have a forum topic. If it doesn't have one already, you can ask a Code Reviewer to make one in the `#jr-devs-requests` in our Discord server.
 
-We recommend developing your first achievement set with a game that has 10 or fewer set requests.  This allows you to focus on the learning process and refine your skills, as initial achievement sets often benefit from iteration.  A smaller audience also helps manage initial support requests, preventing a sudden influx of tickets.
+We recommend developing your first achievement set with a game that has 10 or fewer set requests. This allows you to focus on the learning process and refine your skills, as initial achievement sets often benefit from iteration. A smaller audience also helps manage initial support requests, preventing a sudden influx of tickets.
 
 ## Required Knowledge
 
@@ -50,6 +50,7 @@ Junior Developer program graduates must demonstrate proficiency in the following
 - Producing high quality, stable sets with limited supervision
 
 Helpful initial topics to study:
+
 - [Hexadecimal notation](/developer-docs/memory-inspector#decimal-binary-and-hexadecimal-notations)
 - [Mem/Delta relationships](/developer-docs/delta-values)
 - Various memory sizes
@@ -75,7 +76,7 @@ The [Real Examples](/developer-docs/real-examples) and [Achievement Templates](/
 
 ## Requesting a Code Review
 
-After creating the achievement set, publish it to Unofficial and then create a post in `#jr-dev-forum`. Follow all of the requirements for [requesting a Code Review.](/developer-docs/jr-dev-rules.html#code-review-requests)
+After creating the achievement set, publish it to Unofficial and then create a post in `#jr-devs-requests`. Follow all of the requirements for [requesting a Code Review.](/developer-docs/jr-dev-rules.html#code-review-requests)
 
 ## When Will I Be Promoted to Developer?
 
@@ -85,6 +86,6 @@ The Code Reviewer team will consider a Junior Developer for graduation largely b
 
 - Their ability to publish work that meets or exceeds the standards of the [Developer's Code of Conduct](/guidelines/developers/code-of-conduct)
 - The quality and complexity of their work
-    - High quality is defined as strong set design, writing, badges, code notes and achievement logic
+  - High quality is defined as strong set design, writing, badges, code notes and achievement logic
 - The time and thought they put into planning and working on achievements
 - Showing the will to use the Developer status with care and responsibility
diff --git a/docs/developer-docs/jr-dev-rules.md b/docs/developer-docs/jr-dev-rules.md
@@ -32,7 +32,7 @@ The purpose of the Set Review is to ensure Junior Developers have a solid baseli
 
 Once a set plan is approved, Junior Developers may begin work on set development.
 
-Note: New Junior Developers who had a set plan approved when requesting to join the Junior Developer may immediately begin work on the set once they are onboarded and have made a claim on the set for which their initial plan was approved. 
+Note: New Junior Developers who had a set plan approved when requesting to join the Junior Developer may immediately begin work on the set once they are onboarded and have made a claim on the set for which their initial plan was approved.
 
 ### Rules and Restrictions
 
@@ -45,25 +45,26 @@ The following rules apply to all Junior Developers:
 - 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
 - May only [revise](/guidelines/content/achievement-set-revisions) sets where the Junior Developer is the sole author of the existing set.
-  - Must make a revision request in #jr-dev-forum detailing the revision plan. The Code Reviewer team will consider the request for approval
+  - Must make a revision request in #jr-devs-requests detailing the revision plan. The Code Reviewer team will consider the request for approval
 - May not make a claim on any GameCube set
-- May not make a claim without Code Reviewer approval on sets for the below consoles. Junior Developers must make a development request in #jr-dev-forum after at least 1 set has been published, with approval at the discretion of the Code Reviewer team
+- May not make a claim without Code Reviewer approval on sets for the below consoles. Junior Developers must make a development request in #jr-devs-requests after at least 1 set has been published, with approval at the discretion of the Code Reviewer team
   - PlayStation 2
   - PlayStation Portable
   - Any future 6th+ generation consoles, unless specifically allowed
   - Dreamcast games using the [Windows CE firmware](https://retroachievements.org/game/24833)
 - 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)
+  - Must make a subset request in ⁠#jr-devs-requests 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 1 set for a hack during the program
 
 ### Ticket Handling
+
 Junior Developers are expected to prioritize resolving open tickets over development of a new set.
 
 - If a ticket is in Request status while waiting for information from the reporter, they may continue work on a new set, but must immediately reprioritize the ticket(s) once the reporter responds
-  - To put a ticket into Request status, ask the Code Reviewers, using the #jr-dev-forum, to transfer the ticket to the reporter after you have requested further information by asking the reporter using a comment on the ticket.
+  - To put a ticket into Request status, ask the Code Reviewers, using the #jr-devs-requests, to transfer the ticket to the reporter after you have requested further information by asking the reporter using a comment on the ticket.
 - Once you have fully addressed the ticket, leave a comment on the ticket describing what the cause of the issue was and what you did to resolve the issue.
-- Contact the Code Reviewers, using the #jr-dev-forum, to resolve ot close the ticket as appropriate after your comment has been made.
+- Contact the Code Reviewers, using the #jr-devs-requests, to resolve ot close the ticket as appropriate after your comment has been made.
 
 ### Code Review Requests
 

diff --git a/docs/developer-docs/unsupported-emulators-and-cores.md b/docs/developer-docs/unsupported-emulators-and-cores.md
@@ -199,7 +199,7 @@ description: Information about unsupported emulators and cores for RetroAchievem
 
 - ⌛ BizHawk core: **Mupen64Plus**
   - Testing (there are some graphical issues that can be fixed using the angrylion plugin)
- 
+
 ## Nintendo DS
 
 - ❌ libretro core: **DeSmuME 2015**
@@ -233,7 +233,6 @@ description: Information about unsupported emulators and cores for RetroAchievem
 
 ## PC-8800
 
-
 ## PC-9800
 
 - ❌ _Not supported_ - needs hashing method and memory map

diff --git a/docs/es/developer-docs/how-to-become-an-achievement-developer.md b/docs/es/developer-docs/how-to-become-an-achievement-developer.md
@@ -19,7 +19,7 @@ Estos requisitos también son una lista de verificación para los revisores de c
 Sigue las [directrices del código de conducta del desarrollador](/es/guidelines/developers/code-of-conduct#working-on-empty-sets) para encontrar un juego.
 Asegúrate de que el juego cumpla con las [reglas y restricciones (EN)](/developer-docs/jr-dev-rules#rules-and-restrictions) antes de trabajar en logros.
 Para reclamar un juego, debe tener un tema en el foro.
-Si no tiene uno, puedes pedir a un revisor de código que cree uno en el `#jr-dev-forum` en nuestro servidor de Discord.
+Si no tiene uno, puedes pedir a un revisor de código que cree uno en el `#jr-devs-requests` en nuestro servidor de Discord.
 Siéntete libre de declarar tus intenciones de trabajar en el juego en el tema, y publicar actualizaciones a medida que avanzas.
 
 **Consejo**: para tu primer set de logros se recomienda elegir un juego que aún no tenga logros **y** que no sea muy popular.
@@ -104,7 +104,7 @@ Para familiarizarte con estas técnicas, debes practicar. **Puedes usar cualquie
 
 ## Revise su trabajo
 
-Después de haber creado varios logros, súbelos a Unofficial y luego crea una publicación en `#jr-dev-forum` en nuestro servidor de Discord (si no usas Discord, envía un mensaje a [RAdmin](http://retroachievements.org/user/RAdmin)) y pide que alguien revise tu trabajo.
+Después de haber creado varios logros, súbelos a Unofficial y luego crea una publicación en `#jr-devs-requests` en nuestro servidor de Discord (si no usas Discord, envía un mensaje a [RAdmin](http://retroachievements.org/user/RAdmin)) y pide que alguien revise tu trabajo.
 
 **NO** pidas a otro desarrollador que promueva tus logros a Core sin una revisión adecuada.
 

diff --git a/docs/es/general/faq.md b/docs/es/general/faq.md
@@ -121,7 +121,7 @@ El hash de RA es una cadena única de 32 números hexadecimales, para distinguir
 
 ### ¿Cómo solicito un desbloqueo manual?
 
-- Si usas [Discord](https://discord.gg/dq2E4hE), escribe una solicitud en el canal [#manual-unlock (desbloqueo manual)](https://discord.com/channels/310192285306454017/1029858289221116104) siguiendo el formato que hay en el [mensaje fijado de este hilo](https://discord.com/channels/310192285306454017/1029858289221116104/threads/1029875838327463966).
+- Si usas [Discord](https://discord.gg/dq2E4hE), escribe una solicitud en el canal [#unlock-requests (desbloqueo manual)](https://discord.com/channels/310192285306454017/1029858289221116104) siguiendo el formato que hay en el [mensaje fijado de este hilo](https://discord.com/channels/310192285306454017/1029858289221116104/threads/1029875838327463966).
 
 - Si no usas [Discord](https://discord.gg/dq2E4hE). Estando logueado en **RetroAchievements.org** [envía un mensaje privado](https://retroachievements.org/createmessage.php?t=RAdmin) al usuario [RAdmin](https://retroachievements.org/user/RAdmin) con el título: **Manual Unlock Request (Petición de desbloqueo manual)**
   y una descripción que sea similar a esta:
@@ -144,7 +144,7 @@ El hash de RA es una cadena única de 32 números hexadecimales, para distinguir
    1. Capturas de pantalla que muestren que se está jugando en HARDCORE y se ha completado el logro.
    2. **Video (aún mejor)** ([ejemplo perfecto de prueba proporcionada por gr1nya](https://youtu.be/uqD-GTkZbLo)).
    3. Ejemplos de logros que hayas conseguido que demuestren que has ganado el logro. Por ejemplo: Has conseguido el logro de 10 000 puntos, pero el de 5000 puntos no se te ha concedido.
-3. Si estás en nuestro servidor discord, envía un mensaje al canal de [#manual-unlock (desbloqueo manual)](https://discord.gg/FswPDnu) añadiendo **@manual-unlock**. Si no es el caso, [envía un mensaje privado](https://retroachievements.org/createmessage.php?t=RAdmin) al usuario [RAdmin](https://retroachievements.org/user/RAdmin). El mensaje debe contener:
+3. Si estás en nuestro servidor discord, envía un mensaje al canal de [#unlock-requests (desbloqueo manual)](https://discord.gg/FswPDnu) añadiendo **@manual-unlock**. Si no es el caso, [envía un mensaje privado](https://retroachievements.org/createmessage.php?t=RAdmin) al usuario [RAdmin](https://retroachievements.org/user/RAdmin). El mensaje debe contener:
    1. El enlace al ticket. Puedes encontrar el ticket aquí: http://retroachievements.org/ticketmanager.php
    2. En qué modo estabas jugando (HARDCORE/softcore)
    3. Enlace a la [prueba certificada](#qualified-proof) de completado. Incluye una prueba de que el logro se consiguió en HARDCORE, si estabas jugando en HARDCORE.

diff --git a/docs/general/contributing-to-the-docs.md b/docs/general/contributing-to-the-docs.md
@@ -241,9 +241,9 @@ Results:
 
 | First Header | Second Header | Third Header |
 | :----------- | :-----------: | -----------: |
-| Left         | Center        | Right        |
-| Left         | Center        | Right        |
-| Left         | Center        | Right        |
+| Left         |    Center     |        Right |
+| Left         |    Center     |        Right |
+| Left         |    Center     |        Right |
 
 ## VitePress Components