misc: Fix typos in examples

Author: JDBetteridge

examples/cfd/02_convection_nonlinear.ipynb

@@ -137,7 +137,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Excellent, we again get a wave that resembles the one from the oiginal examples.\n",
+    "Excellent, we again get a wave that resembles the one from the original examples.\n",
     "\n",
     "Now we can set up our coupled problem in Devito. Let's start by creating two initial state variables $u$ and $v$, as before, and initialising them with our \"hat function."
    ]

examples/cfd/07_cavity_flow.ipynb

@@ -464,7 +464,7 @@
     "u = TimeFunction(name='u', grid=grid, space_order=2)\n",
     "v = TimeFunction(name='v', grid=grid, space_order=2)\n",
     "p  = TimeFunction(name='p',  grid=grid, space_order=2)\n",
-    "#Variables are automatically initalized at 0.\n",
+    "#Variables are automatically initialized at 0.\n",
     "\n",
     "# First order derivatives will be handled with p.dxc\n",
     "eq_u =Eq(u.dt + u*u.dx + v*u.dy, -1./rho * p.dxc + nu*(u.laplace),  subdomain=grid.interior)\n",

examples/cfd/08_shallow_water_equation.ipynb

@@ -27,7 +27,7 @@
     "\n",
     "For a given bathymetry model, which can include a complex seafloor topography, we want to model the amplitudes, speed and interaction of waves at the seasurface. At a given point $(x,\\; y)$, the thickness of the water column between the seafloor and undisturbed water surface is defined by the variable $h$, while the wave amplitude is $\\eta$ and therefore the whole thickness of the water column $D = h + \\eta$.\n",
     "\n",
-    "Using appropriate boundary conditions at the water surface/seafloor, assuming that the horizontal wavelength of the modelled waves are much larger than the water depth and integrating the conservation of mass and momentum equations over the water column, we can derive the following equations to decribe wave propagation \n",
+    "Using appropriate boundary conditions at the water surface/seafloor, assuming that the horizontal wavelength of the modelled waves are much larger than the water depth and integrating the conservation of mass and momentum equations over the water column, we can derive the following equations to describe wave propagation \n",
     "\n",
     "\\begin{equation}\n",
     "\\begin{split}\n",
@@ -212,7 +212,7 @@
     "\\end{split}\\notag\n",
     "\\end{equation}\n",
     "\n",
-    "In order to avoid the occurence of high frequency artifacts, when waves are interacting with the boundaries, boundary conditions will be avoided. Normally Dirichlet conditions are used for the M and N discharge fluxes, and Neumann for the wave height field. Those lead to significant boundary reflections which might be not realistic for a given problem.\n",
+    "In order to avoid the occurrence of high frequency artifacts, when waves are interacting with the boundaries, boundary conditions will be avoided. Normally Dirichlet conditions are used for the M and N discharge fluxes, and Neumann for the wave height field. Those lead to significant boundary reflections which might be not realistic for a given problem.\n",
     "\n",
     "Let's assume the gravity $g = 9.81$ and the Manning's roughness coefficient $\\alpha = 0.025$ for the all the remaining examples."
    ]
@@ -8076,7 +8076,7 @@
    "source": [
     "## Example VI: 2D circular dam break problem\n",
     "\n",
-    "As a final modelling example, let's take a look at an (academic) engineering problem: a tsunami induced by the collapse of a circular dam in a lake with a constant bathymetry of 30 m. We only need to set the wave height in a circle with radius $r_0 = 5\\; m$ to $\\eta_0 = 0.5 \\; m$ and to zero everywhere else. To avoid the occurence of high frequency artifacts in the wavefield, known as numerical grid dispersion, we apply a Gaussian filter to the initial wave height. To achieve a symmetric dam collapse, the initial discharge fluxes $M_0,N_0$ are set to equal values."
+    "As a final modelling example, let's take a look at an (academic) engineering problem: a tsunami induced by the collapse of a circular dam in a lake with a constant bathymetry of 30 m. We only need to set the wave height in a circle with radius $r_0 = 5\\; m$ to $\\eta_0 = 0.5 \\; m$ and to zero everywhere else. To avoid the occurrence of high frequency artifacts in the wavefield, known as numerical grid dispersion, we apply a Gaussian filter to the initial wave height. To achieve a symmetric dam collapse, the initial discharge fluxes $M_0,N_0$ are set to equal values."
    ]
   },
   {

examples/cfd/09_Darcy_flow_equation.ipynb

@@ -400,7 +400,7 @@
    "metadata": {},
    "outputs": [],
    "source": [
-    "# Call operator for the 15,000th psuedo-timestep\n",
+    "# Call operator for the 15,000th pseudo-timestep\n",
     "output1 = darcy_flow_2d(w1, f)\n",
     "output2 = darcy_flow_2d(w2, f)\n",
     "output3 = darcy_flow_2d(w3, f)"

examples/cfd/tools.py

@@ -19,7 +19,7 @@ def plot_field(field, xmin=0., xmax=2., ymin=0., ymax=2., zmin=None, zmax=None,
     ymax : int, optional
         Length of the y-axis.
     view: int, optional
-        View point to intialise.
+        View point to initialise.
     """
     if xmin > xmax or ymin > ymax:
         raise ValueError("Dimension min cannot be larger than dimension max.")

examples/checkpointing/checkpoint.py

@@ -2,6 +2,6 @@
 
 warning("""The location of Devito's checkpointing has changed. This location will be
            deprecated soon. Please change your imports to 'from devito import
-           DevitoCheckpoint, CheckpointOperato'""")
+           DevitoCheckpoint, CheckpointOperator'""")
 
 from devito.checkpointing import *  # noqa

examples/compiler/01_data_regions.ipynb

@@ -263,7 +263,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "One can also pass a 3-tuple `(o, lp, rp)` instead of a single integer representing the discretization order. Here, `o` is the discretization order, while `lp` and `rp` indicate how many points are expected on left and right sides of a point of interest, respectivelly."
+    "One can also pass a 3-tuple `(o, lp, rp)` instead of a single integer representing the discretization order. Here, `o` is the discretization order, while `lp` and `rp` indicate how many points are expected on left and right sides of a point of interest, respectively."
    ]
   },
   {

examples/finance/bs_ivbp.ipynb

@@ -81,7 +81,7 @@
     "# smin = 50.0\n",
     "# smax = 150.0\n",
     "\n",
-    "# Amount of padding to proccess left/right (hidden from graphs)\n",
+    "# Amount of padding to process left/right (hidden from graphs)\n",
     "padding = 10\n",
     "smin -= padding\n",
     "smax += padding\n",

examples/mpi/overview.ipynb

@@ -627,7 +627,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "This is again a global data view. The shown *with_halo* is the \"true\" halo surrounding the physical domain (often referred to as the \"outer halo\"), **not** the halo used for the MPI halo exchanges (often referred to as \"ghost region\" or \"inner halo\"). A user can straightforwardly initialize the \"true\" halo region (which is typically read by a stencil `Eq` when an `Operator` iterates in proximity of the domain bounday).\n",
+    "This is again a global data view. The shown *with_halo* is the \"true\" halo surrounding the physical domain (often referred to as the \"outer halo\"), **not** the halo used for the MPI halo exchanges (often referred to as \"ghost region\" or \"inner halo\"). A user can straightforwardly initialize the \"true\" halo region (which is typically read by a stencil `Eq` when an `Operator` iterates in proximity of the domain boundary).\n",
     "\n",
     "Note: This \"halo\" is often encountered as \"ghost cell area\" in literature"
    ]

examples/performance/00_overview.ipynb

@@ -254,7 +254,7 @@
     "A few optimization options are available for this pass (but not on all platforms, see [here](https://github.com/devitocodes/devito/blob/main/examples/performance/README.md)), though in our experience the default values do a fine job:\n",
     "\n",
     "* `par-collapse-ncores`: use a collapse clause only if the number of available physical cores is greater than this value (default=4).\n",
-    "* `par-collapse-work`: use a collapse clause only if the trip count of the collapsable loops is statically known to exceed this value (default=100).\n",
+    "* `par-collapse-work`: use a collapse clause only if the trip count of the collapsible loops is statically known to exceed this value (default=100).\n",
     "* `par-chunk-nonaffine`: a coefficient to adjust the chunk size in non-affine parallel loops. The larger the coefficient, the smaller the chunk size (default=3).\n",
     "* `par-dynamic-work`: use dynamic scheduling if the operation count per iteration exceeds this value. Otherwise, use static scheduling (default=10).\n",
     "* `par-nested`: use nested parallelism if the number of hyperthreads per core is greater than this value (default=2).\n",
@@ -643,7 +643,7 @@
     "```\n",
     "\n",
     "So the sub-expression `a[1] + a[2]` is computed twice, by two consecutive iterations.\n",
-    "What makes CIRE complicated is the generalization to arbitrary expressions, the presence of multiple dimensions, the scheduling strategy due to the trade-off between redundant compute and working set, and the co-existance with other optimizations (e.g., blocking, vectorization). All these aspects won't be treated here. What instead we will show is the effect of CIRE in our running example and the optimization options at our disposal to drive the detection and scheduling of the captured redundancies.\n",
+    "What makes CIRE complicated is the generalization to arbitrary expressions, the presence of multiple dimensions, the scheduling strategy due to the trade-off between redundant compute and working set, and the co-existence with other optimizations (e.g., blocking, vectorization). All these aspects won't be treated here. What instead we will show is the effect of CIRE in our running example and the optimization options at our disposal to drive the detection and scheduling of the captured redundancies.\n",
     "\n",
     "In our running example, some cross-iteration redundancies are induced by the nested first-order derivatives along `y`. As we see below, these redundancies are captured and assigned to the two-dimensional temporary `r0`.\n",
     "\n",