From e674a6839a2cb31a965ce64efae5d4065660c19f Mon Sep 17 00:00:00 2001
From: Matt Carvin <90224411+mcarvin8@users.noreply.github.com>
Date: Fri, 17 Jan 2025 12:08:00 -0500
Subject: [PATCH] docs: fix link to debugging section

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 136dc7e..218e19b 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ This plugin is intended for users who deploy their Apex codebase (Apex classes a
 
 This plugin will work if you run local tests or run all tests in an org, including tests that originate from installed managed and unlocked packages. Since files from managed and unlocked packages aren't retrieved into Salesforce DX repositories, these files cannot be included in your code coverage reports.
 
-When the plugin is unable to find the Apex file from the Salesforce CLI coverage report in your repository, it will print a warning and not add that file's coverage data to the coverage report created by this plugin. A warning will be printed for each file not found in a package directory in your repository. See [Debugging](https://github.com/mcarvin8/apex-code-coverage-transformer?tab=readme-ov-file#errors-and-warnings) for more information.
+When the plugin is unable to find the Apex file from the Salesforce CLI coverage report in your repository, it will print a warning and not add that file's coverage data to the coverage report created by this plugin. A warning will be printed for each file not found in a package directory in your repository. See [Debugging](https://github.com/mcarvin8/apex-code-coverage-transformer?tab=readme-ov-file#debugging) for more information.
 
 ## Creating Code Coverage Files with the Salesforce CLI