diff --git a/docs/developer-docs/save-and-password-protection.md b/docs/developer-docs/save-and-password-protection.md
index 2f6dd9b4..892f55b9 100644
--- a/docs/developer-docs/save-and-password-protection.md
+++ b/docs/developer-docs/save-and-password-protection.md
@@ -221,4 +221,4 @@ The only time there is too much save protection is if the save protection preven
 
 ## Save Protection and Save States
 
-It is very common for new jr devs to ask about save states and if those should be protected against. Keep in mind that save states are a snapshot of the memory at the moment the state was created so most save protection will not protect from loading a state where the achievement would trigger. Also since states are only allowed in softcore where the rules are less strict this isn't as essential. Most forms of save protection will protect against when you need to protect against with states as well. So overall, don't be too concerned about protecting specifically against loading a state. The purpose of save protection is to ensure that when a battery or memory card save is loaded that no achievements trigger.
+It is very common for new jr devs to ask about save states and if those should be protected against. Keep in mind that save states are a snapshot of the memory at the moment the state was created so most save protection will not protect from loading a state where the achievement would trigger. Also since states are only allowed in casual mode where the rules are less strict this isn't as essential. Most forms of save protection will protect against when you need to protect against with states as well. So overall, don't be too concerned about protecting specifically against loading a state. The purpose of save protection is to ensure that when a battery or memory card save is loaded that no achievements trigger.
diff --git a/docs/developer-docs/why-delta.md b/docs/developer-docs/why-delta.md
index ac4987c1..b19317ff 100644
--- a/docs/developer-docs/why-delta.md
+++ b/docs/developer-docs/why-delta.md
@@ -29,7 +29,7 @@ _See also: [Save and Password Protection](/developer-docs/save-and-password-prot
 
 It’s usually not actually enough to say “are these conditions true now?” to trigger an achievement. Often there are many ways to reach those conditions in a way that shouldn’t trigger the achievement, and loading a save file is one of them. A `Delta` condition _alone_ may not be sufficient for save protection, since the values in memory are still changing whenever you load a save, but they will often be a part of it.
 
-Even if your game doesn’t have save files or passwords, keep in mind that a lot of people play in Softcore where they can save and load states at any time, and ideally you’ll protect against that as well. So even games that you might not think benefit from this still can!
+Even if your game doesn’t have save files or passwords, keep in mind that a lot of people play in Casual mode where they can save and load states at any time, and ideally you’ll protect against that as well. So even games that you might not think benefit from this still can!
 
 _(Note: If the above paragraph makes you ask, “how could `Delta` prevent save states from triggering achievements, when those memory addresses would still be changing when you load a state?”, the technical answer is that save states also save the `Delta` state for conditions that read it, so loading a save state will not activate `Delta` conditions based on the pre-load state.)_
 
@@ -82,6 +82,6 @@ Mem   8-bit 0x<state> =  0xFF
 
 ### I don’t need `Delta` because there is no situation where the current frame conditions are true and the achievement shouldn’t trigger.
 
-First of all, this can never be true - see the above paragraph about save protection. Even games that don’t have a save system can be save stated in Softcore.
+First of all, this can never be true - see the above paragraph about save protection. Even games that don’t have a save system can be save stated in Casual mode.
 
 Even if you think you have the one achievement that doesn’t benefit at all from using `Delta` - well, even if that were true, adding it couldn’t hurt. It’s important to get into the habit of using it everywhere - it prevents false triggers often enough that it’s always a good decision to add, just in case.
diff --git a/docs/general/emulator-support-and-issues.md b/docs/general/emulator-support-and-issues.md
index 26e290bf..57a7bdc8 100644
--- a/docs/general/emulator-support-and-issues.md
+++ b/docs/general/emulator-support-and-issues.md
@@ -344,7 +344,7 @@ Limited microphone support.
 | **Beetle PSX HW**                               | libretro core       | Most recommended.                                                                                         |
 | **Beetle PSX**                                  | libretro core       |                                                                                                           |
 | **SwanStation**                                 | libretro core       |                                                                                                           |
-| **[DuckStation](https://www.duckstation.org/)** | Standalone emulator | There may be memory leaks and/or burn-in when using save states. This can be disruptive to softcore mode. |
+| **[DuckStation](https://www.duckstation.org/)** | Standalone emulator | There may be memory leaks and/or burn-in when using save states. This can be disruptive to casual mode. |
 
 ### PlayStation 2
 
diff --git a/docs/general/events.md b/docs/general/events.md
index 4c7092c6..7a83d232 100644
--- a/docs/general/events.md
+++ b/docs/general/events.md
@@ -131,7 +131,7 @@ An event centered around playing games from DevJam, an event for developers that
 Started in 2026, Community Hosted Events are a framework for players to host event ideas that are smaller in scope or do not meet the criteria of an event team hosted event.
 
 Unlike other events, which are hosted by the events team, these events are proposed by members of the RetroAchievements community,
-support a wider variety of event styles, are shorter, and allow softcore participation.
+support a wider variety of event styles, are shorter, and allow casual mode participation.
 However, they do not have their own badges. Instead, you earn points towards a central "Community Events" badge.
 
 To learn more about events, be sure to join the Discord server.
diff --git a/docs/general/faq.md b/docs/general/faq.md
index df6b1aee..6dc5bf50 100644
--- a/docs/general/faq.md
+++ b/docs/general/faq.md
@@ -10,14 +10,14 @@ This feature restricts the player from loading save states (creating them is sti
 Note that the only exception to altering speed is fast-forward, which is allowed.
 Essentially, you are playing the game without the game-altering enhancements emulators come with.
 
-While you will still be able to get achievements in Softcore, playing in Hardcore mode is the only way to earn a Mastery for a game, which is displayed both on your profile and on the game's page as a master of the game, as well as on the main leaderboard.
+While you will still be able to get achievements in Casual mode, playing in Hardcore mode is the only way to earn a Mastery for a game, which is displayed both on your profile and on the game's page as a master of the game, as well as on the main leaderboard.
 Playing in Hardcore will also allow you to set times, scores, or participate in miscellaneous challenges on game-specific leaderboards.
 Most events also require you to earn achievements in Hardcore, unless otherwise specified on the event page.
-Completing a game with softcore will still give you a badge to show on your profile; however, there will not be a gold border, and you won't show up as a recent master of the game.
+Completing a game in casual mode will still give you a badge to show on your profile; however, there will not be a gold border, and you won't show up as a recent master of the game.
 
 If you want to have a one-to-one replication of how you used to play retro games in the distant past, then Hardcore mode is what you are looking for.
 
-**Note**: If you want to play with the Hardcore mode disabled (also known as "Softcore"), you might experience issues.
+**Note**: If you want to play with the Hardcore mode disabled (also known as "Casual"), you might experience issues.
 See [Why you shouldn't use the load state feature](/orphaned/load-state-feature).
 
 ### What are the RetroPoints (white points)?
@@ -120,7 +120,7 @@ It's recommended to post screenshots on [imgur](https://imgur.com/) and videos o
 Also add details like:
 
 - when it was/wasn't awarded;
-- what game mode (hardcore/softcore);
+- what game mode (hardcore/casual);
 - what difficulty level or other settings you've selected;
 - how long you were playing;
 - when you most recently died or continued;
@@ -158,7 +158,7 @@ When sending a manual unlock request via the website your message <ins>must</ins
 
    - Provide a direct link to the Achievement ID(s) of the unlock(s) you’re requesting.
      - If your request contains more than three achievements then please also include a list of just the IDs in comma delimited format, ex. `123, 456, 789`.
-   - **State whether the request is for softcore or hardcore unlocks.**
+   - **State whether the request is for a casual or hardcore unlock.**
 
 2. Broken Achievement Ticket:
 
diff --git a/docs/general/glossary.md b/docs/general/glossary.md
index 6ff3045d..c3e3bb63 100644
--- a/docs/general/glossary.md
+++ b/docs/general/glossary.md
@@ -16,6 +16,14 @@ There are three different types of awards:
 * Game Awards – Given for [completing](#completion) or [mastering](#mastery) game sets.
 * Site Awards – Special awards given out for completing certain tasks
 
+## Casual
+
+Casual, formerly known as Softcore, is a mode for achievement collecting that allows you to use all of an emulator's features.
+
+Collecting every achievement in a set, in either hardcore or casual, gives you a [Completion](#completion) of the game, and a [badge](#award-badge) for your profile.
+
+See the [FAQ entry](faq.md#what-is-hardcore-mode) for more information about Hardcore/Casual mode.
+
 ## Cheevo
 
 Short for "Achievement".
@@ -33,7 +41,7 @@ On the [Emulator Support](emulator-support-and-issues.md) page, you can see what
 
 ## Completion
 
-Completion is the [softcore](#softcore) version of a [mastery](#mastery).
+Completion is the [casual mode](#casual) version of a [mastery](#mastery).
 
 You earn it for collecting every achievement in a game or [set](#set).
 
@@ -56,7 +64,7 @@ See [the dedicated page](events.md) for more information and some active events
 
 Collecting every achievement in a [set](#set) in hardcore mode gives you a [mastery](#mastery) of the game, and a badge for your profile.
 
-See the [FAQ entry](faq.md#what-is-hardcore-mode) for more information about Hardcore/Softcore mode.
+See the [FAQ entry](faq.md#what-is-hardcore-mode) for more information about Hardcore/Casual mode.
 
 ## Hash
 
@@ -99,14 +107,6 @@ You can see these by going to a game's page and navigating to the other icons ab
 
 See [the dedicated subsets page](../guidelines/content/subsets.md) for more information.
 
-## Softcore
-
-"Softcore" is a mode for achievement collecting that allows you to use all of an emulator's features. 
-
-Collecting every achievement in a set, in either hardcore or softcore, gives you a [Completion](#completion) of the game, and a [badge](#award-badge) for your profile.
-
-See the [FAQ entry](faq.md#what-is-hardcore-mode) for more information about Hardcore/Softcore mode.
-
 ## Standalone
 
 Typically, all games run on an emulator. However, some games run standalone (e.g. Final Fantasy XI and Terraria).
diff --git a/docs/general/hardcore-compliance-requirements.md b/docs/general/hardcore-compliance-requirements.md
index 8e5b712d..084c11f8 100644
--- a/docs/general/hardcore-compliance-requirements.md
+++ b/docs/general/hardcore-compliance-requirements.md
@@ -15,7 +15,7 @@ RetroAchievements features must work as intended:
 - **Achievements**: Triggers must evaluate correctly. Measured and Trigger flags must work properly. Both must be visible in the achievement list as well as displayed during gameplay when appropriate conditions are met.
 - **Rich Presence and Leaderboards**: Must function correctly.
 - **Offline queueing**: Unlocks created while offline must be securely cached and sync to RetroAchievements when connectivity returns.
-- **Save state hit storage**: Hit counts should be stored in save states. While not strictly required, this is highly recommended as it's important for debugging complex achievement logic and ensures proper functionality in softcore mode. Without this, players may experience issues and developers will have difficulty troubleshooting.
+- **Save state hit storage**: Hit counts should be stored in save states. While not strictly required, this is highly recommended as it's important for debugging complex achievement logic and ensures proper functionality in casual mode. Without this, players may experience issues and developers will have difficulty troubleshooting.
 - **Toolkit support**: If you ship a Windows version of the emulator, please investigate adding [RAIntegration DLL](https://github.com/RetroAchievements/RAIntegration) support. This is not required, but if it isn't included, a subtle info blurb will be present on our Downloads page, and players will get a very loud warning when trying to open tickets.
 - **Save file compatibility**: Save files (memory cards, SRAM, EEPROM, battery saves, etc.) should use standard formats compatible with other emulators of the same system. This is highly recommended as it benefits both users (who can switch emulators without losing progress) and developers (who can validate manual unlock requests by loading saves in emulators with RAIntegration support).
 
@@ -31,8 +31,8 @@ The following rules must be enforced in Hardcore mode:
 - **Slowdown and frame advance are disabled** in hardcore.
 - **Loading save states is ALWAYS blocked** in hardcore.
 - **Rich Presence and Leaderboards cannot be disabled** in hardcore. Disabling leaderboard popups is okay to support for either mode.
-- If the emulator supports a **"resume/quick resume" feature**, the resumed session must drop to Softcore.
-- **Mode switching**: Switching from softcore to hardcore is not allowed mid-session. **This action must result in a full reset of the game.** Switching from hardcore to softcore is allowed mid-session.
+- If the emulator supports a **"resume/quick resume" feature**, the resumed session must drop to Casual mode.
+- **Mode switching**: Switching from casual mode to hardcore mode is not allowed mid-session. **This action must result in a full reset of the game.** Switching from hardcore mode to casual mode is allowed mid-session.
 - Users should be allowed to create save states while in hardcore for debugging purposes, but those states cannot be loadable when hardcore mode is enabled.
 - Memory editors, debuggers, and/or scripting/TAS/recorded input playback are strictly prohibited.
 
@@ -67,7 +67,7 @@ The emulator, or the parent emulator it is forked from, must have been publicly
 
 ## E. Defaults and UX
 
-- When users log in to their RetroAchievements accounts, **enabling hardcore by default is recommended**, but not required. If softcore is the default, enabling hardcore must be one click/tap away and clearly indicated.
+- When users log in to their RetroAchievements accounts, **enabling hardcore by default is recommended**, but not required. If casual mode is the default, enabling hardcore must be one click/tap away and clearly indicated.
 - **Hardcore state must be visibly indicated** in the UI during play. This is normally done when the player starts a game - they can see a brief informational message saying what mode they're in.
 
 ## F. Transparency and Legality
diff --git a/docs/general/standalone-support.md b/docs/general/standalone-support.md
index 3b90782d..4359fb73 100644
--- a/docs/general/standalone-support.md
+++ b/docs/general/standalone-support.md
@@ -17,7 +17,7 @@ Standalone support for a game has strict non-negotiable requirements that must b
   - In other words, if a game is a work-in-progress, or still receiving new content via updates and DLC, it is not eligible for a standalone set at this time.
 - The proposer must be a Developer on RetroAchievements, as these achievement sets still have to follow our global [Achievement Design](https://docs.retroachievements.org/developer-docs/achievement-design.html) rules. This is not something we can trust anyone with who has not showed us their proficiency in set design before.
   - Alternatively, the proposer may suggest a standalone while being a Junior Developer or a regular user, but must do so with the support of a RetroAchievements Developer who will be in charge of set design.
-- You must be able to enforce Hardcore restrictions as shown in the [Global Leaderboard and Achievement Hunting Rules](https://docs.retroachievements.org/guidelines/users/global-leaderboard-and-achievement-hunting-rules.html). Such examples include black/whitelisting other mods and/or cheats that reduce the challenge of achievements, or disallowing multiplayer to prevent unfair advantages. These advantages should only be reserved for Softcore players, if applicable.
+- You must be able to enforce Hardcore restrictions as shown in the [Global Leaderboard and Achievement Hunting Rules](https://docs.retroachievements.org/guidelines/users/global-leaderboard-and-achievement-hunting-rules.html). Such examples include black/whitelisting other mods and/or cheats that reduce the challenge of achievements, or disallowing multiplayer to prevent unfair advantages. These advantages should only be reserved for Casual mode players, if applicable.
 - We expect you to have knowledge of the tools required to add Standalone support to a game. This varies depending on the game you are working on, with some games requiring expertise with programming languages such as C#, while other games may require extensive modding tools available which can be leveraged for developing an achievement set. Please also check out the [Standalone Integration guide](https://api-docs.retroachievements.org/connect/standalone.html) to find out how to connect your standalone project to RetroAchievements.
 - Decompilations, recompilations, and other unofficial ports are not eligible for standalone sets.
 
diff --git a/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md b/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md
index febebb99..028b8aca 100644
--- a/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md
+++ b/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md
@@ -32,19 +32,19 @@ The RetroAchievements global leaderboard is the main official community competit
 
 What is considered fair and legitimate play versus unfair (cheating) on the global leaderboard has been shaped continually by the community since it's inception. The rules below are what we expect from every player who would like to participate in the ranking system. Any indication of a player's failure to follow the rules herein may lose use of the global leaderboard, also known as **[Untracked](#untracked)** status.
 
-## Hardcore vs Softcore
+## Hardcore Mode vs Casual Mode
 
-There are two modes of play: Hardcore and Softcore.
+There are two modes of play: Hardcore and Casual.
 
 - Hardcore mode is a feature where the emulator disables save state loading, rewind and slow motion. The [fast-forward feature is the only accepted exception](#allowed-1). Users who take the global leaderboard seriously will most likely earn achievements in hardcore. Also, events will almost always require achievements to be earned in Hardcore.
-  - Note: Creating save states is allowed in hardcore and can be done to help practice an area later on in softcore, or help developers resolve tickets.
-- Softcore mode allows for emulator features such as save states, rewind, slow motion, emulator cheats, etc. This mode is much less competitive and is geared toward players who just want to do their own thing. This mode can be somewhat problematic when it comes to achievement processing; therefore, error reports are often taken with a grain of salt.
+  - Note: Creating save states is allowed in hardcore and can be done to help practice an area later on in casual mode, or help developers resolve tickets.
+- Casual mode allows for emulator features such as save states, rewind, slow motion, emulator cheats, etc. This mode is much less competitive and is geared toward players who just want to do their own thing. This mode can be somewhat problematic when it comes to achievement processing; therefore, error reports are often taken with a grain of salt.
 
 ## Untracked
 
-Users who have the Untracked status are omitted from all rankings. Their activity is hidden from view outside of their user page and their unlocks do not affect achievement statistics. This status is for users who share their accounts, have zero interest in hardcore and softcore rankings, are suspected of cheating, or actually are cheating. Untracked users can still earn achievements how they normally would, obtain mastery badges, etc.
+Users who have the Untracked status are omitted from all rankings. Their activity is hidden from view outside of their user page and their unlocks do not affect achievement statistics. This status is for users who share their accounts, have zero interest in hardcore and casual rankings, are suspected of cheating, or actually are cheating. Untracked users can still earn achievements how they normally would, obtain mastery badges, etc.
 
-Voluntary untracks can be requested through [RAdmin](https://retroachievements.org/user/RAdmin), and likewise can be reversed by resetting all progress and contacting the same account. Before requesting a voluntary untrack, remember that Softcore mode exists if your reasoning is that you prefer to use emulator features such as save states and emulator cheats.
+Voluntary untracks can be requested through [RAdmin](https://retroachievements.org/user/RAdmin), and likewise can be reversed by resetting all progress and contacting the same account. Before requesting a voluntary untrack, remember that Casual mode exists if your reasoning is that you prefer to use emulator features such as save states and emulator cheats.
 
 Involuntary untracks are done when players have violated the [Global Leaderboard](#global-leaderboard) rules. Untracked players should contact [RACheats](https://retroachievements.org/user/RACheats) for further guidance if they are involuntarily untracked and want to find out if they are eligible to be retracked.
 
@@ -103,7 +103,7 @@ Occasionally a developer might provide a save file or password for you to use to
 - Downloading a clicker game save online.
 - Begging a friend to send you his save file because your house burned down and you lost all your PC files.
 - Loading a save file for Hardcore you created while playing on a non-RA emulator.
-- Loading a save file for Hardcore you created in Softcore in order to gain Hardcore points.
+- Loading a save file for Hardcore you created in Casual mode in order to gain Hardcore points.
 
 ### 5. Do not modify the game's file(s) or memory by any means. {#not-allowed-5}
 
@@ -182,7 +182,7 @@ The other side of the coin for [allowed 2](#allowed-2). Cheat codes and debug mo
 
 Even in hardcore mode fast-forward is allowed, as a modern convenience. It's ~~almost~~ a consensus that fast-forward offers no risk to the fairplay and then it's available for everyone to use it.
 
-**NOTE**: in _softcore_ mode savestates, rewind and slow motion are also allowed, but expect to have some issues. Read in [this link Why you shouldn't use the load state feature](/orphaned/load-state-feature).
+**NOTE**: in _casual_ mode savestates, rewind and slow motion are also allowed, but expect to have some issues. Read in [this link Why you shouldn't use the load state feature](/orphaned/load-state-feature).
 
 ### 2. _When explicitly said in achievement's description_, in-game cheat codes/modes and in-game debug tools are allowed. {#allowed-2}
 
diff --git a/docs/orphaned/load-state-feature.md b/docs/orphaned/load-state-feature.md
index dd71b7cf..ec97f98c 100644
--- a/docs/orphaned/load-state-feature.md
+++ b/docs/orphaned/load-state-feature.md
@@ -1,17 +1,17 @@
 ---
 title: Why You Shouldn't Use the Load State Feature
-description: Using load states in RetroAchievements can disrupt achievement tracking, especially in softcore mode. This happens because progress resets when reloading, affecting challenges like no-damage or no-password runs.
+description: Using load states in RetroAchievements can disrupt achievement tracking, especially in casual mode. This happens because progress resets when reloading, affecting challenges like no-damage or no-password runs.
 ---
 
 # Why You Shouldn't Use the Load State Feature
 
 **Note**: currently the issue described here happens only on DuckStation standalone and RetroArch versions older than 1.9.1.
 
-## Hardcore/Softcore
+## Hardcore/Casual Mode
 
-Some users like to use the save/load state feature to save their progress in a game. As you may know, this feature isn't allowed when playing with hardcore mode. But some users aren't hardcore gamers and prefer to keep hardcore mode disabled (let's call this mode softcore).
+Some users like to use the save/load state feature to save their progress in a game. As you may know, this feature isn't allowed when playing with hardcore mode. But some users aren't hardcore gamers and prefer to keep hardcore mode disabled (let's call this casual mode).
 
-From time to time some users [report](/general/faq#how-do-i-report-a-broken-achievement) that an achievement isn't triggering, and when asked they say they were playing in softcore.
+From time to time some users [report](/general/faq#how-do-i-report-a-broken-achievement) that an achievement isn't triggering, and when asked they say they were playing in casual mode.
 
 One thing you all have to keep in mind is:
 
@@ -39,7 +39,7 @@ Examples of conditions:
 - starting the boss fight
 - the game is paused
 
-The problem with softcore is that when you load a saved state you can ruin the logic behind an achievement.
+The problem with casual mode is that when you load a saved state you can ruin the logic behind an achievement.
 
 ## Examples
 
@@ -62,7 +62,7 @@ When you are at stage 1, the emulator memorizes it, the same thing for all other
 
 Now imagine this scenario:
 
-- a softcore player started the game and played stages 1, 2 and 3
+- a casual mode player started the game and played stages 1, 2 and 3
 - they needed to stop playing when at stage 4 and then they saved a state to continue later
 - they closed the emulator
 - later they could play again, started the game, and loaded the state they saved