grammar fixes.

Author: gavination

blog/2023-09-15-teams-feature-overview/index.mdx

@@ -12,15 +12,15 @@ Our team knew early on that users needed the ability to share machines in the St
 We also needed the Studio to be an effective tool for teams to work together and share context.
 But how do we do that safely, making sure the right eyes were on the right machines?
 And how do we protect against accidental mishaps that have plagued devs since the dawn of the computer?
-Being a distributed dev team ourselves, we’ve shared these same pain points, and decided to build a solution directly in the Studio.
+Being a distributed dev team ourselves, we’ve shared these same pain points and decided to build a solution directly in the Studio.
 Enter [Stately teams](https://stately.ai/docs/teams), our way to provide privacy and safety while allowing effortless collaboration.
 
 <!--truncate-->
 
 ## Why would I need a team?
 
 Great question, and we’re glad you asked!
-While we have the [Discover](https://stately.ai/registry/discover) page, which showcases over 20 thousand(!) community-created machines, we know that statecharts can contain critical details about core algorithms or can have processes that give businesses a competitive edge.
+While we have the [Discover](https://stately.ai/registry/discover) page, which showcases over 20 thousand(!) community-created machines, we know that statecharts can contain critical details about core algorithms or processes that give businesses a competitive edge.
 Many users expressed interest in keeping these types of machines private, and we listened.
 
 ### Sharing machine visualizations with teammates
@@ -41,11 +41,11 @@ Teams is an exclusive feature for [**Pro** and **Enterprise** users](https://sta
 ### Access control
 There are many times when a dev team needs to share their work context with others without granting them full rights to the projects. 
 For example, Lenny in accounting probably shouldn't have access to the company repo, but he could benefit from visually understanding the steps involved in processes and workflows.
-Having different teams with different roles lets us to keep parties informed without added risk. 
+Having different teams with different roles lets us keep parties informed without added risk. 
 Don't trust your PM's trigger finger? Make them a [viewer](https://stately.ai/docs/teams#viewer-role); we promise not to tell. 
 Taking a vacation before new members can be onboarded? 
 Make another teammate an [admin](https://stately.ai/docs/teams#admin-role). 
-[Checkout all our roles and permissions in our docs](https://stately.ai/docs/teams#team-roles). 
+[Check out all our roles and permissions in our docs](https://stately.ai/docs/teams#team-roles). 
 
 ### Sharing conveniently and safely
 
@@ -57,7 +57,7 @@ Inviting users to collaborate on the same private team allows them to share with
 ### A source of what, now?
 
 Simply put, a “source of truth” is a single place where all the information about a project is stored.
-In our case, we wanted to make sure that teams have a single place to view and collaborate on machine visualizations, and that place is a team-based project in the Studio.
+In our case, we wanted to make sure that teams have a single place to view and collaborate on machine visualizations, and that place is a team project in the Studio.
 This prevents confusion and allows for a shared context between all team members. With a proper source of truth configured, we can avoid situations like this:
 
 ![Four files with the filenames: onboardMachine.json, onboardMachine-final.json, onboardMachine-final-final.json, onboardMachine-actual-final-for-real-this-time.json.](/blog/2023-09-15-file-confusion.png)
@@ -66,7 +66,7 @@ This prevents confusion and allows for a shared context between all team members
 
 Ideally, yes, the team’s repository is the single source of truth for all application logic, but not every team member is a developer, nor should they all have access to source code.
 That said, we know teams need to ensure their machines in the Studio are always in lockstep with the rest of their source, so we added the ability to [import machines directly from GitHub](https://stately.ai/docs/import-from-github).
-We’re also working on a full-fledged GitHub Sync feature, allowing users to save machines as commits back to their source repos! [Check out Anders’ demo previewing GitHub Sync in our recent office hours live stream](https://www.youtube.com/watch?v=WelBycMg2eA&t=1293s).
+We’re also working on a fully-fledged GitHub Sync feature, allowing users to save machines as commits back to their source repos! [Check out Anders’ demo previewing GitHub Sync in our recent office hours live stream](https://www.youtube.com/watch?v=WelBycMg2eA&t=1293s).
 ### Superpower Pro features
 
 Having teams allows other features to shine. For example, we all know the value of collaboration, but more users naturally add more potential for mistakes to happen, even with proper roles assigned. To protect against mistakes, we’ve added the ability to [lock machines](https://stately.ai/docs/lock-machines), preventing teammates from accidentally overwriting or deleting machines.