diff --git a/README.md b/README.md
index c3680371..f58b60a1 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ We have separate folders for the samples of individual modules:
 
 ## Spring Data Redis
 
-* `example` - Example for basic Sprign Data Redis setup.
+* `example` - Example for basic Spring Data Redis setup.
 * `cluster-sentinel` - Example for Redis cluster and Sentinel support.
 
 ## Spring Data Elasticsearch
diff --git a/jpa/java8/README.md b/jpa/java8/README.md
index f0a18803..741b5f23 100644
--- a/jpa/java8/README.md
+++ b/jpa/java8/README.md
@@ -41,11 +41,11 @@ try (Stream<Customer> customers = repository.streamAllCustomers()) {
 Note how the returned `Stream` has to be used in a try-with-resources clause as the underlying resources have to be closed once we finished iterating over the result.
 
 
-## Support for JDK 8' `CompletableFuture` in `@Asnyc` repository methods
+## Support for JDK 8' `CompletableFuture` in `@Async` repository methods
 
 JPA repositories can now use `CompletableFuture` as return type for query methods for async execution of the query with support for fluent processing.
 
-Note that: Support for `CompletableFuture` in combination with `@Asnyc` is available in Spring Framework 4.2.x.
+Note that: Support for `CompletableFuture` in combination with `@Async` is available in Spring Framework 4.2.x.
 
 ```java
 interface CustomerRepository extends Repository<Customer, Long> {
diff --git a/multi-store/README.md b/multi-store/README.md
index e0d9d962..7875ee65 100644
--- a/multi-store/README.md
+++ b/multi-store/README.md
@@ -15,4 +15,4 @@ If you run `ApplicationConfigurationTest` you should see the following output:
 … DEBUG … - Spring Data MongoDB - Registering repository: orderRepository - Interface: example.springdata.multistore.shop.OrderRepository - Factory: org.springframework.data.mongodb.repository.support.MongoRepositoryFactoryBean
 ```
 
-As you can see, Spring Data detects the fact that the application runs on multiple Spring Data modules. This triggers the strict configuration mode in which only repository interfaces will be detected that can be uniquely can be assigned to the module currently scanning. By default this is assignment is detected by inspecting the managed domain type for store specific annotations (e.g. `@Entity` for JPA or `@Document` for MongoDB).  
+As you can see, Spring Data detects the fact that the application runs on multiple Spring Data modules. This triggers the strict configuration mode in which only repository interfaces will be detected that can be uniquely assigned to the module currently scanned. By default this assignment is detected by inspecting the managed domain type for store specific annotations (e.g. `@Entity` for JPA or `@Document` for MongoDB).