minor fixes to last commit

custom_components/pyscript/eval.py

@@ -428,8 +428,9 @@ async def do_service_call(func, ast_ctx, data):
                                 break
                         else:
                             continue
-                        for ok_type in arg_info["type"]:
-                            mesg += f", or {ok_type.__name__}"
+                        mesg += ", or " + ", or ".join(
+                            sorted([ok_type.__name__ for ok_type in arg_info["type"]])
+                        )
                 self.logger.error(
                     "%s defined in %s: decorator @%s argument %d should be a %s; ignoring decorator",
                     self.name,

docs/reference.rst

@@ -175,7 +175,7 @@ the prior value is also available to the expression as ``domain.name.old`` in ca
 condition the trigger on the prior value too.
 
 Multiple arguments are logically "or"ed together, so the trigger occurs if any of the expressions
-evaluate to ``True``. Any argument can alternatively be be a list or set of strings, and they are
+evaluate to ``True``. Any argument can alternatively be a list or set of strings, and they are
 treated the same as multiple arguments by "or"ing them together.
 
 All state variables in HASS have string values. So you’ll have to do comparisons against string
@@ -205,7 +205,7 @@ You can specify a state trigger on any change with a string that is just the sta
    @state_trigger("domain.light_level")
 
 The trigger can include arguments with any mixture of string expressions (that are evaluated
-when any of the underlying state variable change) and string state variable names (that trigger
+when any of the underlying state variables change) and string state variable names (that trigger
 whenever that variable changes).
 
 Note that if a state variable is set to the same value, HASS doesn’t generate a state change event,