Merge pull request #755 from SimonMarquis/patch-4

Mention core-designsystem module in the modularization journey docs

Author: dturner

docs/ModularizationLearningJourney.md

@@ -159,13 +159,21 @@ Using the above modularization strategy, the Now in Android app has the followin
    <td><code>TopicsRepository</code><br>
    </td>
   </tr>
+  <tr>
+   <td><code>core:designsystem</code>
+   </td>
+   <td>Design system which includes Core UI components (many of which are customized Material 3 components), app theme and icons. The design system can be viewed by running the `app-nia-catalog` run configuration. 
+   </td>
+   <td>
+   <code>NiaIcons</code>    <code>NiaButton</code>    <code>NiaTheme</code> 
+   </td>
+  </tr>
   <tr>
    <td><code>core:ui</code>
    </td>
-   <td>UI components, composables and resources, such as icons, used by different features.
+   <td>Composite UI components and resources used by feature modules, such as the news feed. Unlike the `designsystem` module, it is dependent on the data layer since it renders models, like news resources. 
    </td>
-   <td><code>NiaIcons</code><br>
-   <code>NewsResourceCardExpanded</code>
+   <td> <code>NewsFeed</code> <code>NewsResourceCardExpanded</code>
    </td>
   </tr>
   <tr>