From b6ce7fd9ffb1a5608560f7186215d0389a893936 Mon Sep 17 00:00:00 2001 From: GregoryPorter Date: Thu, 29 Sep 2016 16:43:58 +0200 Subject: [PATCH 1/2] Update step_04.ngdoc corrected syntactic error `all controllers is one file` -> `all controllers in one file` --- docs/content/tutorial/step_04.ngdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/tutorial/step_04.ngdoc b/docs/content/tutorial/step_04.ngdoc index a108ce8b2d77..3b8643c92d04 100644 --- a/docs/content/tutorial/step_04.ngdoc +++ b/docs/content/tutorial/step_04.ngdoc @@ -34,7 +34,7 @@ To that end, we will explain why and how we: ## One Feature per File It might be tempting, for the sake of simplicity, to put everything in one file, or have one file -per type; e.g. all controllers is one file, all components in another file, all services in a third +per type; e.g. all controllers in one file, all components in another file, all services in a third file, and so on. This might seem to work well in the beginning, but as our application grows it becomes a burden to maintain. As we add more and more features, our files will get bigger and bigger and it will be From 99a0ce19f5706c61c7d4403d54f876d5f8e1e522 Mon Sep 17 00:00:00 2001 From: GregoryPorter Date: Thu, 29 Sep 2016 16:47:16 +0200 Subject: [PATCH 2/2] Update step_06.ngdoc: incorrect file name `phone-list.compenents.js -> `phone-list.component.js` --- docs/content/tutorial/step_06.ngdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/tutorial/step_06.ngdoc b/docs/content/tutorial/step_06.ngdoc index 239d413ecf33..3e598967c816 100644 --- a/docs/content/tutorial/step_06.ngdoc +++ b/docs/content/tutorial/step_06.ngdoc @@ -80,7 +80,7 @@ manipulation code is necessary! ## Component Controller
-**`app/phone-list/phone-list.components.js`:** +**`app/phone-list/phone-list.component.js`:** ```js angular.