diff --git a/game_eggs/tycoon_games/openrct2/README.md b/game_eggs/tycoon_games/openrct2/README.md
index 9137ebf8..1c6d5b57 100644
--- a/game_eggs/tycoon_games/openrct2/README.md
+++ b/game_eggs/tycoon_games/openrct2/README.md
@@ -51,7 +51,7 @@ ___
 |  | Minimum |
 |---------|---------|
 | Processor | Recent x86/64 (AMD/Intel) processor. No ARM support. |
-| RAM | 4096 MiB |
+| RAM | 256-512 MiB (depends on # of clients & park size) |
 | Storage | 80 MB |
 | RCT2 Files | **Not required** |
 
@@ -70,7 +70,7 @@ ___
 Unfortunately, because console commands currently do not register, becoming the first admin on the server takes some steps, listed below:
 1. Ensure the "Log Server Actions" startup variable is set to "true".
 2. Start the server and join it with the client you want to make an admin.
-3. Open `ServerData/serverlogs/<Server Name>/<date>.txt` and copy the SHA1 hash next to your client's username (note the username as well).
+3. Open `ServerData/serverlogs/<Server Name>/<Latest Date>.txt` and copy the SHA1 hash next to your client's username (note the username as well).
 4. Then, open `ServerData/users.json`. Paste the hash into the "hash" value, and change the "name" value to your client's username.
 5. Reboot the server, re-join it, and you should be an admin!
 
@@ -79,10 +79,10 @@ ___
 ### Known Issues
 The following are known issues that are unique to running OpenRCT2 on Pterodactyl, but likely can only be fixed by further development/updates from OpenRCT2.
 - Only building from source from the `develop` branch currently yields a package that is bootable. This will no longer be true for any OpenRCT2 releases after v.0.3.5.1.
-    - This also means that clients joining the server must be on the latest develop branch as well.
+    - This also means that clients joining the server must be on the latest `develop` branch as well.
 - Configuring a password on the server disallows non-admin clients from entering in a password in their client to connect; it just disconnects them. Admin clients can still join normally.
 - You may rarely run into the server crashing on start due to a "Floating point exception(core dumped)" error. If this occurs to you, please help with OpenRCT2 development by doing the following:
 	1. Add the following to the beginning of your server's startup command: `SEGFAULT_SIGNALS=fpe LD_PRELOAD=/lib/x86_64-linux-gnu/libSegFault.so `
-	2. Start the server. If it boots normally, nothing will print. If it crashes, it will print a stack trace to the console.
+	2. Start the server. If it boots normally, nothing extra will print. If it crashes, it will print a stack trace to the console.
 	3. If a crash occurs, copy the entire stack trace, and save it to a log sharing website (like [Hastebin](https://www.hastebin.com)).
 	4. [Open a new Bug Report Issue with OpenRCT2](https://github.com/OpenRCT2/OpenRCT2/issues/new?assignees=&labels=bug&template=bug_report.yaml) and share your logs with them.