Fix various typos

Author: luzpaz

elastic-tube-1d/README.md

@@ -90,7 +90,7 @@ cd solid-python
 ./run.sh
 ```
 
-**Optional:** A run-time plot visualization can be trigged by passing `--enable-plot` in `run.sh` of `FluidSolver.py`. Additionally a video of the run-time plot visualization can be generated by additionally passing `--write-video`
+**Optional:** A run-time plot visualization can be triggered by passing `--enable-plot` in `run.sh` of `FluidSolver.py`. Additionally a video of the run-time plot visualization can be generated by additionally passing `--write-video`
 
 {% warning %}
 The C++ and Python solvers lead to different results. Please consider the Python results as the correct ones and refer to this [open issue](https://github.com/precice/tutorials/issues/195) for more insight. Contributions are particularly welcome here.

elastic-tube-1d/fluid-cpp/src/FluidComputeSolution.cpp

@@ -121,10 +121,10 @@ int fluidComputeSolutionSerial(
     const double velocity_in = u0 + ampl * sin(frequency * (t + t_shift) * PI);
     Res[0] = velocity_in - velocity[0];
 
-    /* Pressure Inlet is lineary interpolated */
+    /* Pressure Inlet is linearly interpolated */
     Res[N + 1] = -pressure[0] + 2 * pressure[1] - pressure[2];
 
-    /* Velocity Outlet is lineary interpolated */
+    /* Velocity Outlet is linearly interpolated */
     Res[N] = -velocity[N] + 2 * velocity[N - 1] - velocity[N - 2];
 
     /* Pressure Outlet is "non-reflecting" */
@@ -148,7 +148,7 @@ int fluidComputeSolutionSerial(
       break;
     }
 
-    /* Initilizing the the LHS i.e. Left Hand Side */
+    /* Initializing the the LHS i.e. Left Hand Side */
     std::fill(LHS_buffer.begin(), LHS_buffer.end(), 0.0);
 
     for (int i = 1; i < N; i++) {
@@ -188,11 +188,11 @@ int fluidComputeSolutionSerial(
 
     // Velocity Inlet is prescribed
     LHS(0, 0) = 1;
-    // Pressure Inlet is lineary interpolated
+    // Pressure Inlet is linearly interpolated
     LHS(N + 1, N + 1) = 1;
     LHS(N + 1, N + 2) = -2;
     LHS(N + 1, N + 3) = 1;
-    // Velocity Outlet is lineary interpolated
+    // Velocity Outlet is linearly interpolated
     LHS(N, N)     = 1;
     LHS(N, N - 1) = -2;
     LHS(N, N - 2) = 1;

elastic-tube-1d/fluid-python/thetaScheme.py

@@ -97,10 +97,10 @@ def perform_partitioned_theta_scheme_step(velocity0, pressure0, crossSection0, c
         # Velocity Inlet is prescribed
         res[0] = velocity_in - velocity1[0]
 
-        # Pressure Inlet is lineary interpolated
+        # Pressure Inlet is linearly interpolated
         res[N + 1] = -pressure1[0] + 2 * pressure1[1] - pressure1[2]
 
-        # Velocity Outlet is lineary interpolated
+        # Velocity Outlet is linearly interpolated
         res[N] = -velocity1[-1] + 2 * velocity1[-2] - velocity1[-3]
 
         # Pressure Outlet is "non-reflecting"

elastic-tube-3d/README.md

@@ -33,7 +33,7 @@ You can start the simulation by running the script `./run.sh` located in each pa
 
 ## Post-processing
 
-You can visualize the results using paraView or `cgx`(for native CalculiX resul files), as usual. The total deformation is rather small. Multiplying the deformation by factor of 10 (warp by vector filter in paraView) and visualizing the fluid domain at `t=0.005s` looks as follows:
+You can visualize the results using paraView or `cgx`(for native CalculiX result files), as usual. The total deformation is rather small. Multiplying the deformation by factor of 10 (warp by vector filter in paraView) and visualizing the fluid domain at `t=0.005s` looks as follows:
 
 ![result tube](images/tutorials-elastic-tube-3d-tube-result.png)
 

multiple-perpendicular-flaps/README.md

@@ -27,7 +27,7 @@ For a case showing fluid-structure interaction only (no multi-coupling), take a
 
 ## Why multi-coupling?
 
-This is a case with three participants: the fluid and each flap. In preCICE, there are two options to [couple more than two participants](https://www.precice.org/configuration-coupling-multi.html). The first option a composition of bi-coupling schemes, in which we must specify the exchange of data in a participant to participant manner. However, such a composition is not suited for combining multiple strong fluid-structure interations [1]. Thus, in this case, we use the second option, fully-implicit multi-coupling.
+This is a case with three participants: the fluid and each flap. In preCICE, there are two options to [couple more than two participants](https://www.precice.org/configuration-coupling-multi.html). The first option a composition of bi-coupling schemes, in which we must specify the exchange of data in a participant to participant manner. However, such a composition is not suited for combining multiple strong fluid-structure interactions [1]. Thus, in this case, we use the second option, fully-implicit multi-coupling.
 
 We can set this in our `precice-config.xml`:
 
@@ -44,7 +44,7 @@ The participant that has the control is the one that it is connected to all othe
 
 For the fluid participant we use OpenFOAM. In particular, we use the application `pimpleFoam`. The geometry of the Fluid participant is defined in the file `Fluid/system/blockMeshDict`. Besides, we must specify where are we exchanging data with the other participants. The interfaces are set in the file `Fluid/system/preciceDict`. In this file, we set to exchange stress and displacement on the surface of each flap.
 
-Most of the coupling details are specified in the file `precide-config.xml`. Here we estipulate the order in which we read/write data from one participant to another or how we map from the fluid to the solid's mesh. In particular, we have choosen the nearest-neighbor mapping scheme.
+Most of the coupling details are specified in the file `precide-config.xml`. Here we estipulate the order in which we read/write data from one participant to another or how we map from the fluid to the solid's mesh. In particular, we have chosen the nearest-neighbor mapping scheme.
 
 For the simulation of the solid participants we use the deal.II adapter. In deal.II, the geometry of the domain is specified directly on the solver. The two flaps in our case are essentially the same but for the x-coordinate. The flap geometry is given to the solver when we select the scenario in the '.prm' file.
 

turek-hron-fsi3/README.md

@@ -49,7 +49,7 @@ cd solid-dealii
 
 You can also run OpenFOAM in parallel by `./run.sh -parallel`. The default setting here uses 25 MPI ranks. You can change this setting in `fluid-openfoam/system/decomposeParDict`.
 
-You may adjust the end time in the `precice-config.xml`, or interupt the execution earlier if you want.
+You may adjust the end time in the `precice-config.xml`, or interrupt the execution earlier if you want.
 
 In the first few timesteps, many coupling iterations are required for convergence. Don't lose hope, things get better quickly.