From a5f0b2a2512a40f5f12648e804cfffd56cd7f2db Mon Sep 17 00:00:00 2001 From: Brian Vaughn Date: Fri, 8 Jun 2018 10:32:45 -0400 Subject: [PATCH] Typo fix --- content/blog/2018-06-07-you-probably-dont-need-derived-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2018-06-07-you-probably-dont-need-derived-state.md b/content/blog/2018-06-07-you-probably-dont-need-derived-state.md index 3e0c60066..4932e7060 100644 --- a/content/blog/2018-06-07-you-probably-dont-need-derived-state.md +++ b/content/blog/2018-06-07-you-probably-dont-need-derived-state.md @@ -184,7 +184,7 @@ This also provides the flexibility to only reset parts of our component's intern #### Alternative 2: Reset uncontrolled component with an instance method -More rarely, you may need to reset state even if there's no appropriate ID to use as `key`. One solution is to reset the key to a random value or autoincrementing number each time you want to reset. One other viable alternative is to exposing an instance method to imperatively reset the internal state: +More rarely, you may need to reset state even if there's no appropriate ID to use as `key`. One solution is to reset the key to a random value or autoincrementing number each time you want to reset. One other viable alternative is to expose an instance method to imperatively reset the internal state: ```js class EmailInput extends Component {