@@ -96,7 +96,7 @@ the cell in which the function is defined or exiting the Jupyter session will no
9696already running function. This is same behavior as ` reload ` . In pyscript, each triggered function
9797(ie, a trigger has occurred and the trigger conditions are met, and the function is actually
9898executing Python code) runs as an independent task until it finishes. So if you are testing triggers
99- of a long-running function (eg, one that uses ` task.sleep() or ` task.wait_until()`) you could end up
99+ of a long-running function (eg, one that uses ` task.sleep() ` or ` task.wait_until() ` ) you could end up
100100with many running instances. It's strongly recommended that you use ` task.unique() ` to make sure old
101101running function tasks are terminated when a new one is triggered. Then you can manually call
102102` task.unique() ` to terminate that last running function before exiting the Jupyter session.
@@ -106,7 +106,7 @@ triggers, functions or services there, then those objects will survive the termi
106106of your Jupyter session. However, if you ` reload ` the scripts, then those newly-created
107107objects will be removed. To make any additions or changes permanent (meaning they will
108108be re-created on each ` reload ` or each time your restart HASS) then you shoud copy the
109- changes or additions to one of you pyscript script files.
109+ changes or additions to one of your pyscript script files.
110110
111111## Global Contexts
112112
@@ -145,4 +145,4 @@ have a different iPython instance), so each tab (eg, a notebook in one and a con
145145will have different global contexts. If you wish, you can use the function ` pyscript.set_global_ctx() `
146146to set the context in the other tabs to be the same as the first.
147147
148- * Jupyter auto-completion it doesn't yet work in Jupyter lab - that's an open bug I need to fix.
148+ * Jupyter auto-completion doesn't yet work in Jupyter lab - that's an open bug I need to fix.
0 commit comments