fix: correct typos

src/Blog/wwwroot/posts/the-case-against-undefined-recurring-meetings/index.md

@@ -28,7 +28,7 @@ It is funny too because most of us don't ever blink an eye at any of this practi
 
 And from an individual contributor perspective, it isn't just all financial. These practices have real effects on our performance. We aren't designed for rapid context-switching that a calendar fragmented with meetings creates.
 
-Deep work such as writing, coding, designing, analyzing data, or just generally thinking requires long uninterrupted blocks of time. These blocks offer the oppotunity to get into a "flow" state where you are fully immersed in the task at hand and can produce your best work. When that flow is interrupted or prevented from ever happening in the first place because you've got another 10:00 AM meeting, you are not just losing the meeting time. You are losing the time it takes to get into that flow state and the time it takes to recover from being pulled out of it. The estimates I've seen suggest this can be on average 20-30 minutes per interruption.
+Deep work such as writing, coding, designing, analyzing data, or just generally thinking requires long uninterrupted blocks of time. These blocks offer the opportunity to get into a "flow" state where you are fully immersed in the task at hand and can produce your best work. When that flow is interrupted or prevented from ever happening in the first place because you've got another 10:00 AM meeting, you are not just losing the meeting time. You are losing the time it takes to get into that flow state and the time it takes to recover from being pulled out of it. The estimates I've seen suggest this can be on average 20-30 minutes per interruption.
 
 This also speaks to another documented phenomenon that is often referred to as Meeting Recovery Syndrome. I know it sounds made up, but it is a real thing. This is essentially describing the time spent cooling off or ruminating after a frustrating or ineffective meeting. It is characterized by mental fatigue and actual increases in cortisol levels. So again we aren't just paying a financial price for these meetings, we are also paying a real psychological and physiological price as well.
 
@@ -44,9 +44,9 @@ And while I'm sure some will say well "that is why we hire good people and we ha
 
 ## They are not strategic
 
-The most commond defense of URMs is that they are necessary for team cohesion and communication. I mean have you even lived if you haven't listened to someone talk about the need for "alignment" amonst the team? I get it. I really do. But synchronous communication is the most expensive medium possible for status updates and it is far from the only medium for accomplishing them. In my opinion, in most cases it is not even the best way. 
+The most command defense of URMs is that they are necessary for team cohesion and communication. I mean have you even lived if you haven't listened to someone talk about the need for "alignment" amongst the team? I get it. I really do. But synchronous communication is the most expensive medium possible for status updates and it is far from the only medium for accomplishing them. In my opinion, in most cases it is not even the best way.
 
-I mean if one persion is talking and everyone else is listening, you are fundamentally trying to solve a data transfer problem, not a collaboration one and conversations are far from an efficient, effective, or scalable way to do that. Not to mention that round-robin updates just hold the entire room hostage to the speaking speed of the slowest person and the average adult reads must faster than the average adult speaks.
+I mean if one person is talking and everyone else is listening, you are fundamentally trying to solve a data transfer problem, not a collaboration one and conversations are far from an efficient, effective, or scalable way to do that. Not to mention that round-robin updates just hold the entire room hostage to the speaking speed of the slowest person and the average adult reads must faster than the average adult speaks.
 
 The cool thing is a lot of organizations are coming around to this idea. Shopify deleted something like 10,000+ recurring meetings from employee calendars. Basecamp has a company policy of no meetings. GitLab prioritizes asynchronous communication and has a lot of great resources on how to do that effectively. And there are a lot of other companies that are trying to be more intentional about how they use meetings and when they use them. So I think we are starting to see a shift in the culture around meetings and I hope that trend continues.