Update leadership overview

leadership-resources/leadership_overview.md

@@ -1,12 +1,12 @@
 # Leadership Overview & Expectations 
 
-Women Who Code is not possible without the wonderful volunteers who dedicate their time and passion to spreading our mission. Our netowrks are led by 400+ volunteers including our amazing team of ladies in richmond. We need all forms of support! Those interested in hosting and sponsoring, presenting, coordinating one event or many. If youre interested in helping us **please do not hesitate to reach out** Below are our expectations of those interested in becomming a core team member. 
+Women Who Code is not possible without the wonderful volunteers who dedicate their time and passion to spreading our mission. Our networks are led by 400+ volunteers including our amazing team of ladies in Richmond. We need all forms of support! Those interested in hosting and sponsoring, presenting, coordinating one event or many. If youre interested in helping us **please do not hesitate to reach out** Below are our expectations of those interested in becoming a core team member. 
 
 ### Expectation of all Leads 
 
 ---
 
-**Work toward the 2018 Netowrk goals**
+**Work toward the 2018 Network goals**
 
 - At the end of each year we will come together as a team to recap and plan for the following year. In this we will identify new or recurring [Goals](network-goals.md) for our network
 
@@ -17,23 +17,23 @@ Women Who Code is not possible without the wonderful volunteers who dedicate the
     1. Welcome new members (the leads who attended a Meetup should each reach out to two newer attendees to follow up about something
                             leads who didn't attend the Meetup should monitor Slack to welcome new members in the channel by @name)                          
     2. encourage conversations in the general group 
-    3. provide technical community through slack (post in your repsective technology domain channels )
+    3. provide technical community through slack (post in your respective technology domain channels)
 
     **slack is as active as we make it**
-- Attend one quartely chapter meeting with other leads and directors 
+- Attend one quarterly chapter meeting with other leads and directors 
 
 **Be open and committed**
 - When life hits the fan just let us know you need to step back. This is why we have multiple people filling roles, But remember your commitments to your positions 
-- Update github with resources & links posted in relevant channels for your events
-- Coordinate with your leads on a regular basis (consider making a private slack channel to collaborate. for ex: all python leads would join #python-leads)
-- Lean in! (something about helping other areas, coming up with ideas, and invtiting others to join)
+- Update GitHub with resources & links posted in relevant channels for your events
+- Coordinate with your leads on a regular basis (consider making a private slack channel to collaborate. For ex: all python leads would join #python-leads)
+- Lean in! Invite friends and co-workers to join! Help come up with ideas for the future of WWC RVA. Jump onboard with other areas that might need help one month.
 - If you need help making an event, speak to one of the other leads or ask in #core-team on Slack.
 
 **Be a wwcode example**
 - Uphold our [Code of Conduct](../code_of_conduct.md)
 - Know our [mission and vision](https://www.womenwhocode.com/about)
 - Guide new leaders through expectations of being a lead 
-- Hone your craft & develop your self 
+- Hone your craft & develop yourself 
 
 
 ### Education Team Roles and Responsibilites
@@ -42,56 +42,56 @@ Women Who Code is not possible without the wonderful volunteers who dedicate the
 **Directors**
 
 - Responsible for community and network technology events 
-    - Insuring teams have enough bandwidth (2-3 leads each) & gauging lead investment 
+    - Ensure teams have enough bandwidth (2-3 leads each) & gauge lead investment 
     - Schedule meetups 
     - Attend newly created meetups for leadership support & one off events
-    - Keep backalog of events and source one-offs/hackathon events 
-    - Grow communites as bandwidth is satisfied 
-    - Maintain github organization 
+    - Keep backlog of events and source one-offs/hackathon events 
+    - Grow communities as bandwidth is satisfied 
+    - Maintain GitHub organization 
     - Help generate new events and communities 
 
 **Community Leads** 
 
-- responsible for coordinating rercurring meetups around specific technology topic.  
-    - Leads facilitate scheduling with the education directors on a quarterly basis (can be one event a quarter, a month, a week etc) 
-    - Set direction for your community. Take a look at our [event inspiration ](event-inspiration.md) for ideas on types of events your community could have (eel free to mix it up!).
-    - Send directors details (Dates, Space, event details) of upcoming meetups in a timley manor (3 months out). Review the [playbook](event-playbook.md) for gudiance on how to approach coordinating meetups.     
-    - Share pictures / blurbs for social 
-    - Maintain github repos for community
+- Responsible for coordinating reoccurring meetups around specific technology topics.  
+    - Leads facilitate scheduling with the education directors on a quarterly basis (can be one event a quarter, a month, a week etc.) 
+    - Set direction for your community. Take a look at our [event inspiration ](event-inspiration.md) for ideas on types of events your community could have (feel free to mix it up!).
+    - Send directors details (Dates, Space, event details) of upcoming meetups in a timely manner (3 months out). Review the [playbook](event-playbook.md) for guidance on how to approach coordinating meetups.     
+    - Share pictures / blurbs for social media 
+    - Maintain GitHub repos for your community
 
 
 
 **One Off leads** 
 
-- Rsponsible for coordinating one off technical meetups as badnwidth and speaker/content availbility allow. 
+- Rsponsible for coordinating one off technical meetups as bandwidth and speaker/content availbility allows. 
     - Leads should be actively monitoring the one-off backlog for potential events 
-    - Send directors details (Dates, Space, event details) of upcoming meetups in a timley manor (3 months out). Review the [playbook](event-playbook.md) for gudiance on how to approach coordinating meetups.     
-    - Share pictures / blurbs for social 
-    - Share code/ resources on github when needed 
+    - Send directors details (Dates, Space, event details) of upcoming meetups in a timely manner (3 months out). Review the [playbook](event-playbook.md) for guidance on how to approach coordinating meetups.     
+    - Share pictures / blurbs for social media 
+    - Share code / resources on GitHub when needed 
 
 ### Network Roles & Responsibilities 
 ---
 
 **Directors**
 
 - Responsible for network events and community building 
-    - Develope backlog of partner orginizations interested in host and sponsor opportunities
+    - Develop backlog of partner organizations interested in host and sponsor opportunities
     - grow richmond community participation 
-    - coordinate content and netowrk leads 
+    - coordinate content and network leads 
 
 
 **Content Lead** 
 
-- Repsonsbile for sharing wwcode mission and values and creating presence in richmond and beyon 
-    - Strong understanding of the WWCode core values and mision. 
-    - Manage Social Media precesne, Email, Blog Posts, meeting minutes?.
+- Responsible for sharing wwcode mission and values and creating presence in Richmond and beyond 
+    - Strong understanding of the WWCode core values and mission. 
+    - Manage Social Media presence, Email, Blog Posts, meeting minutes?.
     - Strong communication skills 
 
 
 
 **Network Leads** 
 
-- Responsible for networking and larger community building evens 
+- Responsible for networking and larger community building events 
     - Leads should be actively monitoring the backlog for potential events 
-    - Send directors details (Dates, Space, event details) of upcoming meetups in a timley manor (3 months out). Review the [playbook](event-playbook.md) for gudiance on how to approach coordinating meetups.     
-    - Share pictures / blurbs for social 
+    - Send directors details (Dates, Space, event details) of upcoming meetups in a timely manner (3 months out). Review the [playbook](event-playbook.md) for guidance on how to approach coordinating meetups.     
+    - Share pictures / blurbs for social media