Fix typos (#1007)

* Fix typos

Found via:
- `codespell -S package-lock.json -L inflight,ue,falsy`
- `typos --format brief`

* fix capitalization

* fix capitalization

* fix capitalization

---------

Co-authored-by: Ryan Morshead <ryan.morshead@gmail.com>

Author: kianmeng

docs/README.md

@@ -3,7 +3,7 @@
 We provide two main ways to run the docs. Both use
 [`nox`](https://pypi.org/project/nox/):
 
-- `nox -s docs` - displayes the docs and rebuilds when files are modified.
+- `nox -s docs` - displays the docs and rebuilds when files are modified.
 - `nox -s docs-in-docker` - builds a docker image and runs the docs from there.
 
 If any changes to the core of the documentation are made (i.e. to non-`*.rst` files),

docs/source/_custom_js/src/index.js

@@ -86,7 +86,7 @@ function triggerIfInViewport(element, callback) {
     },
     {
       root: null,
-      threshold: 0.1, // set offset 0.1 means trigger if atleast 10% of element in viewport
+      threshold: 0.1, // set offset 0.1 means trigger if at least 10% of element in viewport
     },
   );
 

docs/source/about/changelog.rst

@@ -62,7 +62,7 @@ v1.0.0-a4
 
 **Deprecated**
 
-- :pull:`919` - Declaration of keys via keywork arguments in standard elements. A script
+- :pull:`919` - Declaration of keys via keyword arguments in standard elements. A script
   has been added to automatically convert old usages where possible.
 
 
@@ -590,7 +590,7 @@ v0.35.2
 This release includes several bug fixes. The most significant of which is the ability to
 change the type of an element in the try (i.e. to and from being a component) without
 getting an error. Originally the errors were introduced because it was though changing
-element type would not be desireable. This was not the case though - swapping types
+element type would not be desirable. This was not the case though - swapping types
 turns out to be quite common and useful.
 
 **Closed Issues**

docs/source/guides/adding-interactivity/components-with-state/_examples/adding_state_variable/data.json

@@ -44,7 +44,7 @@
   {
     "name": "Terracotta Army",
     "artist": "Unknown Artist",
-    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consited of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
+    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consisted of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
     "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/9/9a/2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg/1920px-2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg",
     "alt": "12 terracotta sculptures of solemn warriors, each with a unique facial expression and armor."
   },

docs/source/guides/adding-interactivity/components-with-state/_examples/isolated_state/data.json

@@ -44,7 +44,7 @@
   {
     "name": "Terracotta Army",
     "artist": "Unknown Artist",
-    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consited of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
+    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consisted of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
     "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/9/9a/2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg/1920px-2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg",
     "alt": "12 terracotta sculptures of solemn warriors, each with a unique facial expression and armor."
   },

docs/source/guides/adding-interactivity/components-with-state/_examples/multiple_state_variables/data.json

@@ -44,7 +44,7 @@
   {
     "name": "Terracotta Army",
     "artist": "Unknown Artist",
-    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consited of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
+    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consisted of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
     "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/9/9a/2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg/1920px-2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg",
     "alt": "12 terracotta sculptures of solemn warriors, each with a unique facial expression and armor."
   },

docs/source/guides/adding-interactivity/components-with-state/_examples/when_variables_are_not_enough/data.json

@@ -44,7 +44,7 @@
   {
     "name": "Terracotta Army",
     "artist": "Unknown Artist",
-    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consited of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
+    "description": "The Terracotta Army is a collection of terracotta sculptures depicting the armies of Qin Shi Huang, the first Emperor of China. The army consisted of more than 8,000 soldiers, 130 chariots with 520 horses, and 150 cavalry horses.",
     "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/9/9a/2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg/1920px-2015-09-22-081415_-_Terrakotta-Armee%2C_Grosse_Halle.jpg",
     "alt": "12 terracotta sculptures of solemn warriors, each with a unique facial expression and armor."
   },

docs/source/guides/adding-interactivity/dangers-of-mutability/index.rst

@@ -531,7 +531,7 @@ Removing Set Items
             s.difference_update(values)
             s -= values  # "in-place" operators mutate!
 
-            s.symetric_difference_update(values)
+            s.symmetric_difference_update(values)
             s ^= values  # "in-place" operators mutate!
 
             s.intersection_update(values)
@@ -547,7 +547,7 @@ Removing Set Items
             s.difference(values)
             s - values
 
-            s.symetric_difference(values)
+            s.symmetric_difference(values)
             s ^ values
 
             s.intersection(values)

docs/source/guides/adding-interactivity/index.rst

@@ -111,7 +111,7 @@ Section 3: State as a Snapshot
 ------------------------------
 
 As we :ref:`learned earlier <Components with State>`, state setters behave a little
-differently than you might exepct at first glance. Instead of updating your current
+differently than you might expect at first glance. Instead of updating your current
 handle on the setter's corresponding variable, it schedules a re-render of the component
 which owns the state.
 
@@ -133,7 +133,7 @@ actually sent?
 .. reactpy:: state-as-a-snapshot/_examples/print_chat_message
 
 As it turns out, changing the message recipient after pressing send does not change
-where the message ulitmately goes. However, one could imagine a bug where the recipient
+where the message ultimately goes. However, one could imagine a bug where the recipient
 of a message is determined at the time the message is sent rather than at the time the
 "Send" button it clicked. Thus changing the recipient after pressing send would change
 where the message got sent.

docs/source/guides/adding-interactivity/multiple-state-updates/index.rst

@@ -10,7 +10,7 @@ Batched Updates
 ---------------
 
 As we learned :ref:`previously <state as a snapshot>`, state variables remain fixed
-inside each render as if state were a snapshot taken at the begining of each render.
+inside each render as if state were a snapshot taken at the beginning of each render.
 This is why, in the example below, even though it might seem like clicking the
 "Increment" button would cause the ``number`` to increase by ``3``, it only does by
 ``1``:
@@ -22,7 +22,7 @@ the event handler is not an ``async`` function), ReactPy waits until all the cod
 event handler has run before processing state and starting the next render. Thus, it's
 the last call to a given state setter that matters. In the example below, even though we
 set the color of the button to ``"orange"`` and then ``"pink"`` before ``"blue"``,
-the color does not quickly flash orange and pink before blue - it alway remains blue:
+the color does not quickly flash orange and pink before blue - it always remains blue:
 
 .. reactpy:: _examples/set_color_3_times