diff --git a/content/faq/startup-troubleshooting.md b/content/faq/startup-troubleshooting.md
index ad64e29a..60a1764a 100644
--- a/content/faq/startup-troubleshooting.md
+++ b/content/faq/startup-troubleshooting.md
@@ -18,8 +18,8 @@ LBRY operates on a couple different ports and if there are conflicts/firewall ru
 ### This is my first time running LBRY and it won't start
 - Port 3333 already in use. This issue would reveal itself in the log file. You can see how to change this port [here](https://lbry.io/faq/how-to-change-port). If the port is properly forwarding correctly, you are able to successfully see port 3333 Open on this [port checker tool](https://www.canyouseeme.org). 
 - Port 50001 wallet connection fails. This issue would reveal itself in the log file. Typical things to check would be firewall/security settings that may block this connection. 
-- On Linux, LBRY may fail to start because of missing authentication capability. Please see [giuthub issue](https://github.com/lbryio/lbry-app/issues/386) or possible workaround below.
-- On Windows, LBRY may fail to start because of non-ASCII characters in your Windows username. Check your c:\users\<username> path to see if there are any such characters. Please see [github issue](https://github.com/lbryio/lbry/issues/794) or workaround below.
+- On Linux, LBRY may fail to start because of missing authentication capability. Please see [GitHub issue](https://github.com/lbryio/lbry-app/issues/386) or possible workaround below.
+- On Windows, LBRY may fail to start because of non-ASCII characters in your Windows username. Check your c:\users\<username> path to see if there are any such characters. Please see [GitHub issue](https://github.com/lbryio/lbry/issues/794) or workaround below.
 
 ### LBRY used to work previously but now it won't start
 First and foremost, please ensure you are on the [latest verison](https://lbry.io/get) of LBRY. Reinstalling the latest version may alleviate some start-up issues. Before installing, either make sure no LBRY/lbrynet processes or simply reboot your computer.