@@ -134,7 +134,7 @@ To run a code cell independently, the cell needs to first be activated. This
134
134
is done by clicking on it with the cursor. Jupyter will indicate a cell has been
135
135
activated by highlighting it with a blue rectangle to its left. After the cell
136
136
has been activated ({numref}` activate-and-run-button ` ), the cell can be run by either pressing
137
- the ** Run** (&blacktriangleright ; ) button in the toolbar, or by using a keyboard shortcut of
137
+ the ** Run** (&#x 23F5 ; ) button in the toolbar, or by using a keyboard shortcut of
138
138
` Shift + Enter ` .
139
139
140
140
``` {figure} img/jupyter/activate-and-run-button-annotated.png
@@ -231,7 +231,7 @@ To edit a Markdown cell in Jupyter, you need to double click on the cell. Once
231
231
you do this, the unformatted (or * unrendered* ) version of the text will be
232
232
shown ({numref}` markdown-cell-not-run ` ). You
233
233
can then use your keyboard to edit the text. To view the formatted
234
- (or * rendered* ) text ({numref}` markdown-cell-run ` ), click the ** Run** (&blacktriangleright ; ) button in the toolbar,
234
+ (or * rendered* ) text ({numref}` markdown-cell-run ` ), click the ** Run** (&#x 23F5 ; ) button in the toolbar,
235
235
or use the ` Shift + Enter ` keyboard shortcut.
236
236
237
237
``` {figure} img/jupyter/markdown-cell-not-run.png
@@ -285,7 +285,7 @@ As you might know (or at least imagine) by now, Jupyter notebooks are great for
285
285
interactively editing, writing and running Python code; this is what they were
286
286
designed for! Consequently, Jupyter notebooks are flexible in regards to code
287
287
cell execution order. This flexibility means that code cells can be run in any
288
- arbitrary order using the ** Run** (&blacktriangleright ; ) button. But this flexibility has a downside:
288
+ arbitrary order using the ** Run** (&#x 23F5 ; ) button. But this flexibility has a downside:
289
289
it can lead to Jupyter notebooks whose code cannot be executed in a linear
290
290
order (from top to bottom of the notebook). A nonlinear notebook is problematic
291
291
because a linear order is the conventional way code documents are run, and
@@ -294,7 +294,7 @@ code is used in some automated process, it will need to run in a linear order,
294
294
from top to bottom of the notebook.
295
295
296
296
The most common way to inadvertently create a nonlinear notebook is to rely solely
297
- on using the (&blacktriangleright ; ) button to execute cells. For example,
297
+ on using the (&#x 23F5 ; ) button to execute cells. For example,
298
298
suppose you write some Python code that creates a Python object, say a variable named
299
299
` y ` . When you execute that cell and create ` y ` , it will continue
300
300
to exist until it is deliberately deleted with Python code, or when the Jupyter
0 commit comments