diff --git a/README.md b/README.md
index da0a42e..9f0e142 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 In an event-driven microservices architecture, the concept of a domain event is central to the behavior of each service. Popular practices such as _CQRS_ (Command Query Responsibility Segregation) in combination with _Event Sourcing_ are becoming more common in applications as microservice architectures continue to rise in popularity.
 
-This reference architecture and sample project demonstrates an end-to-end example of building event-driven microservices that use Spring Boot and Spring Cloud. The project aims to show what an ideal development process might look like for building microservices that handle both HTTP and AMQP protocols for exchanging messages.
+This reference architecture and sample project demonstrate an end-to-end example of building event-driven microservices that use Spring Boot and Spring Cloud. The project aims to show what an ideal development process might look like for building microservices that handle both HTTP and AMQP protocols for exchanging messages.
 
 Demonstrated concepts:
 
@@ -46,7 +46,7 @@ The web role contains a REST API with transactions that requires strong consiste
 
 #### Worker role
 
-The worker role contains an AMQP-based message processor that listens for events generated by the web role and from other microservices. The worker role will be responsible for managing workflows that are eventually consistent. Any transaction the requires complex durable communication between separate microservices will be handled in the worker role.
+The worker role contains an AMQP-based message processor that listens for events generated by the web role and from other microservices. The worker role will be responsible for managing workflows that are eventually consistent. Any transaction requires complex durable communication between separate microservices will be handled in the worker role.
 
 ### Packaging
 
@@ -106,7 +106,7 @@ From the root of the project:
 
 The Spring Cloud Stream applications will be imported and the event streams will be available in the streams section of the data flow server. The load simulator stream module will begin to slowly pump events into the system and you'll be able to see the activity in the analytics section where you can see counters measuring the event load over time.
 
-This project is working off of snapshots, so there may be issued running the data flow server. Please submit a issue or a pull request with a fix. (Thanks!)
+This project is working off of snapshots, so there may be issued running the data flow server. Please submit an issue or a pull request with a fix. (Thanks!)
 
 #### Serverless Functions