Fix typos in documentations.

Fix typos in READMEs, javadoc, comments and code.

Original pull request #642

mongodb/example/src/main/java/example/springdata/mongodb/customer/CustomerRepository.java

@@ -42,7 +42,7 @@ public interface CustomerRepository extends CrudRepository<Customer, String> {
 	List<Customer> findByLastname(String lastname, Sort sort);
 
 	/**
-	 * Show case for a repository query using geo-spatial functionality.
+	 * Showcase for a repository query using geospatial functionality.
 	 *
 	 * @param point
 	 * @param distance

mongodb/example/src/main/java/example/springdata/mongodb/immutable/ApplicationConfiguration.java

@@ -45,7 +45,7 @@ class ApplicationConfiguration {
 
 			var randomNumber = ThreadLocalRandom.current().nextInt(1, 100);
 
-			// withRandomNumber is a so called wither method returning a new instance of the entity with a new value assigned
+			// withRandomNumber is a so-called wither method returning a new instance of the entity with a new value assigned
 			return immutablePerson.withRandomNumber(randomNumber);
 		};
 	}

mongodb/example/src/test/java/example/springdata/mongodb/customer/CustomerRepositoryIntegrationTest.java

@@ -108,7 +108,7 @@ class CustomerRepositoryIntegrationTest {
 	}
 
 	/**
-	 * Test case to show the usage of the geo-spatial APIs to lookup people within a given distance of a reference point.
+	 * Test case to show the usage of the geospatial APIs to lookup people within a given distance of a reference point.
 	 */
 	@Test
 	void exposesGeoSpatialFunctionality() {

mongodb/fluent-api/README.md

@@ -31,7 +31,7 @@ mongoOps.query(SWCharacter.class)
 
 ```
 
-Different stages in the command essembly process allow to seamlessly switch to different API paths. Using `near` instead of `matching` switches to the path for geo queries requireing the presence of a `NearQuery` while altering the command result type from `List` to `GeoResults` and limiting terminating operations to just `all()`.
+Different stages in the command assembly process allow to seamlessly switch to different API paths. Using `near` instead of `matching` switches to the path for geo queries requiring the presence of a `NearQuery` while altering the command result type from `List` to `GeoResults` and limiting terminating operations to just `all()`.
 
 ```java
 

mongodb/linking/src/test/java/example/springdata/mongodb/linking/docref/jpastyle/JpaStyleDocRefTests.java

@@ -51,7 +51,7 @@ public class JpaStyleDocRefTests {
 	@Autowired MongoOperations operations;
 
 	/**
-	 * Load linked documents where where the actual reference is stored in the obverse side of the association.
+	 * Load linked documents where the actual reference is stored in the obverse side of the association.
 	 */
 	@Test
 	void saveAndLoadJpaStyleRelation() {
@@ -63,12 +63,12 @@ public class JpaStyleDocRefTests {
 		Employee employee1 = new Employee("greedo-tetsu-jr", "greedo");
 		employee1.setManagerId(manager.getId()); // establish the link to the manager document
 		operations.save(employee1);
-		// no need to update he manager document after save of employee
+		// no need to update the manager document after save of employee
 
 		Employee employee2 = new Employee("boba-fett", "boba");
 		employee2.setManagerId(manager.getId()); // establish the link to the manager document
 		operations.save(employee2);
-		// no need to update he manager document after save of employee
+		// no need to update the manager document after save of employee
 
 		operations.execute(Manager.class, collection -> {
 

mongodb/linking/src/test/java/example/springdata/mongodb/linking/docref/query/QueryDocRefTests.java

@@ -54,7 +54,7 @@ public class QueryDocRefTests {
 	@Autowired MongoOperations operations;
 
 	/**
-	 * Load linked documents where where the reference is stored on the inverse and evaluated against a non id property on
+	 * Load linked documents where the reference is stored on the inverse and evaluated against a non id property on
 	 * the obverse side of the association.
 	 */
 	@Test

mongodb/linking/src/test/java/example/springdata/mongodb/linking/docref/simple/SimpleDocRefTests.java

@@ -54,7 +54,7 @@ public class SimpleDocRefTests {
 	@Autowired MongoOperations operations;
 
 	/**
-	 * Load linked documents where where the reference is stored on the inverse and evaluated against the id property on
+	 * Load linked documents where the reference is stored on the inverse and evaluated against the id property on
 	 * the obverse side of the association.
 	 */
 	@Test

mongodb/query-by-example/src/main/java/example/springdata/mongodb/querybyexample/ContactRepository.java

@@ -20,7 +20,7 @@ import org.springframework.data.repository.CrudRepository;
 import org.springframework.data.repository.query.QueryByExampleExecutor;
 
 /**
- * Repository interface for {@link Contact} and sub-types.
+ * Repository interface for {@link Contact} and subtypes.
  *
  * @author Oliver Gierke
  */

mongodb/schema-validation/README.md

@@ -59,7 +59,7 @@ MongoJsonSchema schema = MongoJsonSchema.builder() //
     ).build();
 ```
 
-The schema can be used for various funcitionality: Set up `Document` validation for a collection:
+The schema can be used for various functionality: Set up `Document` validation for a collection:
 
 ```java
 template.createCollection(Jedi.class, CollectionOptions.empty().validator(Validator.schema(schema)));

mongodb/text-search/src/test/java/example/springdata/mongodb/textsearch/TextSearchRepositoryTests.java

@@ -55,7 +55,7 @@ class TextSearchRepositoryTests {
 
 	/**
 	 * Show how to do simple matching. <br />
-	 * Note that text search is case insensitive and will also find entries like {@literal releases}.
+	 * Note that text search is case-insensitive and will also find entries like {@literal releases}.
 	 */
 	@Test
 	void findAllBlogPostsWithRelease() {

mongodb/text-search/src/test/java/example/springdata/mongodb/textsearch/TextSearchTemplateTests.java

@@ -53,7 +53,7 @@ class TextSearchTemplateTests {
 	@Autowired MongoOperations operations;
 
 	/**
-	 * Show how to do simple matching. Note that text search is case insensitive and will also find entries like
+	 * Show how to do simple matching. Note that text search is case-insensitive and will also find entries like
 	 * {@literal releases}.
 	 */
 	@Test