jramey
diff --git a/‎README.md
Lines changed: 4 additions & 2 deletions b/‎README.md
Lines changed: 4 additions & 2 deletions
diff --git a/‎assets/modularity-1.png
156 KB b/‎assets/modularity-1.png
156 KB
@@ -2116,20 +2116,22 @@ While this guide explains the *what*, *why* and *how*, I find it helpful to see
 ### Module Dependencies
 ###### [Style [Y165](#style-y165)]
 
-  - The application root module depends on the app specific feature modules, the feature modules have no direct dependencies, the cross-application modules depend on all generic modules.
+  - The application root module depends on the app specific feature modules and any shared or reusable modules.
 
     ![Modularity and Dependencies](https://raw.githubusercontent.com/johnpapa/angularjs-styleguide/master/assets/modularity-1.png)
 
     *Why?*: The main app module contains a quickly identifiable manifest of the application's features. 
 
-    *Why?*: Cross application features become easier to share. The features generally all rely on the same cross application modules, which are consolidated in a single module (`app.core` in the image).
+    *Why?*: Each feature area contains a manifest of what it depends on, so it can be pulled in as a dependency and still work. 
 
     *Why?*: Intra-App features such as shared data services become easy to locate and share from within `app.core` (choose your favorite name for this module).
 
     Note: This is a strategy for consistency. There are many good options here. Choose one that is consistent, follows AngularJS's dependency rules, and is easy to maintain and scale.
 
     > My structures vary slightly between projects but they all follow these guidelines for structure and modularity. The implementation may vary depending on the features and the team. In other words, don't get hung up on an exact like-for-like structure but do justify your structure using consistency, maintainability, and efficiency in mind. 
 
+    > In a small app, you can also consider putting all the shared dependencies in the app module where the feature modules have no direct dependencies. This makes it easier to maintain the smaller application, but makes it harder to reuse modules outside of this application.
+
 **[Back to top](#table-of-contents)**
 
 ## Startup Logic