diff --git a/hugo/content/installation/building/unix/third-party.md b/hugo/content/installation/building/unix/third-party.md
index e3bebb9895035a947ddca6220e72c564e6383f4b..00deb3ba855106cc9bb82bd40be1236c6182dc49 100644
--- a/hugo/content/installation/building/unix/third-party.md
+++ b/hugo/content/installation/building/unix/third-party.md
@@ -37,7 +37,7 @@ Recommended software:
 
 All these can be easily installed on most Linux distributions using
 the system's package manager. Below are a few examples for several
-selected operating systems. Please note, that other distributions
+selected operating systems. Note that other distributions
 (Fedora, Mint, etc) may have different commands for invoking the
 package manager and slightly different names of packages (like `boost`
 instead of `libboost` etc). Besides that, the installation should be
@@ -92,7 +92,7 @@ Install newer compiler:
 Enable the new compiler (you will have to run this command for every new terminal):
     <pre><code>$ scl enable devtoolset-4 bash</code></pre>
 
-Make sure, that gcc gives you version 9.0 or higher:
+Make sure that gcc gives you version 9.0 or higher:
     <pre><code>$ g++ --version</code></pre>
 
 ### MacOS
diff --git a/hugo/content/installation/install/windows/python-anaconda/index.md b/hugo/content/installation/install/windows/python-anaconda/index.md
index 76fbc703caf80004cb3f923e97f9a3e73e382aa3..7a582259ec1bd1cda62d347e949a3fc7939788db 100644
--- a/hugo/content/installation/install/windows/python-anaconda/index.md
+++ b/hugo/content/installation/install/windows/python-anaconda/index.md
@@ -11,13 +11,13 @@ using the Anaconda Python distribution and how to run BornAgain in the `conda` e
 ### Download the Anaconda installer
 
 Download the Anaconda distribution for Windows from the [Official website](https://www.anaconda.com/distribution/).
-Please make sure, that
+Make sure that
 
 + you are downloading the Windows version,
 + you are downloading the 64-bit version,
 + your Anaconda Python version major number is the same as the version of Python specified in the BornAgain installer name.
 
-This means, that for BornAgain installed using the installer with the name `{{% recommended-wininstaller %}}` 
+This means that for BornAgain installed using the installer with the name `{{% recommended-wininstaller %}}` 
 you need `Anaconda Python {{% recommended-python %}} 64-Bit version`.
 
 {{< figscg src="anaconda-install-step0.png" class="center" width="450px" caption="Anaconda website download page">}}
@@ -81,7 +81,7 @@ python C:/BornAgain-{{< release-string >}}/Examples/scatter2d/CylindersAndPrisms
 
 {{< figscg src="anaconda-running-step3.png" class="center" width="450px">}}
 
-The used path implies, that BornAgain was installed to the default location. If this was not the case, you will have to adjust the path to the BornAgain Python example accordingly.
+The used path implies that BornAgain was installed to the default location. If this was not the case, you will have to adjust the path to the BornAgain Python example accordingly.
 
 {{< alert theme="info" >}}
 `Tip:` while typing long commands in the command shell you can push the `TAB` key and Windows will attempt to autocomplete long directory names.
diff --git a/hugo/content/installation/install/windows/python-original/python-pycharm/index.md b/hugo/content/installation/install/windows/python-original/python-pycharm/index.md
index 4b5610707e31bb66b389b6f0c4b617c6c858cbe2..100b07546bb4b50872bd052c31eebeb6bfb0efee 100644
--- a/hugo/content/installation/install/windows/python-original/python-pycharm/index.md
+++ b/hugo/content/installation/install/windows/python-original/python-pycharm/index.md
@@ -47,7 +47,7 @@ The final window for project creation should look like the screenshot below.
 Push `create project` button.
 
 {{< alert theme="info" >}}
-Up to now, we have configured `PyCharm` to work with the system interpreter directly. Please note that `PyCharm` has the possibility to run code in a so-called `virtual environment`. The detailed description of the configuration process can be found on the
+Up to now, we have configured `PyCharm` to work with the system interpreter directly. Note that `PyCharm` has the possibility to run code in a so-called `virtual environment`. The detailed description of the configuration process can be found on the
 [official web site](https://www.jetbrains.com/help/pycharm/configuring-python-interpreter.html).
 {{< /alert >}}
 
@@ -58,7 +58,7 @@ As soon as you push the `Create` button, you will be presented with the initial
 
 {{< figscg src="python-pycharm-project7.png" class="center" width="450px">}}
 
-Please also note, that `PyCharm` will automatically start with `indexing` (see the label and the progress bar at the bottom of the screen). This is a one-time procedure in which `PyCharm` familiarizes itself with the project interpreter and its environment. This phase can last from several minutes up to half an hour, depending on the speed of your computer. During this phase you will not be able to run any of the Python scripts.
+Also note that `PyCharm` will automatically start with `indexing` (see the label and the progress bar at the bottom of the screen). This is a one-time procedure in which `PyCharm` familiarizes itself with the project interpreter and its environment. This phase can last from several minutes up to half an hour, depending on the speed of your computer. During this phase you will not be able to run any of the Python scripts.
 
 Now, let's add the BornAgain examples to the project directory to be able to run and modify any of them at any time. Go to the `File/Settings` menu:
 
diff --git a/hugo/content/py/fitting/extended/polarized-spinasymmetry-fit/index.md b/hugo/content/py/fitting/extended/polarized-spinasymmetry-fit/index.md
index 826156d0dc0f861947e6711807a887d52e49f86d..67a5499bed6b31d8d76d1610e1a65e5d0eb2ea9d 100644
--- a/hugo/content/py/fitting/extended/polarized-spinasymmetry-fit/index.md
+++ b/hugo/content/py/fitting/extended/polarized-spinasymmetry-fit/index.md
@@ -35,7 +35,7 @@ This is supported in BornAgain by setting
 fit_objective.setObjectiveMetric("chi2")
 ```
 
-It must be noted, that in order to obtain good results, one needs to provide the uncertainties
+Note that in order to obtain good results, one needs to provide the uncertainties
 of the reflectivity.
 If no uncertainties are available, using the relative difference `fit_objective.setObjectiveMetric("reldiff")` yields better results.
 If the relative difference is selected and uncertainties are provided, BornAgain automatically falls back to the above $\chi^2$ metric.
diff --git a/hugo/content/py/fitting/extended/reflectometry-pt-layer/index.md b/hugo/content/py/fitting/extended/reflectometry-pt-layer/index.md
index d46ec4c9ae94f004b4c342e4c9262b9dbe4c7e29..97f332c7f9d6dde48b53c3172b12ba56956d621f 100644
--- a/hugo/content/py/fitting/extended/reflectometry-pt-layer/index.md
+++ b/hugo/content/py/fitting/extended/reflectometry-pt-layer/index.md
@@ -63,7 +63,7 @@ q = numpy.array(result.result().axis(ba.Axes.QSPACE)) - q_offset
 ##### Initial parameters
 
 In order to successfully fit this example, we chose some sane starting values and
-the example code, that is fully given below, can be run with the following command:
+the example code that is fully given below, can be run with the following command:
 ```python
 python3 Pt_layer_fit.py fit
 ```
diff --git a/hugo/content/py/result/export/axes-in-different-units/index.md b/hugo/content/py/result/export/axes-in-different-units/index.md
index 2246a59c3d0f467bb18a7e1ba54ee5763230d104..ad714a039a3e41e297a1662f22f8417e6d3f38de 100644
--- a/hugo/content/py/result/export/axes-in-different-units/index.md
+++ b/hugo/content/py/result/export/axes-in-different-units/index.md
@@ -12,7 +12,7 @@ In this example we demonstrate how to plot intensity data with detector axes exp
 sample is used to setup the simulation.
 * When the simulation is completed, the `Simulation::result()` method is used to get a `SimulationResult` object.
 * Depending on an additional parameter `IDetector2D.NBINS`, `IDetector2D.DEGREES`, `IDetector2D.QYQZ`, it will be plotted with axes defined either in millimeters (default units of `RectangularDetector`), detector bins, degrees or in $Q$-space.
-* Please note, that the given parameter only affects min/max values of histogram axes (there is no rebinning involved).
+* Note that the given parameter only affects min/max values of histogram axes (there is no rebinning involved).
 
 {{< galleryscg >}}
 {{< figscg src="/img/auto/scatter2d/AxesInDifferentUnits.png" width="670px" caption="Intensity images">}}
diff --git a/hugo/content/ref/instr/det/offspec.md b/hugo/content/ref/instr/det/offspec.md
index a8574ae281686d111749a81f79f763b258145287..da928076295f9b4cf07bf019aa810cb0a73ad7a8 100644
--- a/hugo/content/ref/instr/det/offspec.md
+++ b/hugo/content/ref/instr/det/offspec.md
@@ -15,4 +15,4 @@ ba.OffspecDetector(nphi, phi_min, phi_max, nalpha, alpha_min, alpha_max)
 Scattering intensity is computed for `nphi` azimuthal bins, then naively summed.
 
 Results may vary widely for even vs odd `nphi`. Check!
-Choose the phi range so narrow, and `nphi` so large, that results become stable.
+Choose the phi range so narrow, and `nphi` so large that results become stable.
diff --git a/hugo/content/ref/instr/det/rectangular-detector/index.md b/hugo/content/ref/instr/det/rectangular-detector/index.md
index c9138ed388b903d75ab025e3e8ca5dcc29ee1b7d..11601f8d1736a8d6172b2aa6717d3433360685ea 100644
--- a/hugo/content/ref/instr/det/rectangular-detector/index.md
+++ b/hugo/content/ref/instr/det/rectangular-detector/index.md
@@ -89,7 +89,7 @@ direction: direction of detector u-axis with respect to the sample coordinate sy
 """
 ```
 
-Please note, that the direction vector **u** is set by default to `(0.0, -1.0, 0.0)` which corresponds to the detector u-axis pointing to the right, as shown in the plot above (green arrow on the detector plane). This value should not be changed, unless the user has to deal with a rotation of the detector around the normal vector **n**.
+Note that the direction vector **u** is set by default to `(0.0, -1.0, 0.0)` which corresponds to the detector u-axis pointing to the right, as shown in the plot above (green arrow on the detector plane). This value should not be changed, unless the user has to deal with a rotation of the detector around the normal vector **n**.
 
 In the following, we will show how to set the detector's parameters for the three most common cases in GISAS experimental setups:
 
@@ -103,7 +103,7 @@ In this case the normal vector **n** coincides with the x-axis of the sample coo
 
 {{< figscg src="/img/draw/rectangular_detector_samplepos.png" width="600" class="center">}}
 
-The following code demonstrates the creation of the detector shown in the plot. Please note, that the values of the parameters are given only as an example and do not reflect the relative proportions in the plot.
+The following code demonstrates the creation of the detector shown in the plot. Note that the values of the parameters are given only as an example and do not reflect the relative proportions in the plot.
 
 ```python
 nxbins, nybins = 10, 9
diff --git a/hugo/content/ref/instr/polarized/polarized-spin-flip/index.md b/hugo/content/ref/instr/polarized/polarized-spin-flip/index.md
index d420b5551a413927b3d420c40dfd22b5877a62bd..a615031113c1dc644689edf3afaba4e0fce34b6e 100644
--- a/hugo/content/ref/instr/polarized/polarized-spin-flip/index.md
+++ b/hugo/content/ref/instr/polarized/polarized-spin-flip/index.md
@@ -28,7 +28,7 @@ results_mp = run_simulation(R3(0, -1, 0),
                             R3(0,  1, 0))
 ```
 
-Running the full script, that is given below, we obtain the following simulation result:
+Running the full script that is given below, we obtain the following simulation result:
 
 {{< galleryscg >}}
 {{< figscg src="/img/auto/specular/PolarizedSpinFlip.png" width="650px" caption="Reflectivity">}}
diff --git a/hugo/content/ref/sample/interference/grating/lattice1d/index.md b/hugo/content/ref/sample/interference/grating/lattice1d/index.md
index 566e7ed613089d45661109cc3528aedd7b6e1d50..b718941ef2dddb9d3947de8e29d4e0471b000ed9 100644
--- a/hugo/content/ref/sample/interference/grating/lattice1d/index.md
+++ b/hugo/content/ref/sample/interference/grating/lattice1d/index.md
@@ -10,7 +10,7 @@ In this example we simulate the scattering from infinite 1D repetition of rectan
 * By-default, the axis of the one-dimensional lattice coincides with the $x$-axis of the reference cartesian frame, so it coinsides with the beam direction.
 * Long boxes are placed along a one-dimensional lattice on top of substrate, the lattice_length parameter corresponds to the grating period.
 * The size of boxes is initially chosen to form a grating which is perpendicular to the beam (long side of the box is along $y$-axis).
-* Please keep in mind, that `length`, `width`, `height` in the `Box(length, width, height)` constructor correspond to the directions in the $x,y,z$ axes, in that order, so to achieve the desired setup we use the values: `length`= $10$ nm, `width`= $10000$ nm, `height`= $10$ nm.
+* Keep in mind that `length`, `width`, `height` in the `Box(length, width, height)` constructor correspond to the directions in the $x,y,z$ axes, in that order, so to achieve the desired setup we use the values: `length`= $10$ nm, `width`= $10000$ nm, `height`= $10$ nm.
 * The whole grating is rotated at the end by an angle of $45^{\circ}$ with respect to the beam axis. This is achieved by rotating _both_ the 1D lattice and the long boxes (see lines 25 and 34).
 * To avoid the problem of rapidly oscillating form factors of long boxes (see [this example](/ref/sim/setup/options/mc) for more details), the simulation is performed in monte carlo integration mode.
 
diff --git a/hugo/content/ref/sample/interference/lattice2d/_index.md b/hugo/content/ref/sample/interference/lattice2d/_index.md
index 2c5aeb74fe3a26cd868c80c5bf68f0f7df459299..36e6e258c114a7634162adc0ef0100e3a664d1dd 100644
--- a/hugo/content/ref/sample/interference/lattice2d/_index.md
+++ b/hugo/content/ref/sample/interference/lattice2d/_index.md
@@ -92,12 +92,12 @@ f.setDecayFunction(FTDecayFunction2DCauchy(1000*nm, 1000*nm))
 ```
 
 {{< alert theme="info" >}}
- Typical values for the decay lengths are much larger than the lattice length. Please also note, that small decay lengths (of the order of lattice lengths or smaller) lead to a significant increase of simulation time.
+ Typical values for the decay lengths are much larger than the lattice length. Also note that small decay lengths (of the order of lattice lengths or smaller) lead to a significant increase of simulation time.
 {{< /alert >}}
 
 ### Particle density
 
-The computational kernel provides an automatic calculation of particle densities using the parameters of the 2D lattice. This means, that the user's setting of the particle density via the `ParticleLayout.setParticleDensity()` method (which is a required step in the case of a 1D interference function and radial paracrystal initialization) is ignored.
+The computational kernel provides an automatic calculation of particle densities using the parameters of the 2D lattice. This means that the user's setting of the particle density via the `ParticleLayout.setParticleDensity()` method (which is a required step in the case of a 1D interference function and radial paracrystal initialization) is ignored.
 
 ### Complete example
 
diff --git a/hugo/content/ref/sample/interference/para2d/index.md b/hugo/content/ref/sample/interference/para2d/index.md
index fef593c388d25d1377bbbfe655f73d8701b45504..6ecd19b129783372c77f640ef749a6669a11d19d 100644
--- a/hugo/content/ref/sample/interference/para2d/index.md
+++ b/hugo/content/ref/sample/interference/para2d/index.md
@@ -125,7 +125,7 @@ Interference2DLattice.createHexagonal(lattice_constant, damping_length=0, domain
 
 ### Particle density
 
-The computational kernel provides an automatic calculation of particle densities using the parameters of the 2D lattice. This means, that the user's settings of particle densities via the `ParticleLayout.setParticleDensity()` method (which is a required step in the case of a radial paracrystal interference  function) is ignored.
+The computational kernel provides an automatic calculation of particle densities using the parameters of the 2D lattice. This means that the user's settings of particle densities via the `ParticleLayout.setParticleDensity()` method (which is a required step in the case of a radial paracrystal interference  function) is ignored.
 Averaging over lattice rotation angle.
 
 The paracrystal 2D interference function can be averaged over all azimuthal angles $\xi$ using the `setIntegrationOverXi(True)` method. In this case the initial lattice rotation angle $\xi$, if set, will be ingnored and numeric integration will be performed for $\xi$ in the range 0, 360 degrees. Averaging provides a convenient way of getting an isotropic interference function for the cost of bigger computational time.
diff --git a/hugo/content/ref/sample/roughness/specular/index.md b/hugo/content/ref/sample/roughness/specular/index.md
index 75aaafc92dee3eb3ee44b30c6f3598f6f722b979..210423cf34a0001468117537abe8826f7cbcf5c4 100644
--- a/hugo/content/ref/sample/roughness/specular/index.md
+++ b/hugo/content/ref/sample/roughness/specular/index.md
@@ -24,7 +24,7 @@ one can notice up to two orders of magnitude attenuation of the reflected signal
 the roughness of the sample.
 
 {{< notice note >}}
-Please note that other roughness characteristics (like Hurst parameter or lateral and cross correlation lengths)
+Note that other roughness characteristics (like Hurst parameter or lateral and cross correlation lengths)
 previously described in [example on correlated roughness](/ref/sample/roughness)
 do not affect the result of the simulation. The computation model takes into account only the
 rms-deviation from the mean surface position.
diff --git a/hugo/content/ref/sim/setup/options/mc/index.md b/hugo/content/ref/sim/setup/options/mc/index.md
index 044de364e642e4589b6f8cc5d291cc453c9bcd46..e344b4f7473a0e7a7bb506e767128aa3288d7a0f 100644
--- a/hugo/content/ref/sim/setup/options/mc/index.md
+++ b/hugo/content/ref/sim/setup/options/mc/index.md
@@ -17,7 +17,7 @@ where `n` is the number of scattering intensity evaluations per pixel.
 
 #### Usage example: large qr
 
-This example demonstrates, that for large particles (~$1000$ nm) the contribution to the scattered intensity from the form factor oscillates rapidly within one detector bin and analytical calculations (performed for the bin center) give completely a wrong intensity pattern. In this case Monte-Carlo integrations over detector bin should be used.
+This example demonstrates that for large particles (~$1000$ nm) the contribution to the scattered intensity from the form factor oscillates rapidly within one detector bin and analytical calculations (performed for the bin center) give completely a wrong intensity pattern. In this case Monte-Carlo integrations over detector bin should be used.
 
 The simulation generates four plots using different sizes of the particles, (radius $=10$ nm, height $=20$ nm) or (radius $=1$ $\mu$m, height $=2$ $\mu$m), and different calculation methods: analytical calculations or Monte-Carlo integration. The other parameters are identical: