Update team leads page

Author: meg-gutshall

_includes/events/team_leads.html

@@ -59,7 +59,7 @@ <h2 class="mb-10">What Does It Mean To Lead a Team?</h2>
     <div class="row">
       <div class="col mb-20">
         <p>
-          As a team lead, you will be connecting with a partner organization that has a non profit or civic mandate and work to deliver them software in support of their mission. This entails everything from meeting with the stakeholders, gathering requirements, translating those requirements, providing initial architecting, planning out project milestones, communicating with Ruby for Good organizers, pitching your project to Ruby for Good attendees, leading your team at the event, and seeing the project through to completion.
+          As a team lead, you will be connecting with a partner organization that has a non-profit or civic mandate and work to deliver them software in support of their mission. This entails everything from meeting with the stakeholders, gathering requirements, translating those requirements, providing initial architecting, planning out project milestones, communicating with Ruby for Good organizers, pitching your project to Ruby for Good attendees, leading your team at the event, and seeing the project through to completion.
         </p>
       </div>
     </div>
@@ -146,7 +146,7 @@ <h2 class="mb-10">What We Expect From Our Team Leads</h2>
           </li>
           <li class="indented">Ruby for Good begins!</li>
           <li class="indented">
-            Pitch your project to Ruby for Good attendees on opening night (4:00 PM EST sharp): Provide a brief intro to the organization, to the project, ask for specific technical skills if needed, and communicate your team’s goals if you feel strongly about them (examples: deploy by the end of the event, emphasize team learning, master new gems, mandate pairing for all coding, explore new frontend technologies, etc.)
+            Pitch your project to Ruby for Good attendees on opening night (4:00 PM PST sharp): Provide a brief intro to the organization, to the project, ask for specific technical skills if needed, and communicate your team’s goals if you feel strongly about them (examples: deploy by the end of the event, emphasize team learning, master new gems, mandate pairing for all coding, explore new frontend technologies, etc.)
           </li>
           <li class="indented">
             Set team goals with your team. See above for inspiration.