A few word spelling corrections

content/module-reference/processing-modules/demosaic.md

@@ -70,7 +70,7 @@ method
 edge threshold (_PPG_ only)
 : The threshold for an additional median pass. Defaults to “0” which disables median filtering.
 
-lmmse refine (_LMMSE_ only)
+LMMSE refine (_LMMSE_ only)
 : Refinement steps for use with the LMMSE demosaic algorithm. Median steps average the output. Refinement steps add some recalculation of red and blue channels. While the refinement options work well for luma noise, they may decrease quality on images with heavy chroma noise.
 
 color smoothing

content/module-reference/processing-modules/diffuse.md

@@ -211,4 +211,4 @@ It should be noted that global contrast (using simple tone curves or black/white
 
 Part of the aging process is a loss of eyesight. The amount of sharpening that people over 50 find pleasing may not be the same as for people in their 20s. It is worth considering sharpening to obtain a _plausible_ result (matching your everyday perception) rather than a _pleasing_ result (that may look good only to people with the same eyesight as yours).
 
-Finally, assessing the sharpness of images zoomed to 1:1 (100%) or more is a foolish task. In museums, exhibitions and even on screen, the general audience looks at images as a whole, not with a magnifying glass. Moreover, in most practical uses, photographs rarely exceed a resolution of 3000×2000 pixels (roughly a 300 DPI print at A4/letter dimensions) which, for 24 Mpx sensors, means downscaling by a factor of 4. When examining a 24 Mpx file at 1:1, you are actually looking at an image that will never exist. Sharpening at pixel level, in this context, is a waste of time and CPU cycles.
+Finally, assessing the sharpness of images zoomed to 1:1 (100%) or more is a foolish task. In museums, exhibitions and even on screen, the general audience looks at images as a whole, not with a magnifying glass. Moreover, in most practical uses, photographs rarely exceed a resolution of 3000×2000 pixels (roughly a 300 DPI print at A4/Letter dimensions) which, for 24 megapixel sensors, means downscaling by a factor of 4. When examining a 24 megapixel file at 1:1, you are actually looking at an image that will never exist. Sharpening at pixel level, in this context, is a waste of time and CPU cycles.

content/special-topics/opencl/background.md

@@ -6,7 +6,7 @@ draft: false
 author: "people"
 ---
 
-Processing high resolution images is a demanding task requiring a modern computer. In terms of both memory and CPU power, getting the best out of a typical 15, 20 or 25 Megapixel image can quickly take your computer to its limits.
+Processing high resolution images is a demanding task requiring a modern computer. In terms of both memory and CPU power, getting the best out of a typical 15, 20 or 25 megapixel image can quickly take your computer to its limits.
 
 darktable's requirements are no exception. All calculations are performed on 4 x 32bit floating point numbers. This is slower than “ordinary” 8 or 16 bit integer algebra, but eliminates all problems of tonal breaks or loss of information.
 

content/special-topics/opencl/problems-solutions.md

@@ -26,6 +26,6 @@ Here are a few cases that have been observed in the past:
 
 - darktable fails to compile its OpenCL source files at run-time. In this case you will see a number of error messages looking like typical compiler errors. This could indicate an incompatibility between your OpenCL implementation and darktable's interpretation of the standard. In that case please raise an issue on [github](https://github.com/darktable-org/darktable/issues/new/choose) and we will try to assist. Please also report if you see significant differences between CPU and GPU processing of an image.
 
-- you have installed a number of OpenCL drivers meant for the same hardware, this will always lead to severe problems and must strictly be avoided. On windows systems you often have the `Microsoft OpenCLon12` driver installed via the `OpenCL Compatibility Pack`. Inspect and check at [preferences > processing > OpenCL](../../preferences-settings/processing#cpu--gpu--memory)
+- you have installed a number of OpenCL drivers meant for the same hardware, this will always lead to severe problems and must strictly be avoided. On Windows systems you often have the `Microsoft OpenCLon12` driver installed via the `OpenCL Compatibility Pack`. Inspect and check at [preferences > processing > OpenCL](../../preferences-settings/processing#cpu--gpu--memory)
 
 - A few emulated-on-CPU implementations of OpenCL also exist, coming as drivers provided by INTEL or AMD. We have observed that they do not provide any speed gain versus the compiler-optimized CPU code. Therefore darktable simply discards these drivers / devices by default.

content/special-topics/opencl/setting-up.md

@@ -42,4 +42,4 @@ ocl-icd
 ocd-icd-devel
 ```
 
-On linux systems you might also want the `clinfo` package giving you a lot of information about your OpenCL system and settings.
+On Linux systems you might also want the `clinfo` package giving you a lot of information about your OpenCL system and settings.