Update README.md

Fix typos and formatting

README.md

@@ -17,15 +17,15 @@ These examples are from my ME3 testing of the script, but works similarly if not
 **The Script Running**
 ![MELE AutoSave History](https://github.com/jp-powers/MELE-AutoSave-History/blob/master/Example1.png)
 
-The script utilizes a an infinite loop to constantly monitor the autosave file, so the WinForm console window shows certain items, but the write action (the actual copying) will write a history to the parent Powershell window.
+The script utilizes an infinite loop to constantly monitor the autosave file, so the WinForm console window shows certain items, but the write action (the actual copying) will write a history to the parent Powershell window.
 
 ![Example of copied saves](https://github.com/jp-powers/MELE-AutoSave-History/blob/master/Example2.png)
 
 This was a brand new ME3 save, and the Save_0001.pcsav and beyond files were created by the script, the game autosaved 4 times just in the opening before you can even hit Escape to bring up the menu.
 
 ![Example of in game saves showing](https://github.com/jp-powers/MELE-AutoSave-History/blob/master/Example3.png)
 
-This is an example from in-game, showing the saves as available to select and play. Since the script was monitoring during launch I think the numbering got a little goofy because the autosave was happening before you can actually create saves.
+This is an example from in-game, showing the saves as available to select and play. Since the script was monitoring during launch I think the numbering got a little goofy because the autosave was happening before you can actually create saves normally in game.
 
 ## TL;DR how it works
 
@@ -39,16 +39,18 @@ The script will also scan for saves "older" than our set keep count.
 
 First, you'll want to get a save created for your games. If you already have a save you'll be continuing you can skip this. If not, run the game like normal, and get to a place where you can create a save and do so. If you go to "C:\Users\<username>\Documents\BioWare\Mass Effect Legendary Edition\Save" you should see a folder for the game (ME1, ME2, and/or or ME3), and inside that a folder for the "career." If that's there (for the specific new career you're playing) then you're good to go.
 
-Once you have a career folder created you probably want to run the script before launching the game so it's actively monitoring the auto save at all times. It should be generally safe to Alt+Tab out of the game and start it, though.
+Once you have a career folder created you probably want to run the script before launching the game so it's actively monitoring the auto save at all times. It should be generally safe to Alt+Tab out of the game and start it, though. This is how the ME3 testing in the screenshots was done, it looks like an auto save happens on career creation.
 
 Second, due to how Windows works, you need to enable an Unrestricted execution policy so the script can run. While using the script, enable it. If you'd like to ensure you're OS is as secure as Microsoft intended, run the disable command to return it to default.
 
 Open Powershell (Win+R then enter "powershell" or search Powershell in the start menu), and copy/paste the below commands as needed. When running it will ask you to confirm the changes, enter **Y** to do so.
 
-###Enable Powershell execution
+**Enable Powershell execution**
+
 `Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser`
 
-###Disable Powershell execution
+**Disable Powershell execution**
+
 `Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser`
 
 Once completed, right click the AutoSave-History.ps1 file and select **Run with Powershell**.
@@ -57,10 +59,10 @@ A Powershell window will open as well as the WinForms window. This script is pre
 
 There are 5 total interactions.
 
-1. In the first dropdown, select the game you're currently playing. ME1, ME2, or ME3.
+1. In the first dropdown, select the game you're currently playing. ME2 or ME3.
 1. Click **Read Saves** to populate the second dropdown.
 1. In the second dropdown, select the save/"career" you are actively playing. These are based on the folder names that the game creates, so the naming convention is dictated by that.
-1. Set how many auto saves you want to keep a history of. The default is 50. Due to how the game(s) work, in order for the saves to be loadable, we need to use the same naming convention. For the autoremoval to work, I suggest a high value here, so you have a good history of saves without being ridiculous. That said, for ME3, you may want a *really* high value as it autosaves a lot more frequently.
+1. Set how many auto saves you want to keep a history of. The default is 50. Due to how the game(s) work, in order for the saves to be loadable, we need to use the same naming convention. For the autoremoval to work, I suggest a high value here, so you have a good history of saves without being ridiculous. Refer below to the "Notes about the Save Count to Keep feature" section if you'd like to permanent change the default or disable the auto delete all together.
 1. Click **Start Running** and the script will enter an infinite loop to monitor the auto save file and start copying it only if it changes.
 
 Once you are done playing and close the game, Ctrl+C in the Powershell window to cancel the task. Again, due to how simple the script is, the infinite loop it creates means the WinForm window goes into a "Not Responding" state and can't be interacted with or closed, but Ctrl+C in the Powershell window will stop the infinite loop. The script should also catch this action and dispose of the filewatchers so they're not still open when complete.