From ba77b5918f580475f4148ddab16837073da10ccc Mon Sep 17 00:00:00 2001 From: David Joos Date: Mon, 11 Feb 2013 09:55:29 +0000 Subject: [PATCH] Fixed typo: it > is --- pages/Design-Patterns.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/Design-Patterns.md b/pages/Design-Patterns.md index d57b79b..3f510ac 100644 --- a/pages/Design-Patterns.md +++ b/pages/Design-Patterns.md @@ -119,7 +119,7 @@ and gives you a central place to hook in code that should be run for every reque ## Model-View-Controller The model-view-controller (MVC) pattern and its relatives HMVC and MVVM let you break up code into logical objects that -serve very specific purposes. Models serve as a data access layer where data it fetched and returned in formats usable +serve very specific purposes. Models serve as a data access layer where data is fetched and returned in formats usable throughout your application. Controllers handle the request, process the data returned from models and load views to send in the response. And views are display templates (markup, xml, etc) that are sent in the response to the web browser.