summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorCarson Gross <carson@bigsky.software>2023-11-18 21:06:25 -0700
committerCarson Gross <carson@bigsky.software>2023-11-18 21:06:25 -0700
commit331f79d4690ebf22667baa0f4a8480949d59f127 (patch)
tree2ad0f639d8bed67d8b5be61d035dfeaa792da60f
parent62ef92cccedbe3c331f49d75203b14c727a49949 (diff)
downloadhtmx-331f79d4690ebf22667baa0f4a8480949d59f127.tar.gz
htmx-331f79d4690ebf22667baa0f4a8480949d59f127.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 576689b7..952ec6cb 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
@@ -23,7 +23,7 @@ The last point often strikes people who are used to a single, general purpose JS
can have a single API that can satisfy any number of types of clients? I tried to answer that question as best I can in the essay
above, but it is certainly a reasonable one to ask.
-It seems like (and it is) extra work in some ways when compared to have that one, general API and the associated logic.
+It seems like (and it is) extra work in some ways when compared to having one general API.
At this point in a conversation, someone who agrees broadly with my take on REST, [Hypermedia-Driven Applications](@/essays/hypermedia-driven-applications.md),
etc. will often jump in and say something like