Merge branch 'main' of github.com:HTTPArchive/almanac.httparchive.org into production

Author: tunetheweb

src/config/last_updated.json

@@ -614,7 +614,7 @@
   "en/2022/chapters/jamstack.html": {
     "date_published": "2022-10-13T00:00:00.000Z",
     "date_modified": "2022-10-13T00:00:00.000Z",
-    "hash": "82e652ee06d262b2eed711ff3571f83a"
+    "hash": "6525fb0ea59cbcff150ccbc1588b5312"
   },
   "en/2022/chapters/javascript.html": {
     "date_published": "2022-09-26T00:00:00.000Z",

src/content/en/2022/jamstack.md

@@ -45,7 +45,7 @@ That seems like it should be an obvious "yes": if the page is flat HTML that ren
 
 We landed on the "CDN" aspect of the early definition of Jamstack: it doesn't have to be any specific CDN provider, but part of the definition is definitely the "pre-rendering" part, which implies: you're rendering something, and then caching it. So a Jamstack site should be cached (though whether you cache it yourself, or use a CDN, doesn't matter).
 
-That produces another edge-case: lots of sites are cached! Even completely dynamic sites often cache things for a few minutes to avoid load spikes, and lots of sites are served by CDNs these days, which are intrinsically a cache even if the site's architecture owes nothing to Jamstack patterns. So what's the difference between a normal cached site and a Jamstack site? We decided it meant a Jamstack site should be cacheable.
+That produces another edge-case: lots of sites are cached! Even completely dynamic sites often cache things for a few minutes to avoid load spikes, and lots of sites are served by CDNs these days, which are intrinsically a cache even if the site's architecture owes nothing to Jamstack patterns. So what's the difference between a normal cached site and a Jamstack site? Cacheability is one part, but what else?
 
 ### Does a Jamstack site have to use JavaScript?