self-review

Archmonger · Archmonger · commit b22ce44c1169 · 2024-06-21T20:52:56.000-07:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -36,7 +36,9 @@ Using the following categories, list your changes in this order:
 
 ### Added
 
--   Client-side Python components can now be rendered via the new `pyscript_component` template tag
+-   Client-side Python components can now be rendered via the new `{% pyscript_component %}` template tag
+-   PyScript's can be made accessible for an existing page using the `{% pyscript_setup %}` template tag
+    -   This tag can also be used to load additional dependencies, or change the default PyScript configuration.
 -   Client-side components can be embedded into existing server-side components via `reactpy_django.components.pyscript_component`.
 -   You can now write Python code that runs within client browser via the `reactpy_django.html.pyscript` element. This is a viable substitution for most JavaScript code.
 
diff --git a/docs/src/reference/router.md b/docs/src/reference/router.md
@@ -20,7 +20,7 @@ URL router that enables the ability to conditionally render other components bas
 
 !!! warning "Pitfall"
 
-    All pages where this component exists must have the same, or more permissive exposure within Django's [URL patterns](https://docs.djangoproject.com/en/5.0/topics/http/urls/#example). You can think of this component as a secondary, client-side router. Django still handles the primary server-side routes.
+    All pages where `django_router` is used must have the same, or more permissive URL exposure within Django's [URL patterns](https://docs.djangoproject.com/en/5.0/topics/http/urls/#example). You can think of this component as a secondary, client-side router. Django still handles the primary server-side routes.
 
     We recommend creating a route with a wildcard `.*` to forward routes to ReactPy. For example...
     `#!python re_path(r"^/router/.*$", my_reactpy_view)`
diff --git a/docs/src/reference/template-tag.md b/docs/src/reference/template-tag.md
@@ -39,7 +39,7 @@ Each component loaded via this template tag will receive a dedicated WebSocket c
 
     The ReactPy component finder requires that your component path is a string.
 
-    **Do not** use Django template/context variables for the component path. Failure to follow this warning will result in components that will not render.
+    **Do not** use Django template/context variables for the component path. Failure to follow this warning will result in render failures.
 
     For example, **do not** do the following:
 
@@ -157,7 +157,7 @@ This template tag can be used to insert any number of **client-side** ReactPy co
 
 <!--pyscript-def-start-->
 
-By default, the only dependencies available are the standard Python library, `pyscript`, `pyodide`, `reactpy` core.
+By default, the only dependencies available are the Python standard library, `pyscript`, `pyodide`, `reactpy` core.
 
 Your PyScript component file requires a `#!python def root()` component to function as the entry point.
 
@@ -197,6 +197,8 @@ Your PyScript component file requires a `#!python def root()` component to funct
 
     PyScript components have the ability to directly execute JavaScript using the [`pyodide` `js` module](https://pyodide.org/en/stable/usage/type-conversions.html#importing-javascript-objects-into-python) or [`pyscript` foreign function interface](https://docs.pyscript.net/2024.6.1/user-guide/dom/).
 
+    _The `#!python js` module has access to everything within the browser's JavaScript environment. Therefore, any public JavaScript functions loaded within your HTML `#!html <head>` can be called as well. However, be mindful of JavaScript load order!_
+
     === "root.py"
 
         ```python
@@ -279,7 +281,7 @@ Your PyScript component file requires a `#!python def root()` component to funct
 
 ## PyScript Setup
 
-This template tag configures the current page to be able to run `pyscript` by loading JavaScript, CSS, and settings values.
+This template tag configures the current page to be able to run `pyscript` by loading PyScript's static files.
 
 You can optionally include a list of Python packages to install within the PyScript environment, or a [PyScript configuration dictionary](https://docs.pyscript.net/2024.6.1/user-guide/configuration/).
 
diff --git a/src/reactpy_django/pyscript/component_template.py b/src/reactpy_django/pyscript/component_template.py
@@ -12,9 +12,9 @@ def user_workspace_UUID():
     to prevent overlapping imports and variable names between different components.
 
     This code is designed to be run directly by PyScript, and is not intended to be run
-    in a standard Python environment.
+    in a normal Python environment.
 
-    Our template tag performs string substitutions to turn this file into valid PyScript.
+    ReactPy-Django's template tag performs string substitutions to turn this file into valid PyScript.
     """
 
     def root(): ...
diff --git a/src/reactpy_django/pyscript/layout_handler.py b/src/reactpy_django/pyscript/layout_handler.py
@@ -7,7 +7,7 @@ class ReactPyLayoutHandler:
     variable names between user code.
 
     This code is designed to be run directly by PyScript, and is not intended to be run
-    in a standard Python environment.
+    in a normal Python environment.
     """
 
     def __init__(self, uuid):
@@ -87,9 +87,10 @@ def event_handler(*args):
 
     @staticmethod
     def delete_old_workspaces():
-        """To prevent memory leaks, we must delete all user generated Python code
-        whe it is no longer on the page. To do this, we compare what UUIDs exist on
-        the DOM, versus what UUIDs exist within the PyScript global interpreter."""
+        """To prevent memory leaks, we must delete all user generated Python code when
+        it is no longer in use (removed from the page). To do this, we compare what
+        UUIDs exist on the DOM, versus what UUIDs exist within the PyScript global
+        interpreter."""
         import js
 
         dom_workspaces = js.document.querySelectorAll(".pyscript")
