From 5a042292cfed2c2ca6092783599e4c3fbfa01124 Mon Sep 17 00:00:00 2001 From: jptrsn Date: Mon, 28 Oct 2019 09:58:25 -0400 Subject: [PATCH] Corrected link target --- docs/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index c5d2d6c..5048e4e 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -13,7 +13,7 @@ It can be a challenge to troubleshoot problems with tracking a beacon, as the pr ## Build/Upload Occasionally you may encounter errors when trying to build and upload the code for the first time, or after a new version has been released. This is usually caused by a change to the required values provided in your configuration file, which may have changed. -It's a good idea to check out the [release notes](#release-notes) to see if anything has changed that requires action on your part to have the build succeed. +It's a good idea to check out the [release notes](./releaseNotes) to see if anything has changed that requires action on your part to have the build succeed. ## Logging There are various logs that can help identify the step in the information flow that is the broken link in the chain. If you're submitting an issue, be sure to include the logs that show the problematic behaviour