diff --git a/README.md b/README.md
index 4ace47d2caf5fd8e9af0a5c2a259c13149fb3370..e836c460c112324771db844dddf7496f28f10b9c 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ We are going to create our own GraphQL API on top of this [Rick and Morty API](h
 
 - [ ] 2. Create an Episode type in your schema. Here is the [documentation of the episode endpont](https://rickandmortyapi.com/documentation/#episode-schema).
 
-- [ ] 3. Create a relationship between Episode type in your schema. Here is the [documentation of the episode endpont](https://rickandmortyapi.com/documentation/#episode-schema). Hints
+- [ ] 3. Create a relationship between Episode type in your schema. Please have a look at the [documentation of the episode endpont](https://rickandmortyapi.com/documentation/#episode-schema) to see how to get the episodes of a given character (heads up! we are calling the field in Characters `episodes` but the REST API is calling it `episode`). Hints
 
   - You need to add a Character type in the resolvers object and an episodes field to it. Similar to the Author type and books field in the [documentation](https://www.apollographql.com/docs/apollo-server/essentials/data#resolver-map)
   - You can filter the episodes in our case using the `mapEpisodeUrlToEpisode` defined at the bottom of this file `src/index.js` of this project.