summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorCarson Gross <carson@bigsky.software>2023-11-18 20:57:16 -0700
committerCarson Gross <carson@bigsky.software>2023-11-18 20:57:16 -0700
commit62ef92cccedbe3c331f49d75203b14c727a49949 (patch)
tree76ea247f2a43f1bf48008b168b84080ba72168ba
parenta573775cb596feb5fbc04aea0aa9fac1103baaf4 (diff)
downloadhtmx-62ef92cccedbe3c331f49d75203b14c727a49949.tar.gz
htmx-62ef92cccedbe3c331f49d75203b14c727a49949.zip
fix typo
-rw-r--r--www/content/essays/why-tend-not-to-use-content-negotiation.md2
1 files changed, 1 insertions, 1 deletions
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