Apply suggestions from code review

Co-authored-by: Rem <Remfexxel@pm.me>

Author: Princess-Cheeseballs

src/en/general-development/codebase-info/releases.md

@@ -8,7 +8,7 @@ What does this mean for you? If you're a fork developer, this means that you now
 Updates are deployed every 14 days over the course of a weekend (Usually on a Saturday). 2 days prior to update day, "master" will be branched into "staging" and maintainers will perform a review of the upcoming changes. During this period, changes may be made or PRs may be reverted on the staging branch. Release day also coincides with the day of the regular maintainer meeting, half of which will be devoted to looking over the changes prepared for release. The outcome of this meeting determines if the update will be deployed as is, receive changes, or be delayed. The following 2 days after an update is deployed will allow for balance/minor gameplay fixes to be deployed under the normal Hotfix procedure.
 
 ### Review/PR Procedure
-All PRs must be reviewed according to the PR review procedure [documented here](../../wizden-staff/maintainer/content-review-procedure.md), and may be merged to the development branch "master" at any point. PR's fixing code bugs or critical gameplay issues *may* be merged directly onto the "stable" branch but in that case must additionally follow the Hotfix procedure [documented here](../../wizden-staff/maintainer/hotfix-procedure.md).
+All PRs must be reviewed according to the PR review procedure [documented here](../../wizden-staff/maintainer/content-review-procedure.md), and may be merged to the development branch "master" at any point. PR's fixing code bugs or critical gameplay issues *may* be merged directly onto the "stable" branch, but in that case must additionally follow the Hotfix procedure [documented here](../../wizden-staff/maintainer/hotfix-procedure.md).
 
 ### What is Hotfixable?
 Any issue that directly impacts a player's ability to play the game in a largely negative way and can be considered by most to be a "bug" is eligable to be merged as a Hotfix. Critical gameplay issues may also fall into this category as well. "Critical" being an issue that is majorly disruptive to players **or admins**. *Outside of an emergency*, all **Hotfixes require 3 maintainers to sign-off** on merging (Ideally they should also review but giving approval is enough). Bugfixes may be applied to master following the regular review requirements.

src/en/wizden-staff/maintainer.md

@@ -8,24 +8,24 @@ A maintainer is a member of staff who is given authority and trust to review and
 
 ### SS14 Maintainer
 
-A SS14 Maintainer maintains the content side of Space Station 14. This includes the docs repo and the content repo. 
+An SS14 maintainer maintains the content side of Space Station 14. This includes the docs repo and the content repo. 
 
 ### Documaintainer
 
-A Documaintainer is an SS14 maintainer who only has maintainer powers for the Docs Repo. Within the docs repo, they have the same power and authority as an SS14 maintainer.
+A documaintainer is an SS14 maintainer who only has maintainer powers for the docs repository. Within the docs repository, they have the same power and authority as an SS14 maintainer.
 
 ### Head Mapper
 
-A Head Mapper is an SS14 Maintainer who has exclusive power over content PRs with map changes and additions. These maintainers are expected to ensure mapping standards are met, and their approval is required for any PRs that make mapping changes.
+A head mapper is an SS14 Maintainer who has exclusive power over content PRs with map changes and additions. These maintainers are expected to ensure mapping standards are met, and their approval is required for any PRs that make mapping changes.
 
 ### Art Lead
 
-An Art Lead is an SS14 Maintainer who has exclusive power over content PRs with sprite changes and additions. These maintainers are expected to ensure the game maintains its art style, and their approval is required for any PRs that make significant changes to existing sprites or add new sprites.
+An art lead is an SS14 maintainer who has exclusive power over content PRs with sprite changes and additions. These maintainers are expected to ensure the game maintains its art style, and their approval is required for any PRs that make significant changes to existing sprites or add new sprites.
 
 ### UI Lead
 
-A UI Lead is an SS14 Maintainer who has exclusive power over content PRs with UI changes and additions. These maintainers are expected to ensure the game retains usable, aesthetically pleasing UIs which fit the game's art style. 
+A UI lead is an SS14 maintainer who has exclusive power over content PRs with UI changes and additions. These maintainers are expected to ensure the game retains usable, aesthetically pleasing UIs which fit the game's art style. 
 
 ### Robust Toolbox Maintainer
 
-A Robust Toolbox maintainer is a maintainer for the game's engine, Robust Toolbox. These are the only Maintainers who have merge powers for the engine. 
+A Robust Toolbox maintainer is a maintainer for the game's engine, Robust Toolbox. These are the only maintainers who have merge powers for the engine. 

src/en/wizden-staff/maintainer/maintainer-policy.md

@@ -5,7 +5,7 @@ This policy applies in addition to the [General Staff](../staff-policy.md) and [
 
 **Breaking any of these rules will result in disiplinary action being taken**
 ## Reviews and Feedback
-- All maintainers must follow the [PR Review](../maintainer/content-review-procedure.md) and [Hotfix Procedures](../maintainer/hotfix-procedure.md) when they apply.
+- All maintainers must follow the [PR review](../maintainer/content-review-procedure.md) and [hotfix procedures](../maintainer/hotfix-procedure.md) when they apply.
 - Maintainers should try to the best of their ability, to keep PR authors informed on the status of their PRs.
 - Maintainers should keep public criticism of code *constructive* and avoid making comments in regards to the authors of the code. **Harsh but fair** citicism of code is *acceptable*, but criticism of its author is not.
 - Maintainers should try to perform code reviews *whenever possible*, getting content into the game is everyone's responsibility.