Incorporating @xmulligan 's review comments

Signed-off-by: Emily Fox <themoxiefoxatwork@gmail.com>

operations/README.md

@@ -6,4 +6,4 @@ This directory contains various files, procedures, responsibilties, and expectat
 
 * [TOC Onboarding](onboarding.md) - a collection of materials, general information, and other relevant details to support new and returning TOC members in getting up to speed.
 * [Decision Process](toc-decision-process.md) - General information on how we make decisions.
-* [TOC Chair](toc-chair.md) - Addition onboarding, responsibilities, expectations of the TOC Chair.
+* [TOC Chair](toc-chair.md) - Additional onboarding, responsibilities, expectations of the TOC Chair.

operations/onboarding.md

@@ -26,7 +26,7 @@ The expected time commitment of a TOC member is anywhere from **10-25% of their
 
 The TOC has four (4) hour-long meetings per month held on Tuesdays at 0800 PST/1100 EST/1700 CET.  The first meeting of each month are Technical Advisory Group (TAG) updates and discussion. As a [Liaison](../../tags/cncf-tags.md#toc-liaisons) to one or more TAGs, the content presented and discussed by the TAG should be information you are already aware of. For TAGs that you are not a liaison for, this is your opportunity to become aware of the broader work being done within speciality technical domains and verticals.  It allows you to connect various TAGs and projects together, promoting interoperability for the benefit of the technical community and its adopters.
 
-The second and fourth meetings are generally private meetings. During these meetings, the TOC meets to review issues on the repo, conduct vote parties (to ensure outstanding votes are completed), and discuss any open issues, activities, tasks, and other efforts. Periodically, we may invite the Maintainers, projects or other groups to join us to join so we may connect with them, understand any challenges and successes they encounter, and take feedback to improve our engangements.
+The second and fourth meetings are generally private meetings. During these meetings, the TOC meets to review issues on the repo, conduct vote parties (to ensure outstanding votes are completed), and discuss any open issues, activities, tasks, and other efforts. Periodically, we may invite the Maintainers, projects, or other groups to join us to join so we may connect with them, understand any challenges and successes they encounter, and take feedback to improve our engangements.
 
 The third meeting is public and will usually cover public discussion on improvements and activities the TOC is pursuing or community-led topics where the TOC has oversight or is needed to facilitate neutral consensus.
 
@@ -42,10 +42,10 @@ The TOC attends Governing Board meetings periodically when invited, our particip
 
 At KCCN, the TOC has three additional engagements; TOC Keynote, TOC Panel, and TOC/TAG Meeting.  The TOC keynote is about 15 minutes in length and is delivered by one or more TOC members and may include guests. Common topics are:
 * introducing what the TOC is
-* conveying changes to the ecosystem/landscapre since the last KCCN
+* conveying changes to the ecosystem/landscape since the last KCCN
 * community oriented topics
 
-The TOC Panel is a panel of the TOC members present at the conference and functions similar to a ask-me-anything session. The CNCF CTO initiates the panel by providing an overview to attendees of who the TOC is and what we do. They will often initiate the first few questions to the panel and facilitate attendee questions to the TOC. 
+The TOC Panel is a panel of the TOC members present at the conference and functions similar to an ask-me-anything session. The CNCF CTO initiates the panel by providing an overview to attendees of who the TOC is and what we do. They will often initiate the first few questions to the panel and facilitate attendee questions to the TOC.
 
 The TOC and TAG meeting may be an open (conference attendees may observe) or closed meeting, depending on the topics. This meeting focuses heavily on the TAGs, their health, and their work. TOC Liaisons are expected to make time to meet with their TAGs as part of that meeting.
 
@@ -80,11 +80,11 @@ Emojis can be used individually or with other emojis, this usually happens to in
 
 ### Due Diligence
 
-The primary work a TOC member engages is in conducting the due diligence of cloud native projects as they advance in their maturity, this process is commonly referred to the moving levels or maturation process. After a TOC member steps forward to sponsor a project, it is anticipated that a kick-off meeting is held to set expectations for what the process will be like, provide rough timelines, collect additional information and allow the project to ask any questions.  This kick-off is commonly conducted as a virtual meeting, not lasting more than an hour. Additionally, TOC members should anticipate a few hours of concentrated review, analysing the project, its repository(ies), and clarifying the content of the due diligence. Additional time is expected to be spent conducting and summarizing Adopter interviews to ascertain the current usage of the project within industry.
+The primary work a TOC member engages is in conducting the due diligence of cloud native projects as they advance in their maturity, this process is commonly referred to the moving levels or maturation process. After a TOC member steps forward to sponsor a project, it is anticipated that a kick-off meeting is held to set expectations for what the process will be like, provide rough timelines, collect additional information and allow the project to ask any questions.  This kick-off is commonly conducted as a virtual meeting, not lasting more than an hour. Additionally, TOC members should anticipate a few hours of concentrated review, analysing the project, its repository(ies), and clarifying the content of the due diligence. Additional time is expected to be spent conducting and summarizing Adopter interviews to ascertain the current usage of the project within the industry.
 
 ## Voting
 
-The TOC primarily votes in one of two mechanisms, gitvote or on the mailing list. It is our preference that voting occur with gitvote in the repository as this provides better transparency and is easier to verify and track vote execution. Voting conducted over the mailing list is performed by responding with a +1 Binding (+1B), or -1 Binding (-1). TOC members may abstain if they have a conflict of interest. Indication of abstention from voting for any other reason is discouraged and should not be confused with not yet voting as indication of abstention is active, not passive, andresults in no vote being rendered by that individual. In the absence of information, we cannot make an informed decision, so it is imperative that we ask questions openly and provide answers with clarity for our peer TOC members, particularly on topics that may not be their strength. A vote passes with two-thirds vote of votes cast based on the charter (see [6(c)(viii)](https://www.cncf.io/about/charter)).
+The TOC primarily votes in one of two mechanisms, gitvote or on the mailing list. It is our preference that voting occur with gitvote in the repository as this provides better transparency and is easier to verify and track vote execution. Voting conducted over the mailing list is performed by responding with a +1 Binding (+1B), or -1 Binding (-1). TOC members may abstain if they have a conflict of interest. Indication of abstention from voting for any other reason is discouraged and should not be confused with not yet voting as indication of abstention is active, not passive, and results in no vote being rendered by that individual. In the absence of information, we cannot make an informed decision, so it is imperative that we ask questions openly and provide answers with clarity for our peer TOC members, particularly on topics that may not be their strength. A vote passes with two-thirds vote of votes cast based on the charter (see [6(c)(viii)](https://www.cncf.io/about/charter)).
 
 ## Lobbying and Direct Messages
 

operations/toc-chair.md

@@ -20,7 +20,7 @@ The Chair is expected to perform a variety of functions and can often be thought
 * Ensure notes and actions are documented and issued for TOC meetings with follow-up
 * Verify appropriate workload distribution among the TOC members
 * Ensure TOC meetings have a facilitator and agenda
-* Foster discussion - ask questions, even obvious ones to move the conversation forward or to closure.
+* Foster discussion - ask questions, even obvious ones to move the conversation forward or to closure
 * Protect TOC time - People like to sign the TOC up for a lot of things, you are responsible for ensuring we’re involved in the things we need to be and which ones are not on us
 * Redirect work out of scope of the TOC to the appropriate group (Kubernetes Steering, Governing Board, Code of Conduct Committee, Legal Committee, etc.)
 * Bring project and group conflicts that escalate to the TOC level to closure, either through delegation to TOC members and awareness or through direct resolution while keeping the TOC informed