From ba2ff3a3de394a4c5c9a72ed7314ad3bb52f6a53 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Mon, 11 Nov 2019 11:51:29 +0000 Subject: [PATCH] docs: Add missing word. (#1643) Makes the flow of reading nicer. --- docs/guide/modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/modules.md b/docs/guide/modules.md index 8715ce748..5630c8f6e 100644 --- a/docs/guide/modules.md +++ b/docs/guide/modules.md @@ -301,7 +301,7 @@ You can also remove a dynamically registered module with `store.unregisterModule It may be likely that you want to preserve the previous state when registering a new module, such as preserving state from a Server Side Rendered app. You can achieve this with `preserveState` option: `store.registerModule('a', module, { preserveState: true })` -When you set `preserveState: true`, the module is registered, actions, mutations and getters are added to the store, but the state not. It's assumed that your store state already contains state for that module and you don't want to overwrite it. +When you set `preserveState: true`, the module is registered, actions, mutations and getters are added to the store, but the state is not. It's assumed that your store state already contains state for that module and you don't want to overwrite it. ### Module Reuse