fix typo - 'theses' to 'these'

Author: apdsrocha

content/internships/intern-guide/contents.lr

@@ -27,7 +27,7 @@ Once the internship starts, here's what we expect of you:
 * Work 30-40 hours per week (or agree on a different plan with your mentor ahead of time).
 * Push code to GitHub frequently. Commit early and often.
 * Be available on Slack whenever you are working and post at least once a (work)day to talk about what you're working on that day.
-* Write a short update on your work **every two weeks** and post it to the CC technical blog ([instructions are here](/community/write-a-blog-post)). To get a sense of how theses posts are written and how the projects evolved, you can read entries done by previous [Outreachy](https://opensource.creativecommons.org/blog/categories/outreachy/) or [Google Summer of Code](https://opensource.creativecommons.org/blog/categories/gsoc/) interns.
+* Write a short update on your work **every two weeks** and post it to the CC technical blog ([instructions are here](/community/write-a-blog-post)). To get a sense of how these posts are written and how the projects evolved, you can read entries done by previous [Outreachy](https://opensource.creativecommons.org/blog/categories/outreachy/) or [Google Summer of Code](https://opensource.creativecommons.org/blog/categories/gsoc/) interns.
 * Attend your weekly check-in with your mentor and any other meetings.
 * Be proactive about asking for help, especially when you're stuck.
 * Ensure that you're on track to delivering your project at the end of the work period. If you're not on track, talk with your mentor to come up with a new plan for the project well before the deadline.