From 5cf691496b1f44230c166f2bd75e13a0e843ed24 Mon Sep 17 00:00:00 2001 From: Maxence POUTORD Date: Wed, 8 Mar 2017 14:53:38 +0000 Subject: [PATCH] fix typos --- src/v2/guide/unit-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/v2/guide/unit-testing.md b/src/v2/guide/unit-testing.md index f81917a1fc..80ed38caea 100644 --- a/src/v2/guide/unit-testing.md +++ b/src/v2/guide/unit-testing.md @@ -71,7 +71,7 @@ describe('MyComponent', () => { ## Writing Testable Components -A lot of components' render output are primarily determined by the props they receive. In fact, if a component's render output solely depends on its props, it becomes quite straightforward to test, similar to asserting the return value of a pure function with different arguments. Take an contrived example: +A lot of component's render output are primarily determined by the props they receive. In fact, if a component's render output solely depends on its props, it becomes quite straightforward to test, similar to asserting the return value of a pure function with different arguments. Take a contrived example: ``` html