Fix README formatting

Author: wolveix

README.md

@@ -9,26 +9,20 @@ This is a Dockerized version of the [Satisfactory](https://store.steampowered.co
 
 ## Setup
 
-According to [the official 
-wiki](https://satisfactory.fandom.com/wiki/Dedicated_servers), expect to 
-need 12GB - 16GB of RAM.
+According to [the official wiki](https://satisfactory.fandom.com/wiki/Dedicated_servers), expect to need 12GB - 16GB of RAM.
 
 You'll need to bind a local directory to the Docker container's `/config` directory. This directory will hold the following directories:
 
 -   `/backups` - the server will automatically backup your saves when the container first starts
--   `/gamefiles` - this is for the game's files. They're stored outside of the container to avoid needing to redownload 8GB+ every time you want to rebuild 
-the container
+-   `/gamefiles` - this is for the game's files. They're stored outside of the container to avoid needing to redownload 8GB+ every time you want to rebuild the container
 -   `/saved` - this contains the game's blueprints, saves, and server configuration
 
-Before running the server image, you should find your user ID that will be running the container. This isn't necessary in most cases, but it's good to find 
-out regardless. If you're seeing `permission denied` errors, then this is probably why. Find your ID in `Linux` by running the `id` command. Then grab the 
-user ID (usually something like `1000`) and pass it into the `-e PGID=1000` and `-e PUID=1000` environment variables.
+Before running the server image, you should find your user ID that will be running the container. This isn't necessary in most cases, but it's good to find out regardless. If you're seeing `permission denied` errors, then this is probably why. Find your ID in `Linux` by running the `id` command. Then grab the user ID (usually something like `1000`) and pass it into the `-e PGID=1000` and `-e PUID=1000` environment variables.
 
 Run the Satisfactory server image like this:
 
 ```bash
-docker run -d --name=satisfactory-server -h satisfactory-server -e MAXPLAYERS=4 -e PGID=1000 -e PUID=1000 -e STEAMBETA=false -v /path/to/config:/config -m 16G 
---memory-reservation=12G -p 7777:7777/udp -p 15000:15000/udp -p 15777:15777/udp wolveix/satisfactory-server:latest
+docker run -d --name=satisfactory-server -h satisfactory-server -e MAXPLAYERS=4 -e PGID=1000 -e PUID=1000 -e STEAMBETA=false -v /path/to/config:/config -m 16G --memory-reservation=12G -p 7777:7777/udp -p 15000:15000/udp -p 15777:15777/udp wolveix/satisfactory-server:latest
 ```
 
 ### Docker Compose
@@ -142,8 +136,7 @@ If you want to run a server for the Experimental version of the game, set the `S
 
 ## How to Improve the Multiplayer Experience
 
-The [Satisfactory Wiki](https://satisfactory.fandom.com/wiki/Multiplayer#Engine.ini) recommends a few config tweaks to really get the best out of multiplayer. 
-These changes are already applied to the server, but they need to be applied to your local config too:
+The [Satisfactory Wiki](https://satisfactory.fandom.com/wiki/Multiplayer#Engine.ini) recommends a few config tweaks to really get the best out of multiplayer. These changes are already applied to the server, but they need to be applied to your local config too:
 
 -   Press `WIN + R`
 -   Enter `%localappdata%/FactoryGame/Saved/Config/WindowsNoEditor`
@@ -153,7 +146,5 @@ These changes are already applied to the server, but they need to be applied to
 
 ## Known Issues
 
--   The container is run as `root`. This is pretty common for Docker images, but is bad practice for security reasons. This change was made to address 
-[permissions issues](https://github.com/wolveix/satisfactory-server/issues/44)
--   The server log will show various errors; most of which can be safely ignored. As long as the container continues to run and your log looks similar to the 
-example log, the server should be functioning just fine: [example log](https://github.com/wolveix/satisfactory-server/blob/main/server.log)
+-   The container is run as `root`. This is pretty common for Docker images, but is bad practice for security reasons. This change was made to address [permissions issues](https://github.com/wolveix/satisfactory-server/issues/44)
+-   The server log will show various errors; most of which can be safely ignored. As long as the container continues to run and your log looks similar to the example log, the server should be functioning just fine: [example log](https://github.com/wolveix/satisfactory-server/blob/main/server.log)