diff --git a/docs/en/guides/using-with-vue-router.md b/docs/en/guides/using-with-vue-router.md
index 2a1c8067f..d94be1360 100644
--- a/docs/en/guides/using-with-vue-router.md
+++ b/docs/en/guides/using-with-vue-router.md
@@ -18,7 +18,7 @@ shallow(Component, {
 })
 ```
 
-> **Note:** Installing Vue Router on a localVue also adds `$route` and `$router` as read-only properties. This means you cannot use the `mocks` option to overwrite `$route` or `$router` when mounting a component using a localVue with VueRouter installed.
+> **Note:** Installing Vue Router on a localVue also adds `$route` and `$router` as read-only properties to a localVue. This means you can not use the `mocks` option to overwrite `$route` and `$router` when mounting a component using a localVue with VueRouter installed.
 
 ## Testing components that use `router-link` or `router-view`
 
diff --git a/docs/en/guides/using-with-vuex.md b/docs/en/guides/using-with-vuex.md
index 45771e8da..3c151ff89 100644
--- a/docs/en/guides/using-with-vuex.md
+++ b/docs/en/guides/using-with-vuex.md
@@ -341,6 +341,8 @@ The downside is that when a test breaks, it can be difficult to find where the p
 Let's write a test. When we create a store, we'll use `localVue` to avoid polluting the Vue base constructor. The test creates a store using the store-config.js export:
 
 ```js
+// store-config.spec.js
+
 import mutations from './mutations'
 import getters from './getters'
 
@@ -354,8 +356,6 @@ export default {
 ```
 
 ```js
-// store-config.spec.js
-
 import { createLocalVue } from '@vue/test-utils'
 import Vuex from 'vuex'
 import storeConfig from './store-config'