Minor copy updates

Author: ardalis

src/Services/Basket/Basket.API/README.md

@@ -3,17 +3,17 @@ Sample reference containerized application, cross-platform and microservices arc
 Powered by Microsoft
 
 #Overview
-This sample runs a microservices oriented application and a .net core Mvc application that consumes this services. You can find more information about how to set up docker in your machine in the global directory solution.
+This sample runs a microservices oriented application and an ASP.NET Core MVC application that consumes this services. You can find more information about how to set up docker in your machine in the global directory solution.
 
 #Deploy
-In the global directory you will find the scripts needed to run and deploy the demo into your local docker infraestructure.
+In the global directory you will find the scripts needed to run and deploy the demo into your local docker infrastructure.
 
-- <a href='build-image-services-basket.ps1'>build-image-services-basket.ps1</a>  <b>Build .net applications and docker images</b>: This power shell script that you will find in the <u>root directory of the solution</u> is the responsible of building .net applications and package in a pub folder and use docker commands to build the images needed to run the previously packaged .net applications.
+- <a href='build-image-services-basket.ps1'>build-image-services-basket.ps1</a>  <b>Build .net applications and docker images</b>: This PowerShell script that you will find in the <u>root directory of the solution</u> is responsible for building .NET applications and package in a pub folder and use docker commands to build the images needed to run the previously packaged .NET applications.
 
-- <b>Compose containers in your docker local VM</b>: Finally you have to open your favourite command tool pointing to the <u>root directory of this project</u> where docker-compose.yml file is located and run the command  `docker-compose up`
+- <b>Compose containers in your docker local VM</b>: Finally you have to open your favorite command tool pointing to the <u>root directory of this project</u> where docker-compose.yml file is located and run the command  `docker-compose up`
 
 #Run
-Once the deploy process of docker-compose finishes you have to be able to access the services in this urls:
+Once the deploy process of docker-compose finishes you have to be able to access the services in these urls:
 - Basket service: http://localhost:5103
 - Identity service: http://localhost:5105
 - Basket data (Redis): listening in localhost:6379

src/Services/Basket/Basket.API/Startup.cs

@@ -37,9 +37,9 @@ public void ConfigureServices(IServiceCollection services)
             services.AddMvc();
             services.Configure<BasketSettings>(Configuration);
 
-            //By connection here we are making sure that our service
+            //By connecting here we are making sure that our service
             //cannot start until redis is ready. This might slow down startup,
-            //but given that it is there is a delay on resolving the ip address
+            //but given that there is a delay on resolving the ip address
             //and then creating the connection it seems reasonable to move
             //that cost to startup instead of having the first request pay the
             //penalty.