Update 2024-10-14-application-form-advice.md

Typos, thanks Tom J

content/post/2024-10-14-application-form-advice.md

@@ -18,6 +18,6 @@ A really good application form will address very clearly all of the essential cr
 
 Write enough. Honestly, some of the forms were kind of short. It's not enough to say "I'm good at something, I did it such and such a time". Flesh it out a bit. You used GitHub. When? How? Whom with? An application that very clearly, with examples, and fleshed out examples, shows experience and knowledge of the essential criteria will be a good application. 
 
-For a truly great application, and one which is more likely to be shortlisted, show some insight into your work that illustrates the elements of the essential criteria. That's what I really want to hear. You used GitHub, at a specific time and place, for a specific purpose, with a specific set of people. What insights did you gain? For example, on Friday the team and I were having a look at GitHub projeccts, we already use Kanban to manage our sprints but we were seeing what GiitHub can add to this process. There's a clear trade off between complexity and power when you're using GitHub to manage projects. You may not have done anything fancy like that. Who merges pull requests? The reviewer of the owner? How do you let people know there are pull requests? What is your git workflow? How big should a commit be? How old/ behind main is it OK for a branch to be? 
+For a truly great application, and one which is more likely to be shortlisted, show some insight into your work that illustrates the elements of the essential criteria. That's what I really want to hear. You used GitHub, at a specific time and place, for a specific purpose, with a specific set of people. What insights did you gain? For example, on Friday the team and I were having a look at GitHub projects, we already use Kanban to manage our sprints but we were seeing what GitHub can add to this process. There's a clear trade off between complexity and power when you're using GitHub to manage projects. You may not have done anything fancy like that. Who merges pull requests? The reviewer of the owner? How do you let people know there are pull requests? What is your git workflow? How big should a commit be? How old/ behind main is it OK for a branch to be? 
 
-Talk about the way you code. Sometimes when I'm coding, especially dashboards, I find it useful to move away from the screen and use a pen and paper for a bit. Do you refactor early, late? Does your work environment make it hard to get feedback so you end up making three of everything? Bring out the learning you have from your work around each of the essential criteria, with clear and detailed examples, that's the application that brings you to life as a data scientist and will maximise your chances of getting an interview.
+Talk about the way you code. Sometimes when I'm coding, especially dashboards, I find it useful to move away from the screen and use a pen and paper for a bit. Do you refactor early, late? Does your work environment make it hard to get feedback so you end up making three of everything? Bring out the learning you have from your work around each of the essential criteria, with clear and detailed examples, that's the application that brings you to life as a data scientist and will maximise your chances of getting an interview.