From 8656462920f14be28cf13811f8926d28b1989032 Mon Sep 17 00:00:00 2001 From: NoahAndrews Date: Sat, 16 Dec 2017 14:49:27 -0500 Subject: [PATCH] Fix "visibility" typo --- content/faq/startup-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/faq/startup-troubleshooting.md b/content/faq/startup-troubleshooting.md index 60a1764a..677e6e76 100644 --- a/content/faq/startup-troubleshooting.md +++ b/content/faq/startup-troubleshooting.md @@ -4,7 +4,7 @@ category: troubleshooting order: 1 --- -Proper network connectivity, visbility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer one-on-one [troubleshooting](https://lbry.io/faq/how-to-report-bugs). +Proper network connectivity, visibility, and access is a necessity for usage of LBRY, as it is a peer-to-peer protocol that requires clients to see and speak to each other. Since individual local network configurations, firewalls, and other security settings vary greatly, LBRY may require some basic network/PC troubleshooting in order to function properly. Since LBRY is in beta, there are certain configurations which we don't support yet, but can offer workarounds (see below) or offer one-on-one [troubleshooting](https://lbry.io/faq/how-to-report-bugs). The first area to check for start-up issues is the [LBRY log file](https://lbry.io/faq/how-to-find-lbry-log-file). Except in extreme cases, a log file should be generated by the daemon startup process and will usually reveal clues on where to find problems.