diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index df9f138b..15db0997 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,4 +1,4 @@
-<!-- 
+<!--
 BEFORE OPENING A PULL REQUEST:
 -> If you're adding multiple independent changes (e.g. adding a section about modding while also fixing a typo on another page) it's generally recommended to split these changes into separate pull requests.
 
diff --git a/docs/Wiki/development/debugging/visualstudio.md b/docs/Wiki/development/debugging/visualstudio.md
index 88115444..7377f191 100644
--- a/docs/Wiki/development/debugging/visualstudio.md
+++ b/docs/Wiki/development/debugging/visualstudio.md
@@ -5,15 +5,15 @@ Northstar is easiest to debug through Visual Studio due to its cmake support.
 
 * If you do not already have Visual Studio download it https://visualstudio.microsoft.com/
   * Its recommended that you install the Community version because it is freely availalbe.
-  * You need to install the `Desktop development with C++` workflow to debug native programs    
+  * You need to install the `Desktop development with C++` workflow to debug native programs
 ![](../../images/debugger-visualstudio-installer-workloads-cpp.png)
 
 * Open Visual Studio
-* Select `Open a project or solution`    
+* Select `Open a project or solution`
 ![](../../images/debugger-visualstudio-launcher.png)
-  * If you already have a solution open you can open a new project through the menu bar    
+  * If you already have a solution open you can open a new project through the menu bar
 ![](../../images/debugger-visualstudio-menu-solution.png)
 * Open `NorthstarLauncher.exe`
-* You can now debug Northstar    
+* You can now debug Northstar
 ![](../../images/debugger-visualstudio-debug-menubar.png)
   * You can find relevant debug symbols in [NorthstarLauncher releases](https://github.com/R2Northstar/NorthstarLauncher/releases)
\ No newline at end of file
diff --git a/docs/Wiki/development/debugging/x64dbg.md b/docs/Wiki/development/debugging/x64dbg.md
index 7506754e..ea28bf10 100644
--- a/docs/Wiki/development/debugging/x64dbg.md
+++ b/docs/Wiki/development/debugging/x64dbg.md
@@ -14,17 +14,17 @@ If you are not experienced with x64dbg it its recommended to use [Visual Studio]
 * Run `x96dbg.exe`
   * You may receive a Windows SmartScreen prompt, x64dbg snapshots are not signed and will always cause these prompts
   * When running for the first time it will ask you some questions. After this is complete rerun the executable.
-* Select `x64dbg` in the Launcher    
+* Select `x64dbg` in the Launcher
 ![](../../images/debugger-x64dbg-launcher.png)
 
 * Do make debugging easier it is suggested to change your settings to the following:
-  * Keeping System Breakpoint enabled is optional but useful    
+  * Keeping System Breakpoint enabled is optional but useful
 ![](../../images/debugger-x64dbg-events.png)
 
-  * Skipping INT3 stepping is recommended to prevent generic breakpoints from stopping the program    
+  * Skipping INT3 stepping is recommended to prevent generic breakpoints from stopping the program
 ![](../../images/debugger-x64dbg-engine.png)
 
-  * Make sure to select the exception before disabling breaking. If you are debugging a C++ Exception you need to ignore common exceptions that occur during runtime    
+  * Make sure to select the exception before disabling breaking. If you are debugging a C++ Exception you need to ignore common exceptions that occur during runtime
 ![](../../images/debugger-x64dbg-exceptions.png)
 
 * Open `NorthstarLauncher.exe` in x64dbg
@@ -38,5 +38,5 @@ Debugging Northstar under Linux is not trivial due to the direct dependency on O
 
 To simplify the use of x64dbg and automate running Origin a community member has created a script: [ns-linux-dbg](https://github.com/R2NorthstarTools/ns-linux-dbg)
 
-To run it simply invoke it: `./nsdbg.py`    
+To run it simply invoke it: `./nsdbg.py`
 It supports a variety of options as well as vanilla wine and Proton, use the help flag to see all possible options: `./nsdbg.py --help`
diff --git a/docs/Wiki/development/releases.md b/docs/Wiki/development/releases.md
index aed3b3db..77de08b9 100644
--- a/docs/Wiki/development/releases.md
+++ b/docs/Wiki/development/releases.md
@@ -136,7 +136,7 @@ Once `2.0` has been released, expectations for `3.0` tend to be lower as the num
 
 ## Other repos
 
-Repos like navmeshes and DiscordRPC get their release unrelated to main Northstar release numbering as they usually only see a few release per year due to 
+Repos like navmeshes and DiscordRPC get their release unrelated to main Northstar release numbering as they usually only see a few release per year due to
 
 
 ### DiscordRPC
diff --git a/docs/Wiki/faq.md b/docs/Wiki/faq.md
index 96506cbe..dd1b11eb 100644
--- a/docs/Wiki/faq.md
+++ b/docs/Wiki/faq.md
@@ -92,7 +92,7 @@ A: This usually lies behind your computer's specs not being high enough in order
 
 ### Q: Why does my game tell me there's an issue with Origin when I don't have Origin? <a href="#ea-replaced-origin" id="faq-ea-replaced-origin"></a>
 
-A: Titanfall2 (and other EA games) used to use a program called [Origin](<https://en.wikipedia.org/wiki/Origin_(service)>) to play games, however this has since been replaced by the EA App. 
+A: Titanfall2 (and other EA games) used to use a program called [Origin](<https://en.wikipedia.org/wiki/Origin_(service)>) to play games, however this has since been replaced by the EA App.
 This change, however, did not update the game's error messages to say "EA App" instead of "Origin", so any time you see that there's an issue with Origin, you can replace mention of "Origin" with the "EA App".
 
 ### Q: When I launch Northstar, a small command prompt appears for a few seconds then closes as nothing else happens!
diff --git a/docs/Wiki/hosting-a-server-with-northstar/basic-listen-server.md b/docs/Wiki/hosting-a-server-with-northstar/basic-listen-server.md
index f6246aa2..2f687b37 100644
--- a/docs/Wiki/hosting-a-server-with-northstar/basic-listen-server.md
+++ b/docs/Wiki/hosting-a-server-with-northstar/basic-listen-server.md
@@ -19,7 +19,7 @@ Whether you're running a listen or dedicated server, you'll generally want to me
 Additionally dedicated server settings and configs can be used on a listen server.\
 Server startup arguments can be placed into `Titanfall2/ns_startup_args.txt`\
 Convars can be placed into `R2Northstar/mods/Northstar.CustomServers/mod/cfg/autoexec_ns_server.cfg`
-The only difference between a listen and dedicated server is that a listen can only run while the host is in the match. 
+The only difference between a listen and dedicated server is that a listen can only run while the host is in the match.
 
 Below are a series of variables and commands you can use for server configuration:
 
diff --git a/docs/Wiki/hosting-a-server-with-northstar/server-settings/playlistvar.md b/docs/Wiki/hosting-a-server-with-northstar/server-settings/playlistvar.md
index 07e600bd..d021e3d2 100644
--- a/docs/Wiki/hosting-a-server-with-northstar/server-settings/playlistvar.md
+++ b/docs/Wiki/hosting-a-server-with-northstar/server-settings/playlistvar.md
@@ -62,7 +62,7 @@ Example: `+setplaylistvaroverrides "run_epilogue 0 featured_mode_amped_tacticals
 | sns_melee_kill_value                               | int             | 5             |                                                                                                |
 | sns_reset_pulse_blade_cooldown_on_pulse_blade_kill | 0-1             | 1             | Enables getting Pulse Blade back after a Pulse Blade kill                                      |
 
-### Gun game playlist overrides 
+### Gun game playlist overrides
 
 | PlaylistOverrides for GG                   | Accepted Values | Default Value | Description                                                                                    |
 | ------------------------------------------ | --------------- | ------------- | ---------------------------------------------------------------------------------------------- |
diff --git a/docs/Wiki/installing-northstar/basic-setup.md b/docs/Wiki/installing-northstar/basic-setup.md
index e5fde1ba..e1af69ba 100644
--- a/docs/Wiki/installing-northstar/basic-setup.md
+++ b/docs/Wiki/installing-northstar/basic-setup.md
@@ -26,7 +26,7 @@ Should you notice any issues/warnings/errors while running Northstar, check the
 
 ## Additional Stuff
 
-You can launch Northstar via Steam, Origin, or EA using [launch options](troubleshooting.md#launch-opts). 
+You can launch Northstar via Steam, Origin, or EA using [launch options](troubleshooting.md#launch-opts).
 
 If Northstar doesn't appear to be installed, or you have issues entering the lobby, try running vanilla files. It's hard to say what VPK mods could cause issues with Northstar at the moment, so it'd probably be easiest just to try running unmodded.
 
diff --git a/docs/Wiki/installing-northstar/northstar-installers/README.md b/docs/Wiki/installing-northstar/northstar-installers/README.md
index 6f9ae430..2b43bd58 100644
--- a/docs/Wiki/installing-northstar/northstar-installers/README.md
+++ b/docs/Wiki/installing-northstar/northstar-installers/README.md
@@ -28,7 +28,7 @@ Note that none of these tools are directly part of the Northstar project and as
 ![FlightCore Mod browser](../../images/flightcore-mod-browser-window.png)
 
 Fast and easy to use Northstar installer, updater, launcher, and mod-manager. Features built-in mod browser and allows for easy installation of pre-release versions of Northstar.\
-Supports Windows and Linux. 
+Supports Windows and Linux.
 
 
 Download and source code:
diff --git a/docs/Wiki/installing-northstar/northstar-installers/flightcore-guide.md b/docs/Wiki/installing-northstar/northstar-installers/flightcore-guide.md
index 57014de3..8853e7fd 100644
--- a/docs/Wiki/installing-northstar/northstar-installers/flightcore-guide.md
+++ b/docs/Wiki/installing-northstar/northstar-installers/flightcore-guide.md
@@ -2,7 +2,7 @@
 
 FlightCore is a Northstar installer and mod manager which allows for installing, updating, and managing mods for the Northstar client made for Titanfall 2.
 
-Something to note is that FlightCore works on both Windows and Linux. The setup process is similar for both, except for the installation folder, and how you install FlightCore. 
+Something to note is that FlightCore works on both Windows and Linux. The setup process is similar for both, except for the installation folder, and how you install FlightCore.
 
 ## Windows Installation
 
@@ -12,7 +12,7 @@ Install the FlightCore file directly from the [Northstar website](https://norths
 
 Then, run the `.msi` file this downloads, and it will automatically install FlightCore for you.
 
-## Linux Installation 
+## Linux Installation
 
 For Linux, you want to download `flight-core_X.Y.Z_amd64.AppImage` (X Y Z being the version numbers of FlightCore) from [FlightCore's GitHub releases page](https://github.com/R2NorthstarTools/FlightCore/releases), put it in a place you prefer, then make sure to right click on it, click on properties, and tick `Executable as Program` (as shown below), then you can just double click it to open FlightCore.
 
@@ -24,7 +24,7 @@ For Linux, you want to download `flight-core_X.Y.Z_amd64.AppImage` (X Y Z being
 
 This is the _Main Menu_ of FlightCore. It includes the _Play_, _Changelog_, _Mods_, and _Settings_ tabs, all of which will be covered in the guide.
 
-## Play 
+## Play
 
 ![Play tab's information](../../images/flightcore-main-window-information.png)
 
@@ -46,7 +46,7 @@ The _Mods_ tab of Flightcore can display either mods installed locally, or a bro
 
 `Online` displays the Mod browser, which sorts by newest uploads by default. Hitting install on a mod will automatically install it, and hitting the *i* next to it will open the mod's information page on ThunderStore in your browser.
 
-## Settings 
+## Settings
 
 ![FlightCore's Settings tab](../../images/flightcore-settings.png)
 
diff --git a/docs/Wiki/installing-northstar/northstar-installers/viper-guide.md b/docs/Wiki/installing-northstar/northstar-installers/viper-guide.md
index ab2ab1dd..d052d77f 100644
--- a/docs/Wiki/installing-northstar/northstar-installers/viper-guide.md
+++ b/docs/Wiki/installing-northstar/northstar-installers/viper-guide.md
@@ -49,7 +49,7 @@ The `Find Mods` button on Viper's mod screen allows you to search through [North
 
 The `Release Notes` tab shows you the release notes for Northstar versions, which you can find [here](https://github.com/R2Northstar/Northstar/releases)
 
-### Viper Menu 
+### Viper Menu
 
 ![Viper's main menu](../../images/viper-menu.png)
 
diff --git a/docs/Wiki/installing-northstar/northstar-installers/vtol-guide.md b/docs/Wiki/installing-northstar/northstar-installers/vtol-guide.md
index 339f56c2..849717d1 100644
--- a/docs/Wiki/installing-northstar/northstar-installers/vtol-guide.md
+++ b/docs/Wiki/installing-northstar/northstar-installers/vtol-guide.md
@@ -4,7 +4,7 @@ VTOL is a mod manager for installing and managing mods for the Northstar client
 
 VTOL works on Windows only and you can find links to download it on [Northstar's website](https://northstar.tf) or [VTOL's GitHub repo](https://github.com/R2NorthstarTools/VTOL).
 Installing it from the website automatically installs the latest version that will automatically update itself.
-On the GitHub repo, you can download the newest version by clicking one of two options. 
+On the GitHub repo, you can download the newest version by clicking one of two options.
 Note that the portable is just a `.exe` file and not the installer, as such it won't automatically update itself.
 
 ![VTOL installer download (on GitHub, automatically updates](../../images/vtol-download-github.png)
@@ -17,7 +17,7 @@ Note that the portable is just a `.exe` file and not the installer, as such it w
 
 **The _Main Menu_ of VTOL is where you'll probably spend most of your time.**
 
-This menu has a lot of useful information, such as the version of VTOL you have, the version of Northstar you have, if the Master Server is online, whether EA App/Origin are currently open, and a place to set your game path. 
+This menu has a lot of useful information, such as the version of VTOL you have, the version of Northstar you have, if the Master Server is online, whether EA App/Origin are currently open, and a place to set your game path.
 
 ## Version Numbers
 
@@ -46,7 +46,7 @@ VTOL handles most things automatically, but it may still require minimal setup f
 
 Something you might have to do manually is locate your Titanfall 2 install. You can do this by pressing the button of the same name on VTOL, and navigating to your Titanfall 2 directory (If you're unsure of what your game path is, check out the [Default Directories](../troubleshooting.md#game-location) section)
 
-After doing this, Northstar should automatically install. If not, the button at the bottom will read _"Install Northstar"_. 
+After doing this, Northstar should automatically install. If not, the button at the bottom will read _"Install Northstar"_.
 Let VTOL install Northstar and you should be good to go. Once installed, this button will turn into the _"Re-Install Northstar"_ button shown in the screenshot earlier, which you can use to forcibly reinstall Northstar in the case something goes wrong with your Northstar install.
 
 ## Launching Northstar via VTOL
@@ -54,7 +54,7 @@ Let VTOL install Northstar and you should be good to go. Once installed, this bu
 ![Launching Northstar](../../images/vtol-launching-northstar.png)
 
 Assuming you've followed everything up to this point, you should be set to hit _"Launch Titanfall 2 Northstar"_ and play on Northstar's servers.
-If you encounter an error like a crash, Northstar will create a log file in the `Titanfall2/R2Northstar/logs` directory. 
+If you encounter an error like a crash, Northstar will create a log file in the `Titanfall2/R2Northstar/logs` directory.
 You can look at this log yourself, or send it on the [Northstar Discord server](https://discord.com/invite/northstar) and someone can try to look at it and help you.
 
 ## Additional Mods/Settings
@@ -84,8 +84,8 @@ You can also right click on a specific mod to get the option to either delete it
 
 ![Mods browser](../../images/vtol-mods-browser.png)
 
-VTOL has a built in-browser for searching [Northstar's Thunderstore page](https://northstar.thunderstore.io/) (the website where most Northstar mods get uploaded to), located at the second tab _"Browse"_ on the tab list. 
-You will see the newest uploaded mods here by default, which you can change by applying filters (Note: The sorting is by default Low-High for filters. 
+VTOL has a built in-browser for searching [Northstar's Thunderstore page](https://northstar.thunderstore.io/) (the website where most Northstar mods get uploaded to), located at the second tab _"Browse"_ on the tab list.
+You will see the newest uploaded mods here by default, which you can change by applying filters (Note: The sorting is by default Low-High for filters.
 You can change this by pressing the button with an arrow next to the filters button, making it High-Low)
 
 VTOL also has support where all you need to do is drag and drop a mod downloaded from the Thunderstore page onto the _"Mods"_ tab (the second tab on the left side) to automatically install the mod.
@@ -121,7 +121,7 @@ For the dedicated server option, you can scroll through this tab to set many dif
 
 ![Tools tab](../../images/vtol-tools.png)
 
-The fifth tab called _"Tools"_ is meant to help those trying to create mods for Northsar. 
+The fifth tab called _"Tools"_ is meant to help those trying to create mods for Northsar.
 
 ### ThunderStore Packer
 
@@ -154,7 +154,7 @@ The fourth screen lists a lot of commonly used tools by modders to help create m
 
 ![VTOL's Profiles menu](../../images/vtol-profiles.png)
 
-The sixth tab is the _"Profiles"_ tab, allowing you to create profiles for Northstar. Profiles are seperate Northstar installs, each with their own set of mods and seperated by folders. 
+The sixth tab is the _"Profiles"_ tab, allowing you to create profiles for Northstar. Profiles are seperate Northstar installs, each with their own set of mods and seperated by folders.
 For example, you can have one profile with your normal set of mods and another profile for only using core mods (those that common with Northstar/the ones that start with `Northstar.`).
 
 ![The Export Profile menu in VTOL](../../images/vtol-export-profile.png)
diff --git a/docs/Wiki/other/helping.md b/docs/Wiki/other/helping.md
index 86a89004..899e5b89 100644
--- a/docs/Wiki/other/helping.md
+++ b/docs/Wiki/other/helping.md
@@ -1,12 +1,12 @@
 # Helping
 
 This section is meant mostly for those that will be actively helping others in the Northstar Discord server or otherwise.
-If you've somehow stumbled upon this page trying to fix an issue for yourself, you should try checking the [troubleshooting page](../installing-northstar/troubleshooting.md) instead. 
+If you've somehow stumbled upon this page trying to fix an issue for yourself, you should try checking the [troubleshooting page](../installing-northstar/troubleshooting.md) instead.
 If you're a helper, it also isn't a bad idea to look at this page a few times and try to have a rough idea of the things that are on it.
 
-When helping a user, please try to move them to the `#help` channel to create a ticket in order to keep public channels less cluttered. 
+When helping a user, please try to move them to the `#help` channel to create a ticket in order to keep public channels less cluttered.
 
-If they really don't want to open a ticket or you don't want to deal with a ticket, ask them to move to `#northstar-chat`. 
+If they really don't want to open a ticket or you don't want to deal with a ticket, ask them to move to `#northstar-chat`.
 There, not only can they embed things, but it'll be slightly more focused on helping than other channels would be.
 
 Arguably the most important things to know as a helper are the ability to read logs and deal with users that don't read the wiki (90% of tickets are solutions solvable by checking the wiki.
@@ -18,12 +18,12 @@ Additionally, please don't be afraid to ask for help. The entirety of `#voluntee
 
 ## Common issues and their tags
 
-In the Northstar Discord server, a massively used device to help end users is the tickets bot. A lot of the common issues and questions that come up have tags for them on the Discord server. 
+In the Northstar Discord server, a massively used device to help end users is the tickets bot. A lot of the common issues and questions that come up have tags for them on the Discord server.
 
 Tags are bits of information that you can easily access by using a slash command.
 We use them mostly for common questions (such as the tag explaining how you can spawn the double barrel shotgun and that you can't spawn it in most servers), and for linking directly to specific pages on the wiki (such as the section about [Intel gen 10+ cpus](https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel)).
 
-The tag command for the tickets bot is `/tag`, and you can either type `/tag id:{TAG ID HERE}` or let the bot autofill the tag for you after typing `/tag` and selecting the tag id from the list (make sure you select the ticket bot, and not Dyno!). 
+The tag command for the tickets bot is `/tag`, and you can either type `/tag id:{TAG ID HERE}` or let the bot autofill the tag for you after typing `/tag` and selecting the tag id from the list (make sure you select the ticket bot, and not Dyno!).
 Note, you can't reply to a user while using a slash command, so try to reply to the bot's message after sending the tag command while pinging the person it's directed at and informing them that they should follow the provided solution.
 
 You can find a list of these tags on the [tag dashboard for the help bot](https://panel.ticketsbot.net/manage/920776187884732556/tags), so long as you sign in using your Discord account and have access to it with the roles that you have.
@@ -38,14 +38,14 @@ When a user clicks on a button to open a ticket they're greeted with the followi
 
 If you or the end user are curious about the difference, a staff ticket can be viewed by anyone with the helper role or above, while a public ticket can be viewed by anyone with the ticket-staff role or above
 
-Once they hit a button to open a ticket, they will fill out the popup with information which will later be shared in their ticket as a message sent as an embed by the ticket bot. 
+Once they hit a button to open a ticket, they will fill out the popup with information which will later be shared in their ticket as a message sent as an embed by the ticket bot.
 This will be the first message in the channel and will look something similar to this:\
 ![The embed sent in a ticket with the information filled out by the user](../images/ticket-open-message.png)
 
 Note the buttons below the embed.\
 Hitting `Close` will close the ticket without a reason for closing it.\
 `Close with reason` will let you give a reason as to why you closed the ticket.\
-`Claim` allows you to "claim" a ticket and lets other helpers know that you'll be solving the ticket. 
+`Claim` allows you to "claim" a ticket and lets other helpers know that you'll be solving the ticket.
 This doesn't usually get used for Northstar, however other helpers can still message in the channel even after it's claimed so don't worry if you accidentally claim a ticket/end up not being able to solve it.
 
 These buttons, however, are not always easy to scroll back up to, especially if the ticket has been open for a while. This is where slash commands come in.
@@ -71,7 +71,7 @@ Using "ac" as described later lets other people know how long until the ticket w
 If the ticket seems resolved/the user has said they have no issues, use `/closerequest` with `close_delay` set to `12` and the `reason` set to "resolved, ac 12hr"
 
 For tickets where the end user that opened the ticket _never_ responded, we usually wait a couple days, ping them a few times, and if they continue to be inactve, set a close request with `close_delay` set to 24 and the `reason` set to "no response, ac 24hr"
-For inactive tickets (when it's the _user_ not responding, not us!) we usually give them a few days and then start pinging them once a day. 
+For inactive tickets (when it's the _user_ not responding, not us!) we usually give them a few days and then start pinging them once a day.
 If they continue to not respond for 2-3 days, we tend to set a close request with `close_delay` set to `48` and the `reason` set to  "inactive ticket, ac 48hr"
 
 You can also use `/closerequest` without giving a `close_delay` or a `reason`, however you should always try to give a reason for closing a ticket, and if you don't give a `close_delay` there's a high chance that the ticket doesn't get closed (quite a few end users don't accept or see the close request)
@@ -79,7 +79,7 @@ You can also use `/closerequest` without giving a `close_delay` or a `reason`, h
 You can view information on the closed tickets, such as open and close date, who opened the ticket, who closed the ticket, and the reason for closing the ticket in the `#transcripts` channel.
 The bot also provides an online log of the entire ticket connected to the embed when a ticket is closed.
 
-## Miscellaneous 
+## Miscellaneous
 
 ### Northstar Servers
 
diff --git a/docs/Wiki/using-northstar/advanced.md b/docs/Wiki/using-northstar/advanced.md
index d904fcdd..4d02ca0b 100644
--- a/docs/Wiki/using-northstar/advanced.md
+++ b/docs/Wiki/using-northstar/advanced.md
@@ -13,7 +13,7 @@ Currently, the only mod managers supporting profiles are [VTOL](https://github.c
 
 The first thing you want to do while creating a new profile is to have a Northstar release version downloaded and ready to be used. You will only need the `R2Northstar` folder from this second version, as the rest of the `NorthstarRelease.vX.Y.Z.zip` doesn't matter to creating additional profiles.
 
-You'll want to rename the `R2Northstar` folder to whatever you prefer it to be called, such as `R2NorthstarNoMods` if you'd like to have a normal Northstar installation without using additional mods. These profiles act entirely independently from the other folders, meaning you can use a mod in a folder without it affecting any others. The only downside to this, however, is that they must all be updated independently when a Northstar update is released. You can install any mods that you would like to `YourProfileName/mods`, and they will load when launching it, though, just like core mods, additional mods will all also need to be updated independently. 
+You'll want to rename the `R2Northstar` folder to whatever you prefer it to be called, such as `R2NorthstarNoMods` if you'd like to have a normal Northstar installation without using additional mods. These profiles act entirely independently from the other folders, meaning you can use a mod in a folder without it affecting any others. The only downside to this, however, is that they must all be updated independently when a Northstar update is released. You can install any mods that you would like to `YourProfileName/mods`, and they will load when launching it, though, just like core mods, additional mods will all also need to be updated independently.
 
 In order to create the `.bat` to launch this profile, you'll need to first create a `.txt` file inside of your Titanfall2 directory, and name it whatever you would like. Inside of this `.txt` file, you'll want to put in `NorthstarLauncher.exe -profile=PROFILE FOLDER NAME HERE`, replacing all of `PROFILE FOLDER NAME HERE` with the name that you gave the folder you installed your mods to. After this, rename the file to `yourFileName.bat`. Double clicking or right clicking on the `.bat` file then hitting `open` will launch Northstar with the assigned profile.
 
@@ -27,7 +27,7 @@ You can set up profiles in an even more advanced way by setting up a way to use
 This section can cause you to mess up your persistence (multiplayer user data) on Northstar if you set your levels too high! Make sure to read carefully!
 {% endhint %}
 
-With everything unlocked, there is no need to set your level to a higher level, but some users may still want to do so. In order to this, you'll need to open the in-game console with the `~` button on your keyboard and type in/copy and paste the relevant commands. Both of these require `sv_cheats 1` to be enabled on the server you're playing on, easily done by using `sv_cheats 1` in the console in a private match. 
+With everything unlocked, there is no need to set your level to a higher level, but some users may still want to do so. In order to this, you'll need to open the in-game console with the `~` button on your keyboard and type in/copy and paste the relevant commands. Both of these require `sv_cheats 1` to be enabled on the server you're playing on, easily done by using `sv_cheats 1` in the console in a private match.
 
 `script GetPlayerArray()[0].SetPersistentVar("gen", INSERT_GEN_COUNT)` this command sets the Generation level of the player. You want to replace `INSERT_GEN_COUNT` with the number you want. Setting this number too high should work for leveling up, however it will display `g103` on your kill card.