Apply suggestions from code review

Co-authored-by: Rem <[email protected]>

Author: Princess-Cheeseballs

src/en/wizden-staff/maintainer.md

@@ -1,31 +1,31 @@
 # Maintainer
 
-This section contains information on Maintainer and PR-Review Policies, **as it pertains to Wizards Den servers, hosted by Space Wizards.** These policies do not apply to other servers, and may be waived in exceptional circumstances.
+This section contains information on Maintainer and PR-Review Policies, **as it pertains to Wizards Den servers, hosted by Space Wizards.** These policies do not apply to other servers and may be waived in exceptional circumstances.
 
 ## Maintainer
 
-A maintainer is a member of staff who is given authority and trust in reviewing and merging PRs. All maintainers regardless of specialization are expected to follow Maintainer Policy.
+A maintainer is a member of staff who is given authority and trust to review and merge PRs. All maintainers, regardless of specialization, are expected to follow the Maintainer Policy.
 
 ### SS14 Maintainer
 
-A SS14 Maintainer maintains the content side of Space Station 14. This includes the docs repo, and content repo. 
+A SS14 Maintainer maintains the content side of Space Station 14. This includes the docs repo and the content repo. 
 
 ### Documaintainer
 
-A Documaintainer is a 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 Repo. Within the docs repo, they have the same power and authority as an SS14 maintainer.
 
 ### Head Mapper
 
-A Head Mapper is a SS14 Maintainer who has exclusive power over content PRs with map changes and additions. These maintainers are expected to ensure mapping standards and their approval is required for any PRs which 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 a 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 which 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 a 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
+### 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/hotfix-procedure.md

@@ -4,7 +4,7 @@ Not following this procedure/policy will result in disciplinary action being tak
 ## Requirements
 - **Three Maintainers must *sign-off*** (Approval is required, reviewing is recommended but optional) on a hotfix PR for it to be merged.
 - The Hotfix procedure only applies to PRs being merged straight to "stable" or "staging". **When merging bugfixes to master, this procedure does NOT apply, use the normal PR procedure instead!**
-- All Hotfixes must adhere to the normal [PR Review Procedure](../maintainer/content-review-procedure.md) in addition to any requirements listed here.
+- All Hotfixes must adhere to the normal [PR review procedure](../maintainer/content-review-procedure.md) in addition to any requirements listed here.
 - Hotfixes must be given the "Hotfix" label during triage. They will also automatically receive a label indicating their branch.
 - Stable Hotfixes are for fixing bugs only, not for adding new content or minor balance adjustments. *If a balance issue is bad enough to majorly impact game quality, it should be considered a bug and is eligible for a hotfix. This is up to Maintainer judgment, but if you are unsure, it's recommended to create a discussion thread prefixed with "HOTFIX-PRNumber".
 - Hotfixes to Staging may include any changes that are deemed necessary for the upcoming release, but are otherwise still referred to as Hotfixes and follow these procedures.