Merge pull request #3906 from leburgeon/patch-9

Update part9d.md

Author: mluukkai

src/content/9/en/part9d.md

@@ -713,7 +713,7 @@ const App = () => {
 }
 ```
 
-It just works, there are no complaints about types! When we hover over the *event.target.value*, we see that it is indeed a string, just what is the expected parameter of the *setNewNote*:
+It just works, there are no complaints about types! When we hover over the *event.target.value*, we see that it is indeed a string, just what is expected for the parameter of *setNewNote*:
 
 ![vscode showing variable is a string](../../images/9/67new.png)
 
@@ -749,7 +749,7 @@ It does not quite work, there is an Eslint error complaining about implicit any:
 
 ![vscode error event implicitly has any type](../../images/9/68new.png)
 
-TypeScript compiler has now no clue what is the type of the parameter, so that is why the type is the infamous implicit any that we want to [avoid](/en/part9/first_steps_with_type_script#the-horrors-of-any) at all costs. The React TypeScript cheatsheet comes again to rescue, the chapter about
+TypeScript compiler now has no clue what the type of the parameter is, this is why the type is the infamous implicit any that we want to [avoid](/en/part9/first_steps_with_type_script#the-horrors-of-any) at all costs. The React TypeScript cheatsheet comes to the rescue again, the chapter about
 [forms and events](https://react-typescript-cheatsheet.netlify.app/docs/basic/getting-started/forms_and_events) reveals that the right type of event handler is *React.SyntheticEvent*.
 
 The code becomes