a few minor edits

Author: craigbarratt

docs/new_features.rst

@@ -19,7 +19,7 @@ The new features since 0.32 in master include:
 - Pyscript state variables (entity_ids) can be persisted across pyscript reloads and HASS restarts,
   from @swazrgb and @dlashua (#48).
 - ``@state_trigger`` now supports triggering on an attribute change with ``"domain.entity.attr"`` and
-  any attribute change with ``"domain.entity.*"``, submitted by @dlashua (#82)
+  any attribute change with ``"domain.entity.*"``, from @dlashua (#82)
 - State variables now support virtual attributes ``last_changed`` and ``last_updated`` for the UTC time when state
   values or any attribute was last changed.
 - State variable values (eg, from ``domain.entity`` or ``state.get()``) now include attributes that can be accessed
@@ -34,11 +34,11 @@ The new features since 0.32 in master include:
   is true (default false). This allows access to HASS internals that might not be otherwise exposed by pyscript.
   Use with caution (#51).
 - Improvements to UI config flow, including allowing parameters to be updated, and the UI reload now works the same
-  as the ``pyscript.reload`` service call, submitted by @raman325 (#53)
+  as the ``pyscript.reload`` service call, from @raman325 (#53)
 - Added inbound ``context`` variable to trigger functions and support optional ``context`` setting on state,
-  event firing and service calls. Proposal and PR by @dlashua (#50, #60).
+  event firing and service calls. Proposal and PR from @dlashua (#50, #60).
 - Logbook now supported using ``context`` and informational message based on trigger type. Proposal and PR
-  by @dlashua (#50, #62).
+  from @dlashua (#50, #62).
 - Required Python packages can be specified in ``requirements.txt`` files at the top-level pyscript
   directory, and each module's or app's directory. Those files are read and any missing packages are
   installed on HASS startup and pyscript reload. If a specific version of a package is needed, it must be
@@ -69,5 +69,5 @@ The bug fixes since 0.32 in master include:
 - Jupyter autocomplete now works on multiline code blocks.
 - Improved error message reporting for syntax errors inside f-strings.
 - Fixed incorrect global context update on calling module that, in turn, does a callback (#58).
-- `task.wait_until` no longer silently ignores unrecognized keyword arguments (#80).
-- `task.wait_until` incorrectly ignored the keyword optional state_check_now argument (#81).
+- ``task.wait_until`` no longer silently ignores unrecognized keyword arguments (#80).
+- ``task.wait_until`` incorrectly ignored the keyword optional state_check_now argument (#81).

docs/reference.rst

@@ -260,9 +260,9 @@ function.
     @state_trigger(str_expr, ..., state_hold=None, state_check_now=False)
 
 ``@state_trigger`` takes one or more string arguments that contain any expression based on one or
-more state variables, and evaluates to ``True`` or ``False`` (or non-zero or zero). Whenever the
-state variables or attributes values mentioned in the expression change, the expression is evaluated
-and the trigger occurs if it evaluates to ``True`` (or non-zero). For each state variable,
+more state variables, and evaluates to ``True`` or ``False`` (or non-zero or zero). Whenever any
+of the state variables or attribute values mentioned in the expression change, the expression is
+evaluated and the trigger occurs if it evaluates to ``True`` (or non-zero). For each state variable,
 eg: ``domain.name``, the prior value is also available to the expression as ``domain.name.old``
 in case you want to condition the trigger on the prior value too. Attribute values can be used
 in the expression too, using the forms ``domain.name.attr`` and ``domain.name.old.attr`` for
@@ -312,12 +312,10 @@ form ``DOMAIN.name.attr``. Attributes maintain their original type, so there is
 then to another type.
 
 You can specify a state trigger on any change with a string that can take three forms:
-``"domain.entity"``
-  triggers on any change to the state variable value
-``"domain.entity.attr"``
-  triggers on any change to the state variable attribute ``attr`` value
-``"domain.entity.*"``
-  triggers on any change to any state variable attribute (but not its value)
+
+- ``"domain.entity"``: triggers on any change to the state variable value
+- ``"domain.entity.attr"``: triggers on any change to the state variable attribute ``attr`` value
+- ``"domain.entity.*"``: triggers on any change to any state variable attribute (but not its value)
 
 For example:
 

info.md

@@ -23,7 +23,7 @@ See the documentation if you want to install pyscript manually.
 
 ## Configuration
 
-* Go to the Integrations menu in the Home Assistant Configuration UI and add `Pyscript Python scripting` from there, or add `pyscript:` to `<config>/configuration.yaml`; there is one optional parameter (see docs)
+* Go to the Integrations menu in the Home Assistant Configuration UI and add `Pyscript Python scripting` from there, or add `pyscript:` to `<config>/configuration.yaml`; see docs for optional parameters
 * Add files with a suffix of `.py` in the folder `<config>/pyscript`.
 * Whenever you change a script file, make a `reload` service call to `pyscript`.
 * Watch the HASS log for `pyscript` errors and logger output from your scripts.