Skip to content

Commit 5dad028

Browse files
authored
Update src/cookbook/gradual-compositionapi-migration.md
1 parent 194b2b4 commit 5dad028

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/cookbook/gradual-compositionapi-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ It is possible to use the Composition API in place of Vuex, and save yourself a
112112

113113
If you're using Vuex, it's very clear exactly what centralized state is being used across the application. In addition, you gain the benefit of using a standardized pattern that comes with officially supported tooling in the DevTools which can make a big difference when it comes to debugging code.
114114

115-
Composition API is very flexible, but you may lose that implicit declaration in communication to fellow maintainers. Our suggestion that if you do use it as a centralized state management store, that you place it in a `stateManagement` folder, or something similarly named, so that responsibilities are clear.
115+
The Composition API is very flexible, but you may lose that implicit declaration in communication to fellow maintainers. Our suggestion is that if you do use it as a centralized state management store, that you place it in a `stateManagement` folder, or something similarly named, so that responsibilities are clear.
116116

117117
## Components
118118

0 commit comments

Comments
 (0)