Update part9d.md and part9e.md

Author: marcbambalan

src/content/9/en/part9d.md

@@ -881,7 +881,7 @@ const App = () => {
 
 ```
 
-When we hover over the *response.data* we see that is has the type *any*
+When we hover over the *response.data* we see that it has the type *any*
 
 ![vscode response.data showing the any type](../../images/9/69new.png)
 

src/content/9/en/part9e.md

@@ -48,7 +48,7 @@ The folder structure looks as follows:
 
 Besides the component *App* a directory for services, there are currently three main components: *AddPatientModal* and *PatientListPage* which are both defined in a directory, and a component *HealthRatingBar* defined in a file. If a component has some subcomponents not used elsewhere in the app, it might be a good idea to define the component and its subcomponents in a directory. For example now the AddPatientModal is defined in the file *components/AddPatientModal/index.tsx* and its subcomponent *AddPatientForm* in its own file under the same directory.
 
-There is nothing very surprising in the code. The state and communication with the backend are implemented with *useState* hook and Axios, similar to the notes app in the previous section. [Material UI](/en/part7/more_about_styles#material-ui) is used to style the app and the navigation structure is implementer with [React Router](/en/part7/react_router), both familiar to us from part 7 of the course.
+There is nothing very surprising in the code. The state and communication with the backend are implemented with *useState* hook and Axios, similar to the notes app in the previous section. [Material UI](/en/part7/more_about_styles#material-ui) is used to style the app and the navigation structure is implemented with [React Router](/en/part7/react_router), both familiar to us from part 7 of the course.
 
 From typing point of view, there are a couple of interesting things. Component *App* passes the function *setPatients* as a prop to the component *PatientListPage*: