Skip to content

Commit 5ca1361

Browse files
authored
Merge pull request #2011 from SimonMarquis/patch-5
Fix small typos
2 parents 4677915 + 426058b commit 5ca1361

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/ModularizationLearningJourney.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,14 +70,14 @@ This contains app level and scaffolding classes that bind the rest of the codeba
7070
`MainActivity`, `NiaApp` and app-level controlled navigation. A good example of this is the navigation setup through `NiaNavHost` and the bottom navigation bar setup through `TopLevelDestination`. The `app` module depends on all `feature` modules and required `core` modules.
7171

7272
### Feature modules
73-
These are feature-specific modules that handle a single responsibility in the app. For example, the `ForYou` feature handles all content and UI state for the "ForYou" screen. Feature modules aren't gradle modules themselves, they are split into two submodules:
73+
These are feature-specific modules that handle a single responsibility in the app. For example, the `ForYou` feature handles all content and UI state for the "ForYou" screen. Feature modules aren't Gradle modules themselves, they are split into two submodules:
7474

7575
* `api` - contains navigation keys
7676
* `impl` - contains everything else
7777

7878
This approach allows features to navigate to other features by using the target feature's navigation keys. A feature's `api` and `impl` modules can be used by any app, including test or other flavoured apps. If a class is needed only by one feature module, it should remain within that module. If not, it should be placed into an appropriate `core` module.
7979

80-
A feature's `api` module should not depend on another feature's `api` or `impl` module. A feature's `impl` should only depend on another featur's `api` module. Both submodules should only depend on the `core` modules that they require.
80+
A feature's `api` module should not depend on another feature's `api` or `impl` module. A feature's `impl` should only depend on another feature's `api` module. Both submodules should only depend on the `core` modules that they require.
8181

8282
### Core modules
8383
These are common library modules containing auxiliary code and specific dependencies that

0 commit comments

Comments
 (0)