diff --git a/docs/core/contributing.md b/docs/core/contributing.md
index e8197e6e1241eb7ec2ee614bffda5cd10a9344c3..8bfd9d5a5e43d49205bfe78359c98004ff051773 100644
--- a/docs/core/contributing.md
+++ b/docs/core/contributing.md
@@ -1,6 +1,6 @@
 # How to contribute
 
-This chapter assumes that you have identified a bug or improvement for CiviCRM where the best resolution is to [write and contribute code to core](/docs/core/hacking.md).
+This chapter assumes that you have identified a bug or improvement for CiviCRM where the best resolution is to [write and contribute code to core](/core/hacking.md).
 
 !!! note
 
diff --git a/docs/core/hacking.md b/docs/core/hacking.md
index 66daab84c4d46c3d583bed57a72fe81fce5ef3d9..1f99e17eb5402bb09001f36907f8a35135fc9941 100644
--- a/docs/core/hacking.md
+++ b/docs/core/hacking.md
@@ -10,7 +10,7 @@
 
 To help you decide, here are a couple of principles:
 
-- Bug fixes should always be applied to core.  See [Contributing to Core](/docs/core/contributing.md) for details.
+- Bug fixes should always be applied to core.  See [Contributing to Core](/core/contributing.md) for details.
 - Some (but not all) enhancements to existing features may be best applied to
   core, especially if they would be useful to others.
 - New features should generally be packed as Extensions.