Apply suggestions from code review

Co-authored-by: Erik van Sebille <[email protected]>

Author: reint-fischer

docs/user_guide/examples/tutorial_statuscodes.md

@@ -82,14 +82,15 @@ If we advect particles with the `AdvectionRK2_3D` kernel, Parcels will raise a `
 
 ```{code-cell}
 :tags: [raises-exception]
-pset = parcels.ParticleSet(fieldset, parcels.Particle, z=[0.5],lat=[2], lon=[1.5])
-pset.execute([parcels.kernels.AdvectionRK2_3D],runtime=np.timedelta64(1, "m"), dt=np.timedelta64(1, "s"), verbose_progress=False)
+pset = parcels.ParticleSet(fieldset, parcels.Particle, z=[0.5], lat=[2], lon=[1.5])
+kernels = [parcels.kernels.AdvectionRK2_3D]
+pset.execute(kernels, runtime=np.timedelta64(1, "m"), dt=np.timedelta64(1, "s"), verbose_progress=False)
 ```
 
 When we add the `KeepInOcean` Kernel, particles will stay at the surface:
 
 ```{code-cell}
-pset = parcels.ParticleSet(fieldset, parcels.Particle, z=[0.5],lat=[2], lon=[1.5])
+pset = parcels.ParticleSet(fieldset, parcels.Particle, z=[0.5], lat=[2], lon=[1.5])
 
 kernels = [parcels.kernels.AdvectionRK2_3D, KeepInOcean]
 
@@ -99,5 +100,5 @@ print(f"particle z at end of run = {pset.z}")
 ```
 
 ```{note}
-Kernels that control what to do with `particles.state` should typically be added at the _end_ of the Kernel list, because otherwise later Kernels may overwrite the `particles.state` or the `particles.dlon` variables.
+Kernels that control what to do with `particles.state` should typically be added at the _end_ of the Kernel list, because otherwise later Kernels may overwrite the `particles.state` or the `particles.dlon` variables (see [Kernel loop explanation](explanation_kernelloop.md)).
 ```