From 1995b752c0a03cd808b5eb3a378f4ea9ef92f309 Mon Sep 17 00:00:00 2001
From: Jesper Mayntzhusen <36075913+jmayntzhusen@users.noreply.github.com>
Date: Thu, 27 Aug 2020 14:55:57 +0200
Subject: [PATCH] Fix broken link

---
 docs/programs/run-a-good-program.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/programs/run-a-good-program.md b/docs/programs/run-a-good-program.md
index 46383278b32..46f0f94c398 100644
--- a/docs/programs/run-a-good-program.md
+++ b/docs/programs/run-a-good-program.md
@@ -16,7 +16,7 @@ Programs that engage in [disclosure](disclosure.html) find themselves having hig
 It’s best practice to actively [communicate with your hackers](communicating-with-hackers.html) by commenting on reports and answering any questions or concerns they have in a timely manner and letting them know of any updates or changes to your program by using the [message hackers](programs/message-hackers.html) feature.
 
 ### Tip #4: Utilize Bounty Tables
-Set up [bounty tables](programs/bounty-tables.html) as they help hackers to see how much is rewarded based on the severity level of the vulnerability.  Additionally, it’s important that you set your bounties to fair amounts that don’t underpay hackers.  
+Set up [bounty tables](bounty-tables.html) as they help hackers to see how much is rewarded based on the severity level of the vulnerability.  Additionally, it’s important that you set your bounties to fair amounts that don’t underpay hackers.  
 
 ### Tip #5: Keep your policy up-to-date
 Make sure all helpful and important information is written on your [policy](policy-and-scope.html) and that you follow the [best practices for good policies](programs/good-policies.html).