fix(posts): typos in guts and open sourcing posts

Author: photonbit

_posts/2023-01-26-guts-of-startup.md

@@ -13,15 +13,15 @@ After 7 years of hard work, our passion project, our beloved venture, our partne
 Like countless other startups, Tesselo has failed and died. Now that we have reached the end,
 we turn remembering Tesselo into a celebration. We will hold memories of our dear venture joyfully.
 
-The first reason to celebrate the end of Tesselo is the successfuly continuation of the careers of
+The first reason to celebrate the end of Tesselo is the successful continuation of the careers of
 everyone that was involved in the project. We can proudly say that nobody regrets their participation,
 on the contrary. We have seen the growth of everyone while Tesselo was alive, and can witness
 the impact it has on the humans - the Tesseras - that have worked with us over time.
 
 We know that celebrating failure is in fashion and spinned the wrong way can be harmful.
-By no means we wish for anyone to fail, because not every failure must be seen as an oportunity.
+By no means we wish for anyone to fail, because not every failure must be seen as an opportunity.
 But it so happens that Tesselo's failure does not feel like a defeat. We knew when to stop
-and acted decisefully to make a graceful landing. We helped everyone to find new challenges,
+and acted decisively to make a graceful landing. We helped everyone find new challenges,
 and have seen that happen quickly. We did not go bankrupt.
 
 So now that Tesselo is dead, what remains? We have decided do die with honour by cutting

_posts/2023-02-07-open-sourcing-our-team-wisdom.md

@@ -34,7 +34,7 @@ Like this the contributions will become public, but not the interaction that lea
 
 ## Publishing team agreements
 
-Througout our work we have developed interesting documents such as team agreements on how to operate.
+Throughout our work we have developed interesting documents such as team agreements on how to operate.
 These documents live on Bahamut, our shared wiki. The agreements might be relevant for our team members
 in their new contexts, and possibly other teams as well. Publishing the agreements
 will make it easier to re-use them in the future.