Merge pull request #27444 from vtjl10:4.x

Fix Typos and Improve Clarity in Documentation #27444

Description:  
This pull request addresses minor typographical errors and improves the clarity of documentation in several markdown files. Specifically:
- Corrected spelling mistakes such as "traslation" to "translation".
- Improved phrasing for better readability and understanding.
- Added references to specific setter methods in the StereoBM documentation for more detailed guidance.

These changes are limited to documentation and do not affect any code functionality.

doc/py_tutorials/py_calib3d/py_depthmap/py_depthmap.markdown

@@ -63,7 +63,7 @@ There are some parameters when you get familiar with StereoBM, and you may need
 - uniqueness_ratio: Another post-filtering step. If the best matching disparity is not sufficiently better than every other disparity in the search range, the pixel is filtered out. You can try tweaking this if texture_threshold and the speckle filtering are still letting through spurious matches.
 - prefilter_size and prefilter_cap: The pre-filtering phase, which normalizes image brightness and enhances texture in preparation for block matching. Normally you should not need to adjust these.
 
-These parameters are set with dedicated setters and getters after the algoritm
+These parameters are set with dedicated setters and getters after the algorithm
 initialization, such as `setTextureThreshold`, `setSpeckleRange`, `setUniquenessRatio`,
 and more. See cv::StereoBM documentation for details.
 

doc/tutorials/gpu/gpu-thrust-interop/gpu_thrust_interop.markdown

@@ -10,7 +10,7 @@ Goal
 ----
 
 Thrust is an extremely powerful library for various cuda accelerated algorithms.  However thrust is designed
-to work with vectors and not pitched matricies.  The following tutorial will discuss wrapping cv::cuda::GpuMat's
+to work with vectors and not pitched matrices.  The following tutorial will discuss wrapping cv::cuda::GpuMat's
 into thrust iterators that can be used with thrust algorithms.
 
 This tutorial should show you how to:

doc/tutorials/objdetect/aruco_faq/aruco_faq.markdown

@@ -165,7 +165,7 @@ for `cv::aruco::Dictionary`. The data member of board classes are public and can
 - Alright, but how can I render a 3d model to create an augmented reality application?
 
 To do so, you will need to use an external rendering engine library, such as OpenGL. The aruco module
-only provides the functionality to obtain the camera pose, i.e. the rotation and traslation vectors,
+only provides the functionality to obtain the camera pose, i.e. the rotation and translation vectors,
 which is necessary to create the augmented reality effect. However, you will need to adapt the rotation
 and traslation vectors from the OpenCV format to the format accepted by your 3d rendering library.
 The original ArUco library contains examples of how to do it for OpenGL and Ogre3D.