Merge branch 'bigskysoftware:master' into my-dev-branch

Author: fercomunello

www/content/docs.md

@@ -38,6 +38,7 @@ custom_classes = "wide-content"
 * [events & logging](#events)
 * [debugging](#debugging)
 * [scripting](#scripting)
+  * [hx-on attribute](#the-hx-on-attribute)
   * [hyperscript](#hyperscript)
 * [3rd party integration](#3rd-party)
 * [caching](#caching)
@@ -114,7 +115,7 @@ The fastest way to get going with htmx is to load it via a CDN. You can simply a
 and get going:
 
 ```html
-<script src="https://unpkg.com/[email protected]" integrity="sha384-TODO" crossorigin="anonymous"></script>
+<script src="https://unpkg.com/[email protected]" integrity="sha384-QFjmbokDn2DjBjq+fM+8LUIVrAgqcNW2s0PjAxHETgRn9l4fvX31ZxDxvwQnyMOX" crossorigin="anonymous"></script>
 ```
 
 While the CDN approach is extremely simple, you may want to consider [not using CDNs in production](https://blog.wesleyac.com/posts/why-not-javascript-cdn).
@@ -345,10 +346,10 @@ you can create your own CSS transition like so:
 .htmx-indicator{
     display:none;
 }
-.htmx-request .my-indicator{
+.htmx-request .htmx-indicator{
     display:inline;
 }
-.htmx-request.my-indicator{
+.htmx-request.htmx-indicator{
     display:inline;
 }
 ```
@@ -1258,7 +1259,7 @@ Scripting solutions that pair well with htmx include:
   team that created htmx.  It is designed to embed well in HTML and both respond to and create events, and pairs very well
   with htmx.
 
-### <a name="hx-on"></a>[The `hx-on` Attribute](#hyperscript)
+### <a name="hx-on"></a>The `hx-on` Attribute{#the-hx-on-attribute}
 
 HTML allows the embedding of inline scripts via the [`onevent` properties](https://developer.mozilla.org/en-US/docs/Web/Events/Event_handlers#using_onevent_properties),
 such as `onClick`:

www/content/essays/why-tend-not-to-use-content-negotiation.md

@@ -153,7 +153,7 @@ is making a SoC argument.)
 
 ## So What's The Alternative?
 
-The alternative is to, as I advocate in [Splitting Your APIs](@/essays/splitting-your-apis.md), erm, splitting your
+The alternative is, as I advocate in [Splitting Your APIs](@/essays/splitting-your-apis.md), er, well, splitting your
 APIs.  This means providing different paths (or sub-domains, or whatever) for your JSON API and your hypermedia (HTML)
 API.
 

www/content/headers/hx-location.md

@@ -27,3 +27,4 @@ Path is required and is url to load the response from. The rest of the data mirr
 * `swap` - how the response will be swapped in relative to the target
 * `values` - values to submit with the request
 * `headers` - headers to submit with the request
+* `select` - allows you to select the content you want swapped from a response