Typographical Fixes (#71)

THE-Spellchecker · web-flow · commit fcc12aba30e8 · 2024-07-13T09:19:27.000-04:00
diff --git a/docs/developer-docs/achievement-design.md b/docs/developer-docs/achievement-design.md
@@ -280,5 +280,5 @@ Challenge Achievements are your chance to show players how to play their favorit
 ## External Resources
 
 - [Best practices achievement creation guide](http://www.voidcn.com/article/p-gmokauqn-bgh.html) written by Jeff Sullivan, Developer Account Manager of XNA Developer Connection (XDC) regarding XBox 360 Achievements.
-- [Make them Work for it](https://gamedevelopment.tutsplus.com/articles/make-them-work-for-it-designing-achievements-for-your-games--gamedev-3371) an achievement design guide written by by Darran Jamieson on 1 Jan 2013.
+- [Make them Work for it](https://gamedevelopment.tutsplus.com/articles/make-them-work-for-it-designing-achievements-for-your-games--gamedev-3371) an achievement design guide written by Darran Jamieson on 1 Jan 2013.
 - [The Achievement Machine: Understanding Xbox 360 Achievements in Gaming Practices](http://gamestudies.org/1101/articles/jakobsson) - by Mikael Jakobsson
diff --git a/docs/developer-docs/achievement-templates.md b/docs/developer-docs/achievement-templates.md
@@ -85,7 +85,7 @@ We want to award if the player finishes the level `N` while time is greater than
 
 In this example we consider a game where there is no in-game timer to use for a speed run.
 
-We want to award if the player finishes the level `N` before a a time `T` in the level, calculated as number of frames, has passed.
+We want to award if the player finishes the level `N` before a time `T` in the level, calculated as number of frames, has passed.
 
 | ID  | Flag      | Type  | Memory  | Cmp | Type  | Mem/Val | Hits           |
 | --- | --------- | ----- | ------- | --- | ----- | ------- | -------------- |
diff --git a/docs/developer-docs/console-specific-tips.md b/docs/developer-docs/console-specific-tips.md
@@ -139,7 +139,7 @@ Pointers always start with a `0x02`. For example, a pointer pointing directly to
 
 ### Mandatory UniBIOS protection
 
-UniBIOS allows several debugging options, and also access the database of individual cheats for every game. Therefore all achievements for Neo Geo need to be protected from abusing it. The simpliest solution here is disallowing UniBIOS usage completely, directly from the level of achievement code.
+UniBIOS allows several debugging options, and also access the database of individual cheats for every game. Therefore all achievements for Neo Geo need to be protected from abusing it. The simplest solution here is disallowing UniBIOS usage completely, directly from the level of achievement code.
 
 Fortunately part of UniBIOS data seems to be reflected in two address strings in the RAM: `0x00fe30` and `0x00fe50`. While UniBIOS is active `0x00fe30` in 32-bit size seems to always brings the same value (for every Neo Geo game) which is `80025632`, and it doesn't seem to change after the ROM was loaded. For any other BIOS, the value is always 0, (except for the moment the RAM is overloaded by the diagnostic program, after the ROM was loaded).
 
diff --git a/docs/developer-docs/devquests.md b/docs/developer-docs/devquests.md
@@ -151,7 +151,7 @@ No hacks or homebrew unless those are the only types of games left without sets.
 **Goal**: Develop a set for one of the most requested games  
 **Repeatable**: No
 
-::: info Set Elligibility
+::: info Set Eligibility
 At the time you claim the set, it must be in Most Wanted section of the latest issue of RANews.
 :::
 
@@ -187,7 +187,7 @@ An English release is considered a game released in English in US, Canada, UK, o
 **Repeatable**: No
 
 - Must be a full set (to the extent of the games capabilities, See Watara vs PSP)
-- Smaller consoles may be ruled inelligible
+- Smaller consoles may be ruled ineligible
 
 #### Current Launch Party Promotion Windows:
 - Neo Geo CD: 2023-11-15 through 2024-05-15
@@ -245,7 +245,7 @@ An English release is considered a game released in English in US, Canada, UK, o
 1. Choose from a provided list or grab one from a hub, just make sure you let us know when you start so we can mark it!
 2. Must go through the revision process as per usual!
 3. Make sure you take care with the set and don't just throw in a bunch of filler
-4. Don't hestitate to contact us with any questions or suggestion<br>• This quest can be done multiple times (current limit: 3)
+4. Don't hesitate to contact us with any questions or suggestion<br>• This quest can be done multiple times (current limit: 3)
 
 ### 014 [Laudable Leaderboards](https://retroachievements.org/game/862)
 
@@ -301,7 +301,7 @@ You must have developed sets for 10 or more supported platforms before opt-in. O
 2. Must be full sets containing all content and challenges appropriate to the game.
 3. The person that wrote the Wish This Set may not be one of the developers making the set.
 4. Quest is available year round, and gets new games eligible every release of RANews.
-5. If you already have a set claimed at the time it becomes elligible for this DevQuest you must be under 50% progress for it to count.
+5. If you already have a set claimed at the time it becomes eligible for this DevQuest you must be under 50% progress for it to count.
 6. Once a game has been featured it remains eligible until the game gets a set.
 
 
@@ -317,7 +317,7 @@ You must have developed sets for 10 or more supported platforms before opt-in. O
 2. Must be full sets containing all content and challenges appropriate to the game.
 3. No Homebrew/Hacks/Unlicensed
 4. New sets only: No Multi Set or Revisions
-5. Other picks are subject to DQ team approval if elligibility is questionable
+5. Other picks are subject to DQ team approval if eligibility is questionable
 7. Collaborations must be approved by the DevQuest team; games done via collaboration must have sufficient content or modes to justify qualifying.
 
 ### 018 [Subset Station](https://retroachievements.org/game/22564)
@@ -411,7 +411,7 @@ You must have made sets for at least 15 subgenres before opt-in. To opt-in, make
 ## Wheel Spin DevQuest Rules
 
 1. You may respin 3 months after you spin. This requires and consumes your respin token for that quest
-2. You start with one respin token (per aplicable DevQuest)
+2. You start with one respin token (per applicable DevQuest)
 3. Each wheel spin quest has its own kind of respin token (can't save your DevQuest 006 token for use in DevQuest 019)
 3. You may not bank extra respin tokens
 4. Once you have used your respin token, you may restore it by fulfilling one of the Respin Tasks, listed below
diff --git a/docs/developer-docs/difficulty-scale-and-balance.md b/docs/developer-docs/difficulty-scale-and-balance.md
@@ -95,7 +95,7 @@ Very few player can get these on their first attempt, perhaps if they already kn
 
 Only the rarest of players can complete these on a first attempt. Most can complete it after many attempts, Many players will drop off here and won't be willing to complete the set unless they are completionists or fans of the game. Many are not able to complete this after very many attempts. Usually takes significant practice, high skills, experience, research, or guides to complete.
 
-**Examples:** Beating Contra in one life. Escaping Zebes (Super Metroid) in under two minutes. Beating many of the Megaman bosses without taking damage. Many damagless stages, depending on the game.
+**Examples:** Beating Contra in one life. Escaping Zebes (Super Metroid) in under two minutes. Beating many of the Megaman bosses without taking damage. Many damageless stages, depending on the game.
 
 ### 6 - Super Hard
 
diff --git a/docs/developer-docs/getting-started-as-an-achievement-developer.md b/docs/developer-docs/getting-started-as-an-achievement-developer.md
@@ -116,7 +116,7 @@ Next we will change these values to the following:
 
 With that set, we don't have any more conditions to add, so we return to the **Achievements Dialog**. To be safe, we should save our progress by hitting **Save Local**! This saves everything to file locally to ensure that we won't lose any progress.
 
-- **Note**: An achievement should have more than one requirement to avoid it triggering at the wrong time (i.e. playing demo mode). In this example, we are using only one requirement to simplify the explanation. See more [Achievement Creation Tips here](/developer-docs/tips-and-tricks#achivement-creation-tips).
+- **Note**: An achievement should have more than one requirement to avoid it triggering at the wrong time (i.e. playing demo mode). In this example, we are using only one requirement to simplify the explanation. See more [Achievement Creation Tips here](/developer-docs/tips-and-tricks#achievement-creation-tips).
 
 ## Testing the Achievement
 
diff --git a/docs/developer-docs/how-to-become-an-achievement-developer.md b/docs/developer-docs/how-to-become-an-achievement-developer.md
@@ -47,7 +47,7 @@ Any aspiring dev must demonstrate understanding of the following concepts:
 - [Alt Groups](/developer-docs/alt-groups)
 - Memory sizes: [8-bit](/developer-docs/memory-inspector#8-bit-mode) and [single bit](/developer-docs/memory-inspector#single-bits)
 - Achievement logic comparisons besides `=`, such as `>`, `<`, `!=`
-- [Adding badges to an achievment](/general/ways-to-contribute)
+- [Adding badges to an achievement](/general/ways-to-contribute)
 - [Creating accurate descriptions for achievements](/guidelines/developers/code-of-conduct#basic-achievement-design-guidelines)
 - Add appropriate [protections](/developer-docs/getting-started-as-an-achievement-developer#important-tips)
 - Make a [stable achievement set](/developer-docs/getting-started-as-an-achievement-developer#important-tips)
diff --git a/docs/developer-docs/recall.md b/docs/developer-docs/recall.md
@@ -9,7 +9,7 @@ description: Learn how to use the Recall operand type to represent a previously
 This feature will be available at the RA_Integration version 1.4 milestone for developers, with support to be added for rcheevos version 11.4 milestone.
 :::
 
-A `Recall` value is the the last value stored by the [`Remember` Flag](/developer-docs/flags/remember)
+A `Recall` value is the last value stored by the [`Remember` Flag](/developer-docs/flags/remember)
 
 The `Recall` accumulator's value is for the current frame's evaluation of logic. It does not persist between evaluations and does not maintain its value for use in a later evaluation. Each group (Core, Alt1, Alt2, etc) has its own separate `Recall` accumulator; a value remembered in one group therefore cannot be recalled in another group. Using `Recall` before a value is remembered in using the `Remember` condition will generate a warning in the asset editor.
 
diff --git a/docs/developer-docs/rich-presence.md b/docs/developer-docs/rich-presence.md
@@ -148,7 +148,7 @@ As of the 1.0 version of the DLL, you can use predefined macros for the most com
 | :---------------: | :---------: | --------------------------------------------------------------------------------------------------------------------- |
 |    `@Number()`    |   `VALUE`   | A generic value with no leading zeroes                                                                                |
 |    `@Score()`     |   `SCORE`   | A generic value, padded with leading zeroes to six digits                                                             |
-| `@Centiseconds()` | `MILLISECS` | The number of hundreths of a second elapsed, and will be formatted as `00:00.00`                                      |
+| `@Centiseconds()` | `MILLISECS` | The number of hundredths of a second elapsed, and will be formatted as `00:00.00`                                      |
 |   `@Seconds()`    |   `SECS`    | The number of seconds elapsed, and will be formatted as `00:00`                                                       |
 |   `@Minutes()`    |  `MINUTES`  | The number of minutes elapsed, and will be formatted as `0h00`                                                        |
 |    `@Float1()`    |  `FLOAT1`   | A floating point number, formatted with one digit after the decimal                                                   |
diff --git a/docs/developer-docs/rollouts.md b/docs/developer-docs/rollouts.md
@@ -6,7 +6,7 @@ Rollouts are events that are meant to mimic a console launch. Developers partici
 
 ## General Guidelines
 
-It's worth noting that these are general guidelines that apply to all rollouts. Individual rollouts may require addtional guidelines.
+It's worth noting that these are general guidelines that apply to all rollouts. Individual rollouts may require additional guidelines.
 
 - Each rollout needs a coordinator/manager to handle a variety of tasks to ensure the rollout goes smoothly.
 
diff --git a/docs/developer-docs/save-and-password-protection.md b/docs/developer-docs/save-and-password-protection.md
@@ -11,7 +11,7 @@ Save and password protection is something that needs to be implemented on any se
 
 ## What Is It?
 
-Save and password protection is using conditions to prevent an achievement from unlocking upon loading a save or loading from a password. Since memory will initialize upon loading a save, many achivements could trigger at this time if it isn't present. This is to ensure that players can't go download a save from a website and use it to unlock most of the set.
+Save and password protection is using conditions to prevent an achievement from unlocking upon loading a save or loading from a password. Since memory will initialize upon loading a save, many achievements could trigger at this time if it isn't present. This is to ensure that players can't go download a save from a website and use it to unlock most of the set.
 
 What save and password protection does not do is prevent players from using their own saves or passwords. It does not mean doing something like blocking the achievement if the player visits the save or load screen (unless the achievement specifically forbids using saves).
 
@@ -96,7 +96,7 @@ If you do not have a game state, you can often check that the location ID is sta
 
 ### Delta Checks
 
-This is simply checking that the delta of something is or is not true. Most often this will be used in AddSource chains to check that something is going fron n-1 to n, but also can be used for things like score to check that the delta is greater than 0 and less than the target. One can also check that the delta of the game state isn't the save/load screen for a very simple, but solid form of protection. This also can involve something like checking that a stage goes from complete to incomplete or the player goes from stage 1 to stage 2 or from stage 1 back to the hub world.
+This is simply checking that the delta of something is or is not true. Most often this will be used in AddSource chains to check that something is going from n-1 to n, but also can be used for things like score to check that the delta is greater than 0 and less than the target. One can also check that the delta of the game state isn't the save/load screen for a very simple, but solid form of protection. This also can involve something like checking that a stage goes from complete to incomplete or the player goes from stage 1 to stage 2 or from stage 1 back to the hub world.
 
 | ID  | Flag      | Type  | Memory        | Cmp | Type  | Mem/Val | Hits |
 | ---:|:--------- |:----- |:------------- |:---:|:----- |:------- |:----:|
@@ -125,7 +125,7 @@ This isn't as commonly used, especially by itself, but is great when dealing wit
 
 In this case, the event happens in a common hub location where players are often going to save. On top of that, the game even prompts the player to save right after the event happens and when they load that save, it will be in the same location as the event.  Plus the game allows the player to save and load at any point outside of battle and cutscenes. That's a big problem since in this case a player could unlock the achievement by loading a save with many other types of save protection.
 
-So a prior is used on the location id in conditon 1 to ensure that the player got to that location via playing the game as normal rather than loading a save. Upon loading a save, the prior would be 0 or the value from another save so that condition would not be true. When playing as normal the prior would be the value in condition 1.
+So a prior is used on the location id in condition 1 to ensure that the player got to that location via playing the game as normal rather than loading a save. Upon loading a save, the prior would be 0 or the value from another save so that condition would not be true. When playing as normal the prior would be the value in condition 1.
 
 | ID  | Flag | Type  | Memory        | Cmp | Type  | Mem/Val       | Hits |
 | ---:|:---- |:----- |:------------- |:---:|:----- |:------------- |:----:|
@@ -168,7 +168,7 @@ Another great use of event flags for save protection is to check that the delta
 
 **Does not work well in:**
 
-- Achivements for optional events that aren't missable
+- Achievements for optional events that aren't missable
 - Achievements where sequence breaking is possible
 - Games with large spans of time between events (especially if the player can save before the next event)
 - Events that can be done in any order.
@@ -177,7 +177,7 @@ Another great use of event flags for save protection is to check that the delta
 
 A solid form of save protection for games where the player can save or load at any time. There are two ways this can be implemented:
 
-1. Checking that the timer is not a default value: Typically this will be a simple delta check on the timer that it is either not 0 or whatever the intial value is for the game.
+1. Checking that the timer is not a default value: Typically this will be a simple delta check on the timer that it is either not 0 or whatever the initial value is for the game.
 
 | ID  | Flag | Type  | Memory       | Cmp | Type  | Mem/Val         | Hits |
 | ---:|:---- |:----- |:------------ |:---:|:----- |:--------------- |:----:|
@@ -194,7 +194,7 @@ A solid form of save protection for games where the player can save or load at a
 
 2. Using SubSource to check for large changes in the timer: 
 
-During most of gameplay this will remain true, but when a save is loaded this will not be true for a single frame, which is the most essential frame where the memory initializes. Thus it will prevent the achievements from unlocking when changing to a diffrent save or loading a save from the title screen.
+During most of gameplay this will remain true, but when a save is loaded this will not be true for a single frame, which is the most essential frame where the memory initializes. Thus it will prevent the achievements from unlocking when changing to a different save or loading a save from the title screen.
 
 | ID  | Flag      | Type  | Memory       | Cmp | Type  | Mem/Val          | Hits |
 | ---:|:--------- |:----- |:------------ |:---:|:----- |:---------------- |:----:|
diff --git a/docs/developer-docs/tips-and-tricks.md b/docs/developer-docs/tips-and-tricks.md
@@ -6,7 +6,7 @@
 
 See also: [Memory Inspector Overview](/developer-docs/memory-inspector).
 
-- Start with 8-bit view in the Memory Viewer. Looking at larger chunks of memory will complicate things, but it will make a seasoned developer's job easier. If you're just starting out and unaware of terms like **endianess** and **bit ordering** (or when the eyes are tired), its best to make your observations in 8-bit view. Its just easier!
+- Start with 8-bit view in the Memory Viewer. Looking at larger chunks of memory will complicate things, but it will make a seasoned developer's job easier. If you're just starting out and unaware of terms like **endianness** and **bit ordering** (or when the eyes are tired), its best to make your observations in 8-bit view. Its just easier!
 
 - **Uncheck "Show Decimal Values"** in the Achievement Editor so you can enter the hex values you see in the Memory Viewer. Its better than using a programmers calculator!
 
diff --git a/docs/general/about-us.md b/docs/general/about-us.md
@@ -77,7 +77,7 @@ The team responsible to keep the this community a healthy place (at least for th
 
 ### Developer Compliance Team
 
-The team responsible for the adherance and driving updates to the [Developer's Code of Conduct](/guidelines/developers/code-of-conduct).
+The team responsible for the adherence and driving updates to the [Developer's Code of Conduct](/guidelines/developers/code-of-conduct).
 
 - [Bryan1150](https://retroachievements.org/user/Bryan1150)
 - [DoctorV](https://retroachievements.org/user/DoctorV)
diff --git a/docs/general/emulator-support-and-issues.md b/docs/general/emulator-support-and-issues.md
@@ -444,7 +444,7 @@ description: Comprehensive guide to emulator support and compatibility for Retro
 - ✅ libretro core: **Beetle PSX**
 - ✅ libretro core: **SwanStation**
 - ❌ libretro core: **PCSX ReARMed**
-  - BIOS are not required for this core and will zero out the Kernal RAM.
+  - BIOS are not required for this core and will zero out the Kernel RAM.
   - Technically supported; not recommended.
 - ❓ BizHawk core: **Octoshock** (Mednafen)
 - ❓ BizHawk core: **Nymashock** (Mednafen)
@@ -461,7 +461,7 @@ description: Comprehensive guide to emulator support and compatibility for Retro
   - Still in alpha state
   - Does not expose memory
 - ❌ libretro core: **Play!**
-  - Low compatibility with most commerical games
+  - Low compatibility with most commercial games
   - Black screen with stuttering sound
 
 ### PlayStation Portable
diff --git a/docs/general/how-ra-works.md b/docs/general/how-ra-works.md
diff --git a/docs/guidelines/content/code-notes.md b/docs/guidelines/content/code-notes.md
diff --git a/docs/guidelines/content/editing-leaderboards.md b/docs/guidelines/content/editing-leaderboards.md
diff --git a/docs/guidelines/content/working-with-the-right-rom.md b/docs/guidelines/content/working-with-the-right-rom.md
diff --git a/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md b/docs/guidelines/users/global-leaderboard-and-achievement-hunting-rules.md
