diff options
author | Viktor Szépe <viktor@szepe.net> | 2023-07-17 16:26:27 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-07-17 10:26:27 -0400 |
commit | 0a471dc4fbd26e8e820415b9033cab40d0193712 (patch) | |
tree | d85844708914c54525e78430ceccf0900fd0be79 | |
parent | e33b0be9090000661e47574b2663c54ad9e94d7c (diff) | |
download | htmx-0a471dc4fbd26e8e820415b9033cab40d0193712.tar.gz htmx-0a471dc4fbd26e8e820415b9033cab40d0193712.zip |
Fix typos in www/ (#1579)
23 files changed, 30 insertions, 30 deletions
diff --git a/www/content/api.md b/www/content/api.md index 331cc430..34e88603 100644 --- a/www/content/api.md +++ b/www/content/api.md @@ -67,7 +67,7 @@ or // issue a GET to /example and put the response HTML into #myDiv htmx.ajax('GET', '/example', '#myDiv') - // issue a GET to /example and replace #myDiv with the repsonse + // issue a GET to /example and replace #myDiv with the response htmx.ajax('GET', '/example', {target:'#myDiv', swap:'outerHTML'}) // execute some code after the content has been inserted into the DOM diff --git a/www/content/attributes/hx-indicator.md b/www/content/attributes/hx-indicator.md index e811ad78..42b180e5 100644 --- a/www/content/attributes/hx-indicator.md +++ b/www/content/attributes/hx-indicator.md @@ -57,7 +57,7 @@ Note that the target of the `hx-indicator` selector need not be the exact elemen want to show: it can be any element in the parent hierarchy of the indicator. Finally, note that the `htmx-request` class by default is added to the element causing -the request, so you can place an indicator inside of that element and not need to explictly +the request, so you can place an indicator inside of that element and not need to explicitly call it out with the `hx-indicator` attribute: ```html diff --git a/www/content/docs.md b/www/content/docs.md index 6f562d60..230e56eb 100644 --- a/www/content/docs.md +++ b/www/content/docs.md @@ -554,7 +554,7 @@ content of the page is examined for elements that match by the `id` attribute. is found for an element in the new content, the attributes of the old content are copied onto the new element before the swap occurs. The new content is then swapped in, but with the *old* attribute values. Finally, the new attribute values are swapped in, after a "settle" delay -(20ms by default). A little crazy, but this is what allowes CSS transitions to work without any javascript by +(20ms by default). A little crazy, but this is what allows CSS transitions to work without any javascript by the developer. ### Out of Band Swaps {#oob_swaps} @@ -603,7 +603,7 @@ with a CSS selector of all the elements whose values you want to include in the If you wish to filter out some parameters you can use the [hx-params](@/attributes/hx-params.md) attribute. -Finally, if you want to programatically modify the parameters, you can use the [htmx:configRequest](@/events.md#htmx:configRequest) +Finally, if you want to programmatically modify the parameters, you can use the [htmx:configRequest](@/events.md#htmx:configRequest) event. #### File Upload {#files} @@ -1107,7 +1107,7 @@ htmx.logger = function(elt, event, data) { ## Debugging -Declarative and event driven programming with htmx (or any other declartive language) can be a wonderful and highly productive +Declarative and event driven programming with htmx (or any other declarative language) can be a wonderful and highly productive activity, but one disadvantage when compared with imperative approaches is that it can be trickier to debug. Figuring out why something *isn't* happening, for example, can be difficult if you don't know the tricks. @@ -1130,7 +1130,7 @@ browser console: monitorEvents(htmx.find("#theElement")); ``` -This will spit out all events that are occuring on the element with the id `theElement` to the console, and allow you +This will spit out all events that are occurring on the element with the id `theElement` to the console, and allow you to see exactly what is going on with it. Note that this *only* works from the console, you cannot embed it in a script tag on your page. @@ -1321,7 +1321,7 @@ In hyperscript you can implement this, as well as fade effect, like so: ##### `ic-post-errors-to` Intercooler provided the [`ic-post-errors-to`](http://intercoolerjs.org/attributes/ic-post-errors-to.html) attribute -for posting errors that occured during requests and responses. +for posting errors that occurred during requests and responses. In hyperscript similar functionality is implemented like so: @@ -1489,7 +1489,7 @@ while still providing additional safety if your HTML-escaping discipline fails. ## Configuring htmx {#config} -Htmx has some configuration options that can be accessed either programatically or declaratively. They are +Htmx has some configuration options that can be accessed either programmatically or declaratively. They are listed below: <div class="info-table"> diff --git a/www/content/essays/10-tips-for-SSR-HDA-apps.md b/www/content/essays/10-tips-for-SSR-HDA-apps.md index 5ff28493..63ca7508 100644 --- a/www/content/essays/10-tips-for-SSR-HDA-apps.md +++ b/www/content/essays/10-tips-for-SSR-HDA-apps.md @@ -11,7 +11,7 @@ Building web applications using traditional Server-Side Rendering (SSR) or, sayi compared with building web applications with Single Page Application frameworks like React. If you come at this style of development with an SPA-engineering hat on, you are likely to be frustrated and miss out -on many advantages of this particular architectual choice. +on many advantages of this particular architectural choice. Here are 10 tip to help you make the mental shift smoothly, taking advantage of the strengths of this approach and minimizing the weaknesses of it: diff --git a/www/content/essays/a-response-to-rich-harris.md b/www/content/essays/a-response-to-rich-harris.md index 264b1690..cdc0a349 100644 --- a/www/content/essays/a-response-to-rich-harris.md +++ b/www/content/essays/a-response-to-rich-harris.md @@ -69,7 +69,7 @@ That said, [infinite scroll](@/examples/infinite-scroll.md) can be achieved quit Nice transitions are, well, nice. We think that designers tend to over-estimate their contribution to application usability, however. Yes, the demo sizzles, but on the 20th click users often just want the UI to get on with it. -That being said, htmx supports using [standard CSS transtions](@/examples/animations.md) to make animations possible. Obviously there is a limit to what you can achieve with these pure CSS techniques, but we believe this can give you the 80 of an 80/20 situation. (Or, perhaps, the 95 of a 95/5 situation.) +That being said, htmx supports using [standard CSS transitions](@/examples/animations.md) to make animations possible. Obviously there is a limit to what you can achieve with these pure CSS techniques, but we believe this can give you the 80 of an 80/20 situation. (Or, perhaps, the 95 of a 95/5 situation.) ### "Multipage Apps Load Javascript Libraries Every Request" diff --git a/www/content/essays/complexity-budget.md b/www/content/essays/complexity-budget.md index 5083dc9c..1065c012 100644 --- a/www/content/essays/complexity-budget.md +++ b/www/content/essays/complexity-budget.md @@ -36,7 +36,7 @@ is one major reason why many good developers are so much more productive than ot However, this doesn't change the fact that, somewhere out there, there is a Complexity Wall lurking and, if you aren't careful you will run into it and grind development to a halt. I have had multiple experiences with this: one day, -inexplicably, development on a system that I was working on went from feeling "large, but managable" to +inexplicably, development on a system that I was working on went from feeling "large, but manageable" to "this is impossible to deal with". ## Spending Your Complexity Budget Wisely diff --git a/www/content/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md b/www/content/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md index a9c2f92c..021e4148 100644 --- a/www/content/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md +++ b/www/content/essays/how-did-rest-come-to-mean-the-opposite-of-rest.md @@ -336,7 +336,7 @@ The back end engineers were still concerned with the network architecture to an term "REST" to describe what they were doing. Even though they were doing things like publishing swagger documentation for their RESTful APIs or [complaining about API -churn of their RESTful APIs](https://www.infoq.com/articles/no-more-mvc-frameworks/), things that wouldn't be occuring +churn of their RESTful APIs](https://www.infoq.com/articles/no-more-mvc-frameworks/), things that wouldn't be occurring if they were actually creating RESTful APIs. Finally, in the late 2010s, people had had enough: REST, even in its RESTless form, simply wasn't keep up with the needs diff --git a/www/content/essays/rest-explained.md b/www/content/essays/rest-explained.md index e7f38735..30dc9669 100644 --- a/www/content/essays/rest-explained.md +++ b/www/content/essays/rest-explained.md @@ -38,7 +38,7 @@ REST is, of course, a client-server architecture, since the web is a client (bro ### [Stateless](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_3) The web, most developers know, is intended to be stateless. All requests should encapsulate all information necessary -to understand that request. For example, there should not be a long running transaction implicity associated with a series +to understand that request. For example, there should not be a long running transaction implicitly associated with a series of requests, as you might have with a SQL database session. ### [Cache](https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_4) diff --git a/www/content/essays/splitting-your-apis.md b/www/content/essays/splitting-your-apis.md index 611d3e03..56d0a13e 100644 --- a/www/content/essays/splitting-your-apis.md +++ b/www/content/essays/splitting-your-apis.md @@ -43,7 +43,7 @@ And these as application API needs: </div> -I will term this mis-alignment of needs the **Data/App API Impedance Mismatch** problem. +I will term this misalignment of needs the **Data/App API Impedance Mismatch** problem. Max's recommendation is to split the API into two "halves": a generic API and an application API: diff --git a/www/content/examples/sortable.md b/www/content/examples/sortable.md index 24b89f7d..7380ccc0 100644 --- a/www/content/examples/sortable.md +++ b/www/content/examples/sortable.md @@ -6,7 +6,7 @@ template = "demo.html" In this example we show how to integrate the [Sortable](https://sortablejs.github.io/Sortable/) javascript library with htmx. -To begin we intialize the `.sortable` class with the `Sortable` javascript library: +To begin we initialize the `.sortable` class with the `Sortable` javascript library: ```js htmx.onLoad(function(content) { diff --git a/www/content/extensions/_index.md b/www/content/extensions/_index.md index 5b8f9dc7..a738e9b5 100644 --- a/www/content/extensions/_index.md +++ b/www/content/extensions/_index.md @@ -71,7 +71,7 @@ See the individual extension documentation for more details. | [`head-support`](@/extensions/head-support.md) | support for merging the `head` tag from responses into the existing documents `head` | [`include-vals`](@/extensions/include-vals.md) | allows you to include additional values in a request | [`json-enc`](@/extensions/json-enc.md) | use JSON encoding in the body of requests, rather than the default `x-www-form-urlencoded` -| [`idiomorph`](https://github.com/bigskysoftware/idiomorph) | an extension for using the idiomorph morphing algorightm as a swapping mechanism +| [`idiomorph`](https://github.com/bigskysoftware/idiomorph) | an extension for using the idiomorph morphing algorithm as a swapping mechanism | [`loading-states`](@/extensions/loading-states.md) | allows you to disable inputs, add and remove CSS classes to any element while a request is in-flight. | [`method-override`](@/extensions/method-override.md) | use the `X-HTTP-Method-Override` header for non-`GET` and `POST` requests | [`morphdom-swap`](@/extensions/morphdom-swap.md) | an extension for using the [morphdom](https://github.com/patrick-steele-idem/morphdom) library as the swapping mechanism in htmx. diff --git a/www/content/extensions/include-vals.md b/www/content/extensions/include-vals.md index 6e5b388e..76b0bb99 100644 --- a/www/content/extensions/include-vals.md +++ b/www/content/extensions/include-vals.md @@ -2,7 +2,7 @@ title = "include-vals" +++ -The `include-vals` extension allows you to programatically include values in a request with +The `include-vals` extension allows you to programmatically include values in a request with a `include-vals` attribute. The value of this attribute is one or more name/value pairs, which will be evaluated as the fields in a javascript object literal. diff --git a/www/content/extensions/preload.md b/www/content/extensions/preload.md index 7ce8cd90..9a9b9add 100644 --- a/www/content/extensions/preload.md +++ b/www/content/extensions/preload.md @@ -58,7 +58,7 @@ Defaults for this extension are chosen to balance users' perceived performance w #### preload="mousedown" (DEFAULT) -The default behavior for this extension is to begin loading a resource when the user presses the mouse down. This is a conservative setting that guarantees the user actually intends to use the linked resource. Because user click events typcially take 100-200ms to complete, this setting gives your server a significant headstart compared with a regular click. +The default behavior for this extension is to begin loading a resource when the user presses the mouse down. This is a conservative setting that guarantees the user actually intends to use the linked resource. Because user click events typically take 100-200ms to complete, this setting gives your server a significant headstart compared with a regular click. ```html <a href="/server/1" preload="mousedown">This will be preloaded when the user begins to click.</a> @@ -90,7 +90,7 @@ Preload can also listen to any custom event within the system, triggering resour ### About Touch Events -To accomodate touchscreen devices, an additional `ontouchstart` event handler is added whenever you specify a `mouseover` or `mousedown` trigger. This extra trigger fires immediately (no waiting period) whenever the user touches the screen, saving you 300ms of waiting time on Android, and 450ms on iOS. +To accommodate touchscreen devices, an additional `ontouchstart` event handler is added whenever you specify a `mouseover` or `mousedown` trigger. This extra trigger fires immediately (no waiting period) whenever the user touches the screen, saving you 300ms of waiting time on Android, and 450ms on iOS. ### Limitations diff --git a/www/content/migration-guide-hotwire-turbo.md b/www/content/migration-guide-hotwire-turbo.md index 566173ec..8956223a 100644 --- a/www/content/migration-guide-hotwire-turbo.md +++ b/www/content/migration-guide-hotwire-turbo.md @@ -47,4 +47,4 @@ document.body.addEventListener('htmx:configRequest', (event) => { ## Stimulus -* [hyperscript](https://hyperscript.org) is a close analogue and an official companion project to htmx, but the two projects are entirely seperated and can be used exclusively from each other or any other library. +* [hyperscript](https://hyperscript.org) is a close analogue and an official companion project to htmx, but the two projects are entirely separated and can be used exclusively from each other or any other library. diff --git a/www/content/migration-guide.md b/www/content/migration-guide.md index 35fabc26..61d99e23 100644 --- a/www/content/migration-guide.md +++ b/www/content/migration-guide.md @@ -48,7 +48,7 @@ See the [htmx documentation on hyperscript](@/docs.md#hyperscript) for practical | [`ic-action`](https://intercoolerjs.org/attributes/ic-action.html) | None. Use [Hyperscript][], e.g. `<button _="on click add .clicked">Add The "clicked" Class To Me</button>`. See the [htmx documentation on hyperscript](@/docs.md#hyperscript) and [hyperscript documentation](https://hyperscript.org)for more examples | [`ic-action-target`](https://intercoolerjs.org/attributes/ic-action-target.html) | None. Use the [Hyperscript target expression](https://hyperscript.org/expressions/target/), e.g. `<div _="on click set .button.style.color to 'red'">Set All Buttons To Red</div>` | [`ic-add-class`](https://intercoolerjs.org/attributes/ic-add-class.html) | None. Use [Hyperscript][], e.g. `<button _="on click add .clicked">Add The "clicked" Class To Me</button>`. See the [htmx documentation on hyperscript](@/docs.md#hyperscript) and [hyperscript documentation](https://hyperscript.org) for more examples -| [`ic-append-from`](https://intercoolerjs.org/attributes/ic-append-from.html) | None. Equivalent functionality can be achived by using for example [`hx-get`](@/attributes/hx-get.md) and [`hx-swap`](@/attributes/hx-swap.md) with value `beforeend` +| [`ic-append-from`](https://intercoolerjs.org/attributes/ic-append-from.html) | None. Equivalent functionality can be achieved by using for example [`hx-get`](@/attributes/hx-get.md) and [`hx-swap`](@/attributes/hx-swap.md) with value `beforeend` | [`ic-attr-src`](https://intercoolerjs.org/attributes/ic-attr-src.html) | None. No direct equivalent functionality exists (TBC) | [`ic-confirm`](https://intercoolerjs.org/attributes/ic-confirm.html) | [`hx-confirm`](@/attributes/hx-confirm.md) | [`ic-delete-from`](https://intercoolerjs.org/attributes/ic-delete-from.html) | [`hx-delete`](@/attributes/hx-delete.md) diff --git a/www/content/posts/2020-11-24-htmx-1.0.0-is-released.md b/www/content/posts/2020-11-24-htmx-1.0.0-is-released.md index 92a41d0f..e0098352 100644 --- a/www/content/posts/2020-11-24-htmx-1.0.0-is-released.md +++ b/www/content/posts/2020-11-24-htmx-1.0.0-is-released.md @@ -29,7 +29,7 @@ HTML-oriented web development was abandoned not because hypertext was a bad idea htmx began life as [intercooler.js](https://intercoolerjs.org) back in [2013](https://github.com/bigskysoftware/intercooler-js/commit/62d3dbdb5c056ee866aba3575e148de649fc3efe). -In [april](https://github.com/bigskysoftware/htmx/commit/e38dea64dd1065003a0e833d7b469d24e6bc2919) of this year I began work on a jQuery-indepenent & improved version of intercoolerjs, renamed +In [april](https://github.com/bigskysoftware/htmx/commit/e38dea64dd1065003a0e833d7b469d24e6bc2919) of this year I began work on a jQuery-independent & improved version of intercoolerjs, renamed to htmx. I chose to rename the library because, in working on intercooler, I had come to appreciate that intercooler & htmx were completing HTML as a hypertext rather than just some funky, idiosyncratic javascript libraries. In [May](https://github.com/bigskysoftware/htmx/releases/tag/v0.0.1) htmx reached 0.0.1. Soon thereafter I had the good fortune of being contacted by [Ben Croker](https://twitter.com/ben_pylo) diff --git a/www/content/posts/2022-02-22-htmx-1.7.0-is-released.md b/www/content/posts/2022-02-22-htmx-1.7.0-is-released.md index 756691ec..08d0917b 100644 --- a/www/content/posts/2022-02-22-htmx-1.7.0-is-released.md +++ b/www/content/posts/2022-02-22-htmx-1.7.0-is-released.md @@ -20,7 +20,7 @@ I'm happy to announce the [1.7.0 release](https://unpkg.com/browse/htmx.org@1.7. to both of them without compromising the core file size of htmx. You are encouraged to move over to the new extensions, but `hx-sse` and `hx-ws` will continue to work indefinitely in htmx 1.x. * You can now mask out [attribute inheritance](@/docs.md#inheritance) via the [`hx-disinherit`](@/attributes/hx-disinherit.md) attribute. -* The `HX-Push` header can now have the `false` value, which will prevent a history snapshot from occuring. +* The `HX-Push` header can now have the `false` value, which will prevent a history snapshot from occurring. * Many new extensions, with a big thanks to all the contributors! * A new [`alpine-morph`](@/extensions/alpine-morph.md) extension allows you to use Alpine's swapping engine, which preserves Alpine state when you have entire Alpine components swapped by htmx. * A [restored](@/extensions/restored.md) extension was added that will trigger a `restore` event on all elements in the DOM diff --git a/www/content/posts/2023-07-14-htmx-1.9.3-is-released.md b/www/content/posts/2023-07-14-htmx-1.9.3-is-released.md index 95f34d30..62672338 100644 --- a/www/content/posts/2023-07-14-htmx-1.9.3-is-released.md +++ b/www/content/posts/2023-07-14-htmx-1.9.3-is-released.md @@ -22,7 +22,7 @@ I'm happy to announce the [1.9.3 release](https://unpkg.com/browse/htmx.org@1.9. ### Improvements & Bug fixes * We now have functioning CI using GitHub actions! -* Fix bug where the `htmx:afterSettle` event was raised multiple times with oob swaps occured +* Fix bug where the `htmx:afterSettle` event was raised multiple times with oob swaps occurred * A large number of accessibility fixes were made in the docs (Thank you Denis & crew!) * Fixed bug w/ WebSocket extension initialization caused by "naked" `hx-trigger` feature * Many other smaller bug fixes diff --git a/www/content/reference.md b/www/content/reference.md index 1046978f..96deb6ff 100644 --- a/www/content/reference.md +++ b/www/content/reference.md @@ -146,7 +146,7 @@ The table below lists all other attributes available in htmx. | [`htmx:historyCacheError`](@/events.md#htmx:historyCacheError) | triggered on an error during cache writing | [`htmx:historyCacheMiss`](@/events.md#htmx:historyCacheMiss) | triggered on a cache miss in the history subsystem | [`htmx:historyCacheMissError`](@/events.md#htmx:historyCacheMissError) | triggered on a unsuccessful remote retrieval -| [`htmx:historyCacheMissLoad`](@/events.md#htmx:historyCacheMissLoad) | triggered on a succesful remote retrieval +| [`htmx:historyCacheMissLoad`](@/events.md#htmx:historyCacheMissLoad) | triggered on a successful remote retrieval | [`htmx:historyRestore`](@/events.md#htmx:historyRestore) | triggered when htmx handles a history restoration action | [`htmx:beforeHistorySave`](@/events.md#htmx:beforeHistorySave) | triggered before content is saved to the history cache | [`htmx:load`](@/events.md#htmx:load) | triggered when new content is added to the DOM diff --git a/www/static/js/demo.js b/www/static/js/demo.js index 03de87ee..037006de 100644 --- a/www/static/js/demo.js +++ b/www/static/js/demo.js @@ -110,7 +110,7 @@ function onDelete(path, response) { } //==================================== -// Activites +// Activities //==================================== var requestId = 0; diff --git a/www/static/js/demo/it.js b/www/static/js/demo/it.js index f53a11b7..2e1084c0 100644 --- a/www/static/js/demo/it.js +++ b/www/static/js/demo/it.js @@ -13,7 +13,7 @@ `env => { with (env) { return \`${escapedCode}\` } }` )(params) } catch (e) { - log('demo:response-error', "An error occured during a mock response", e); + log('demo:response-error', "An error occurred during a mock response", e); return e.message; } } diff --git a/www/themes/htmx-theme/static/js/htmx.js b/www/themes/htmx-theme/static/js/htmx.js index 2fb8b9c5..6c68711d 100644 --- a/www/themes/htmx-theme/static/js/htmx.js +++ b/www/themes/htmx-theme/static/js/htmx.js @@ -227,7 +227,7 @@ return (function () { * @returns {boolean} */ function matches(elt, selector) { - // @ts-ignore: non-standard properties for browser compatability + // @ts-ignore: non-standard properties for browser compatibility // noinspection JSUnresolvedVariable var matchesFunction = elt.matches || elt.matchesSelector || elt.msMatchesSelector || elt.mozMatchesSelector || elt.webkitMatchesSelector || elt.oMatchesSelector; return matchesFunction && matchesFunction.call(elt, selector); @@ -285,7 +285,7 @@ return (function () { if (htmx.config.useTemplateFragments && partialResponse) { var documentFragment = parseHTML("<body><template>" + resp + "</template></body>", 0); // @ts-ignore type mismatch between DocumentFragment and Element. - // TODO: Are these close enough for htmx to use interchangably? + // TODO: Are these close enough for htmx to use interchangeably? return documentFragment.querySelector('template').content; } else { var startTag = getStartTag(resp); diff --git a/www/themes/htmx-theme/static/js/preload.js b/www/themes/htmx-theme/static/js/preload.js index f68feab5..a7493703 100644 --- a/www/themes/htmx-theme/static/js/preload.js +++ b/www/themes/htmx-theme/static/js/preload.js @@ -96,7 +96,7 @@ htmx.defineExtension("preload", { // Apply the listener to the node node.addEventListener(on, function(evt) { if (node.preloadState === "PAUSE") { // Only add one event listener - node.preloadState = "READY"; // Requred for the `load` function to trigger + node.preloadState = "READY"; // Required for the `load` function to trigger // Special handling for "mouseover" events. Wait 100ms before triggering load. if (on === "mouseover") { |