typo: wouldn t -> wouldn't (dotnet#42)

* typo: didn t -> didn't * typo: shouldn t -> shouldn't * Apply suggestions from code review Ignored case on find/replace Co-Authored-By: nschonni <[email protected]>
nwolisa · Mar 26, 2019 · b35d851 · b35d851
1 parent 1e2bae4
commit b35d851
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...rsions-1/contact-manager/iteration-4-make-the-application-loosely-coupled-cs.md b/...rsions-1/contact-manager/iteration-4-make-the-application-loosely-coupled-cs.md
@@ -55,7 +55,7 @@ Imagine, for example, that you decide to change how you implement your data acce
 
 When an application is loosely coupled, on the other hand, you can make changes to one part of an application without touching other parts of an application. For example, you can switch data access technologies without modifying your validation or controller logic.
 
-In this iteration, we take advantage of several software design patterns that enable us to refactor our Contact Manager application into a more loosely coupled application. When we are done, the Contact Manager won't do anything that it didn't do before. However, we'll be able to change the application more easily in the future.
+In this iteration, we take advantage of several software design patterns that enable us to refactor our Contact Manager application into a more loosely coupled application. When we are done, the Contact Manager won t do anything that it didn't do before. However, we'll be able to change the application more easily in the future.
 
 > [!NOTE] 
 > 

diff --git a/...rsions-1/contact-manager/iteration-4-make-the-application-loosely-coupled-vb.md b/...rsions-1/contact-manager/iteration-4-make-the-application-loosely-coupled-vb.md
@@ -55,7 +55,7 @@ Imagine, for example, that you decide to change how you implement your data acce
 
 When an application is loosely coupled, on the other hand, you can make changes to one part of an application without touching other parts of an application. For example, you can switch data access technologies without modifying your validation or controller logic.
 
-In this iteration, we take advantage of several software design patterns that enable us to refactor our Contact Manager application into a more loosely coupled application. When we are done, the Contact Manager won't do anything that it didn't do before. However, we'll be able to change the application more easily in the future.
+In this iteration, we take advantage of several software design patterns that enable us to refactor our Contact Manager application into a more loosely coupled application. When we are done, the Contact Manager won t do anything that it didn't do before. However, we'll be able to change the application more easily in the future.
 
 > [!NOTE] 
 >