From 6c7963bf70a0e4a588f129c36f78e0b4745dd949 Mon Sep 17 00:00:00 2001
From: nickchomey <88559987+nickchomey@users.noreply.github.com>
Date: Sun, 31 Dec 2023 11:40:40 -0600
Subject: [PATCH] Update why-tend-not-to-use-content-negotiation.md

fixing broken link
---
 www/content/essays/why-tend-not-to-use-content-negotiation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/www/content/essays/why-tend-not-to-use-content-negotiation.md b/www/content/essays/why-tend-not-to-use-content-negotiation.md
index 591d762ee..c06586bbe 100644
--- a/www/content/essays/why-tend-not-to-use-content-negotiation.md
+++ b/www/content/essays/why-tend-not-to-use-content-negotiation.md
@@ -103,7 +103,7 @@ You can see why people like the idea!
 
 So why don't I think this is a good approach to splitting your JSON and HTML APIs up?
 
-It boils down to the [differences between JSON APIs and Hypermedia (HTML) APIs](hypermedia-apis-vs-data-apis.md) I hinted
+It boils down to the [differences between JSON APIs and Hypermedia (HTML) APIs](@/essays/hypermedia-apis-vs-data-apis.md) I hinted
 at earlier.  In particular:
 
 * Data APIs should be versioned and should be very stable within a particular version of the API