From 6985d9b7f0ff2bd443f771ea8fdad194aa1f1260 Mon Sep 17 00:00:00 2001
From: David Barnes <dbarnes@kvcc.edu>
Date: Mon, 7 Sep 2015 22:39:35 -0400
Subject: [PATCH] Fix spelling mistake in the README.

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f6fee3b..b1b047e 100644
--- a/README.md
+++ b/README.md
@@ -36,7 +36,7 @@ Solution Requirements:
 * At least one method/function. (The main method is not included in this count)
 
 ### Notes
-Even though you are free to write this however you would like within the constraints layed out, try to follow the single responsibility principle. I would suggest that you should attempt to make the User Interface handle the UI, the WineItem and WineItemCollection handle representing the data, CSVProcessor handle obtaining the data, and the Main handle orcastrating all of it.
+Even though you are free to write this however you would like within the constraints layed out, try to follow the single responsibility principle. I would suggest that you should attempt to make the User Interface handle the UI, the WineItem and WineItemCollection handle representing the data, CSVProcessor handle obtaining the data, and the Main handle orchestrating all of it.
 
 Data that needs to move from one class to another should do so using primitive types such as int, string, char, double as much as possible. This can be ignored for classes that are obviously related such as WineItem and WineItemCollection. The goal is to future proof the program. Think of what if cases such as the following:
 * What if we wanted to change out the User Interface with a different one? How much work would need to be done to fix it?
-- 
GitLab