From e2dd2047b54e990fff54ecfb28d873bb340eeeb1 Mon Sep 17 00:00:00 2001 From: Anchor Date: Mon, 2 Feb 2015 19:00:48 -0800 Subject: [PATCH] Fix typo --- en/13.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/13.1.md b/en/13.1.md index 18a1f7d8..b024de93 100644 --- a/en/13.1.md +++ b/en/13.1.md @@ -33,7 +33,7 @@ Figure 13.3 framework data flow 3. If the requested resource has already been cached, the application will bypass the usual execution process and return a response directly to the user's browser. 4. Security detection: The application will filter incoming HTTP requests and any other user submitted data before handing it off to the controller. 5. Controller loads models, core libraries, and any other resources required to process specific requests. The controller is primarily responsible for handling business logic. -6. Output the rendered view layer to be sent to the client web browser. If you turn the cache, the first view is cached for future routine request.Output changes to the view layer by rendering content to be sent to the Web browser. If caching has been enabled, the first view is cached for future requests to the same resource. +6. Output the rendered view to be sent to the client's web browser. If caching has been enabled, the first view is cached for future requests to the same resource. ## Directory structure