readme tweaks

Author: MisterZeus

README.md

@@ -13,38 +13,43 @@ This project is in open beta. It is not completely bulletproof, but it has been
 ### Installation:
 * There is a zip file in the releases directory. Download this.
 * Navigate to where GOG stores the steam plugin. 
-  * For windows, this is `%localappdata%\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8`
-  * For MacOS, this is `~/Library/Application Support/GOG.com/Galaxy/plugins/installed/steam_ca27391f-2675-49b1-92c0-896d43afa4f8`
+  * Windows:
+    <br>`%localappdata%\GOG.com\Galaxy\plugins\installed\steam_ca27391f-2675-49b1-92c0-896d43afa4f8`
+  * MacOS:
+    <br>`~/Library/Application Support/GOG.com/Galaxy/plugins/installed/steam_ca27391f-2675-49b1-92c0-896d43afa4f8`
 * If the file does not exist, create it. If it does, delete everything inside it. 
 * Extract the zip release so all the contents are in that file. 
 * Start GOG Galaxy. 
 
 ### Logging: 
-We tried to kill as many bugs and test as many behaviors as possible, but we aren't perfect. You may find some case we haven't tested. Please raise an issue here, and in the comment, attach your logs. They can be found here: 
-* For windows, this is `%programdata%\GOG.com\Galaxy\logs`
-* For MacOS, this is `/Users/Shared/GOG.com/Galaxy/Logs`
+We tried to kill as many bugs and test as many behaviors as possible, but we aren't perfect.
+<br>You may find some case we haven't tested.
+<br>Please raise an issue here, and in the comment, attach your logs.
+<br>They can be found here: 
+* Windows:<br>`%programdata%\GOG.com\Galaxy\logs`
+* MacOS:  <br>`/Users/Shared/GOG.com/Galaxy/Logs`
 
 We typically only need the `steam_<numbers and letters>.log` file.
 
 ## Setup (For Developers)
 * Download [Python 3.7.9 32-bit][Python379]
 * Install it with the defaults
 * Create a new virtual env:
-    - If you only have Python 3.7.9<br/>
+    - If you only have Python 3.7.9<br>
     `python -m venv .venv`
-    - If you have multiple Python versions installed (assumes you have `py` as well)<br/>
+    - If you have multiple Python versions installed (assumes you have `py` as well)<br>
     `py -3.7 -m venv .venv`
 * Activate the virtual env 
-  - Windows, Powershell:<br/>
-  `.\.venv\Scripts\activate.ps1`
-  - MacOS, terminal:<br/>
+  - Windows, Powershell:<br>
+  `.venv\Scripts\activate`
+  - MacOS, terminal:<br>
   `.venv/Scripts/activate`
-* Install the dev dependencies:<br/>
+* Install the dev dependencies:<br>
   `pip install -r requirements/dev.txt`
 * Make your edits
 * Update the protobufs (See README_UPDATE_PROTOBUF_FILES.md for more info)
-  Take notice of the initial diff between the files in `protobuf_files` and `protobuf_files/orig`
-  Generating the python files is done via:
+  <br>Take notice of the initial diff between the files in `protobuf_files` and `protobuf_files/orig`
+  <br>Generating the python files is done via:
   `inv GenerateProtobufMessages`
 * Build your edits:
   `inv build`
@@ -70,48 +75,55 @@ Please do the following:
   <br> If using Windows, make sure you have enabled the setting that `adds Python to the PATH environmental variable`.
   <br> These should be the default settings, but make sure anyway.
 * Create a new virtual env:
-    - If you only have python 3.7.9<br/>
+    - If you only have python 3.7.9<br>
     `python -m venv .venv`
-    - IF you have multiple python versions installed (assumes you have `py` as well)<br/>
+    - IF you have multiple python versions installed (assumes you have `py` as well)<br>
     `py -3.7 -m venv .venv`
 * Activate the virtual env 
-  - Windows, Powershell:<br/>
-  `.\.venv\Scripts\activate.ps1`
-  - MacOS, terminal:<br/>
-  `.venv/Scripts/activate.sh`
-* Use Pip to get the python tools we need to install the plugin. These will only be applied to the venv you created earlier:<br/>
+  - Windows, Powershell:<br>
+  `.venv\Scripts\activate`
+  - MacOS, terminal:<br>
+  `.venv/Scripts/activate`
+* Use Pip to get the python tools we need to install the plugin.
+<br>These will only be applied to the `.venv` virtual environment you created earlier:<br>
   `pip install -r requirements/install.txt`
-* Install the plugin. It should work if you have deleted the original plugin, but will patch it if it is there.<br/>
+* Install the plugin. It should work if you have deleted the original plugin, but will patch it if it is there.<br>
   `inv install`
 
-### Installation (non-dev, Tl;Dr):
+### Installation (non-dev, TL;DR):
 
 <b>Windows (Powershell recommended)</b>
 ```
-echo You must have installed python 3.7.9 (32 bit). If not, the rest of this won't work.
+@echo You must have installed python 3.7.9 (32 bit). If not, the rest of this won't work.
 py.exe -3.7 -m venv .venv
-echo if the previous command did not work, you do not have py installed or py is not in your PATH. If you only have python 3.7.9, run the next command. If it worked, skip the next command.
+@echo If the previous command did not work, you do not have py installed or py is not in your PATH.
+@echo If you only have python 3.7.9, run the next command.
+@echo If it worked, skip the next command.
 python.exe -m venv .venv
-echo virtual environment is installed. on to the next step.
-.\.venv\Scripts\activate.ps1
+@echo virtual environment is installed. on to the next step.
+.venv\Scripts\activate
 pip install -r requirements/install.txt
 inv install
 ```
 
 <b>MacOS</b> (assumes your shell is bash, which is the default. if you are good enough to change that, you can figure out how to run these)
 ```
-echo I have installed python 3.7.9 (MacOS). If not, the rest of this won't work.
+echo You must have installed python 3.7.9 (MacOS). If not, the rest of this won't work.
 py -3.7 -m venv .venv
-echo if the previous command did not work, you do not have py installed or py is not in your PATH. If you only have python 3.7.9, run the next command. If it worked, skip the next command.
+echo If the previous command did not work, you do not have py installed or py is not in your PATH.
+echo If you only have python 3.7.9, run the next command.
+echo If it worked, skip the next command.
 python -m venv .venv
 echo virtual environment is installed. on to the next step.
-./.venv/Scripts/activate.sh
+.venv/Scripts/activate
 pip install -r requirements/install.txt
 inv install
 ```
 
 ### Install Error fixes:
-If `inv install` throws a bunch of errors, make sure you have the proper python venv set up. It should complain about `getargspec`. If this happens, you created the wrong virtual environment. You can either delete .venv and reinstall it, or create a new virtual environment with a different name and use that. make sure you use `py -3.7` when creating your venv. If you don't have py, get it. You can specify the full path to python 3.7 instead if you want, but that's harder to do and harder to explain here. 
+If `inv install` throws a bunch of errors, make sure you have the proper python venv set up. It should complain about `getargspec`. If this happens, you created the wrong virtual environment. You can either delete the `.venv` folder and reinstall it, or create a new virtual environment with a different name and use that.
+
+Make sure you use `py -3.7` when creating your venv. If you don't have `py`, get it. You can specify the full path to python 3.7 instead if you want, but that's harder to do and harder to explain here. 
 
 ## Why this fork?
 
@@ -122,10 +134,10 @@ Well, without being too complicated, Steam changed how they do authentication. W
 ### Current Version:
 This is a fork of https://github.com/FriendsOfGalaxy/galaxy-integration-steam
 
-The new Authorization flow implementation is heavily influenced by SteamKit. https://github.com/SteamRE/SteamKit<br/>
+The new Authorization flow implementation is heavily influenced by SteamKit. https://github.com/SteamRE/SteamKit<br>
 While we have not utilized their source code, they have implemented the new authentication workflow before we did, and we used their knowledge of how to do so in order to implement it ourselves. If you are doing anything steam related in C#, you should check them out; their project has far more features than our own.
 
-Some work was influenced by ValvePython. https://github.com/ValvePython/steam<br/>
+Some work was influenced by ValvePython. https://github.com/ValvePython/steam<br>
 Our projects do the same thing, but use different methods (we use asyncio, they use gevent, for example). Both projects were working on the new Auth Flow simultaneously, with little collaboration between us. That said, their scope is much larger than our own and lets you do a lot more things. If you are looking for a python means of implementing a steam network authentication, you should use their work instead.
 
 ### The names of individual developers will appear here, soon(ish). Any thanks can be directed there