typos

Author: skramm

docs/homog2d_algorithms.md

@@ -26,7 +26,7 @@ Here, their sum is obviously higher than the segment length, thus there is no in
 
 For Segment/Segment, the checking is done twice, once for each segment.
 
-A threshold is used to compare theses distances, the computation is actually (pseudocode):
+A threshold is used to compare these distances, the computation is actually (pseudocode):
 ```
 if( | d(ac) + d(bc) - segment_length | < thr::nullDistance() )
 	... then intersection point

docs/homog2d_devinfo.md

@@ -219,7 +219,7 @@ Two Yaml workflow files are present.
 - one [msvc.yml](.github/workflows/msvc.yml) is only dedicated to checking that the Microsoft C++ compiler is able to build the software.
 - the [other (c-cpp.yml)](.github/workflows/c-cpp.yml) runs the unit test file using both GCC and Clang, on two different platforms (Ubuntu 22 and Ubuntu 24).
 
-If both of theses workflows succeed, it will generate the badge on front page.
+If both of these workflows succeed, it will generate the badge on front page.
 
 Once the test app has been build (with `$ make test`), you can run a single test with:
 ```

docs/homog2d_manual.md

@@ -586,7 +586,6 @@ The only constraint is that no coordinate can be equal.
 The function will throw if it is not enforced.
 
 You can also build the rectangle by giving the 4 coordinates x1,y1 and x2,y2.
-The only constraint is that they must be all of the same type (no int/float/double mix).
 ```C++
 FRect r1( x1, y1, x2, y2 );
 ```

homog2d.hpp

@@ -2676,9 +2676,9 @@ class FRect_: public detail::Common<FPT>
 		);
 	}
 
-/// Constructor from x1, y1, x2, y2 (need to be all the same type)
-	template<typename T>
-	FRect_( T x1, T y1, T x2, T y2 )
+/// Constructor from x1, y1, x2, y2
+	template<typename T1,typename T2,typename T3,typename T4>
+	FRect_( T1 x1, T2 y1, T3 x2, T4 y2 )
 	{
 		HOMOG2D_CHECK_IS_NUMBER(T);
 		set( Point2d_<FPT>(x1,y1), Point2d_<FPT>(x2,y2) );

misc/homog2d_test.cpp

@@ -540,7 +540,7 @@ TEST_CASE( "types testing 3", "[test-types-3]" )
 		EllipseD elld4 = elll;
 
 /**
-The goal of theses is to make sure that the conversion (float to double, ...)
+The goal of these is to make sure that the conversion (float to double, ...)
 does not trigger a build failure.
 The checking is only there to avoid a warning about "unused variable".
 \todo Once we switch to C++17, we can remove the checking and use:
@@ -1240,7 +1240,7 @@ TEST_CASE( "getCorrectPoints", "[gcpts]" )
 /////           ISINSIDE TESTS                       /////
 //////////////////////////////////////////////////////////////
 
-// this test only makes sure that all theses situations compile
+// this test only makes sure that all these situations compile
 TEST_CASE( "IsInside - manual", "[IsInside_man]" )
 {
 	Point2d pt1(10,10),pt2(10,10);