From 80adaf1455d4e38297e93769855379ed2aab5d49 Mon Sep 17 00:00:00 2001 From: Jacob Reid Date: Tue, 24 May 2016 16:11:16 -0600 Subject: [PATCH] docs(tutorial/4 - Directory and File Organization): describe your change... --- 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 cc2e152f0b4a..767ab6e65342 100644 --- a/docs/content/tutorial/step_04.ngdoc +++ b/docs/content/tutorial/step_04.ngdoc @@ -109,7 +109,7 @@ Similarly, the accompanying spec file loads the `phonecatApp` module before each that's where our component is registered). Now, imagine that we need a list of phones on another project that we are working on. Thanks to our modular architecture, we don't have to reinvent the wheel; we simply copy the `phone-list/` directory on our other project and add the necessary script -tags in our `index.html` file and we are done, right ? +tags in our `index.html` file and we are done, right? Well, not so fast. The new project doesn't know anything about a `phonecatApp` module. So, we would have to replace all references to `phonecatApp` with the name of this project's main module. As you