diff --git a/docs/guide/unit-testing/readme.md b/docs/guide/unit-testing/readme.md
index 95ff259..7ec635a 100644
--- a/docs/guide/unit-testing/readme.md
+++ b/docs/guide/unit-testing/readme.md
@@ -34,7 +34,7 @@
 1. Open the Chrome browser and go to `chrome://inspect`
 
 ### Fixing failed snapshot tests
-The `test:update` script will update snapshot tests. If the UI has changed and the snapshot tests are failing, after manually verifying the UI changes, run the update script to update the snapshots. Running `test:updat`e can be dangerous, as it will update all snapshot tests.
+The `test:update` script will update snapshot tests. If the UI has changed and the snapshot tests are failing, after manually verifying the UI changes, run the update script to update the snapshots. Running `test:update` can be dangerous, as it will update all snapshot tests.
 
 It is critical to verify all snapshot tests before running the update script. The easiest way is to run the unit test in watch mode, `npm run test:unit -- --watch` and verify each snapshot.
 
@@ -103,7 +103,7 @@
 ### Testing Store Instance
 - Uses mutations and actions as inputs
 - State is the output
-- Requires the use of `localVue` when creating the store to avoide leaky tests
+- Requires the use of `localVue` when creating the store to avoid leaky tests
 
 #### Pros
 - Avoids mocking and brittle tests