Skip to content

Commit cd7109e

Browse files
Minor typo fixin doc.
PiperOrigin-RevId: 706774033
1 parent ed4e982 commit cd7109e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/notebooks/thinking_in_jax.ipynb

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1064,7 +1064,7 @@
10641064
"id": "C-QZ5d1DG-dv"
10651065
},
10661066
"source": [
1067-
"For this reason, a standard convention in JAX programs is to `import numpy as np` and `import jax.numpy as jnp` so that both interfaces are available for finer control over whether operations are performed in a static matter (with `numpy`, once at compile-time) or a traced manner (with `jax.numpy`, optimized at run-time)."
1067+
"For this reason, a standard convention in JAX programs is to `import numpy as np` and `import jax.numpy as jnp` so that both interfaces are available for finer control over whether operations are performed in a static manner (with `numpy`, once at compile-time) or a traced manner (with `jax.numpy`, optimized at run-time)."
10681068
]
10691069
}
10701070
],

docs/notebooks/thinking_in_jax.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -487,4 +487,4 @@ f(x)
487487

488488
+++ {"id": "C-QZ5d1DG-dv"}
489489

490-
For this reason, a standard convention in JAX programs is to `import numpy as np` and `import jax.numpy as jnp` so that both interfaces are available for finer control over whether operations are performed in a static matter (with `numpy`, once at compile-time) or a traced manner (with `jax.numpy`, optimized at run-time).
490+
For this reason, a standard convention in JAX programs is to `import numpy as np` and `import jax.numpy as jnp` so that both interfaces are available for finer control over whether operations are performed in a static manner (with `numpy`, once at compile-time) or a traced manner (with `jax.numpy`, optimized at run-time).

0 commit comments

Comments
 (0)