From 62ef92cccedbe3c331f49d75203b14c727a49949 Mon Sep 17 00:00:00 2001 From: Carson Gross Date: Sat, 18 Nov 2023 20:57:16 -0700 Subject: [PATCH] fix typo --- 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 6b222ea4..576689b7 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 @@ -30,7 +30,7 @@ etc. will often jump in and say something like > "Oh, it's easy, you just use _content negotiation_, it's baked into HTTP!" -Not being content with alienating only the general purpose JSON API enthusiasts, let me know proceed to also alienate +Not being content with alienating only the general purpose JSON API enthusiasts, let me now proceed to also alienate my erstwhile hypermedia enthusiast allies by saying: *I don't think content negotiation is typically the right approach to