Merge pull request #454 from qooqu/patch-1

tiny typo (I think) in what-is-jamstack.njk.
Well spotted. Thanks @qooqu !

Author: Phil Hawksworth

src/site/what-is-jamstack.njk

@@ -34,7 +34,7 @@ layout: layouts/base.njk
 <section class="mb-12 pb-20 border-gray-400 border-b ">
   <h2>Supercharging with services</h2>
   <p>
-    The thriving <a href="/glossary/api-economy/">API economy</a> has become a significant enabler for Jamstack sites. The ability to leverage domain experts who offer their products and service via APIs has allowed teams to build for more complex applications than if they were to take on the risk and burden of such capabilities themselves. Now we can outsource things like authentication and identity, payments, content management, data services, search, and much more.
+    The thriving <a href="/glossary/api-economy/">API economy</a> has become a significant enabler for Jamstack sites. The ability to leverage domain experts who offer their products and service via APIs has allowed teams to build far more complex applications than if they were to take on the risk and burden of such capabilities themselves. Now we can outsource things like authentication and identity, payments, content management, data services, search, and much more.
     </p>
   <p>
     Jamstack sites might utilise such services at build time, and also at run time directly from the browser via JavaScript. And the clean <a href="/glossary/decoupling/">decoupling</a> of these services allows for greater portability and flexibility, as well as significantly reduced risk.