Skip to content

Commit 0bd79ba

Browse files
committed
a couple fixes for small things
1 parent e71e2e9 commit 0bd79ba

1 file changed

Lines changed: 3 additions & 7 deletions

File tree

content/cupy.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# CuPy
22

33
:::{questions}
4-
- How could I make my Python code to run on a GPU
5-
- How do I copy data to the GPU memory
4+
- How could I make my Python code to run on a GPU?
5+
- How do I copy data to the GPU memory?
66
:::
77

88
:::{objectives}
@@ -28,10 +28,6 @@ By design, the CuPy interface is as close as possible to NumPy/SciPy,
2828
making code porting much easier.
2929

3030

31-
32-
:::{highlight} python
33-
:::
34-
3531
## Basics of CuPy
3632

3733
CuPy's syntax here is identical to that of NumPy. A list of
@@ -661,7 +657,7 @@ Names of NumPy data types can be used as type specifiers.
661657
... 'my_kernel') # kernel name
662658
```
663659

664-
In the first line, the object instantiation is named `kernel`.
660+
In the first line, the object instantiation is named `my_kernel`.
665661
The next line has the variables to be used as input (x and y) and output (z).
666662
These variables can be typed with NumPy data types, as shown.
667663
The function code then follows. The last line states the kernel name,

0 commit comments

Comments
 (0)