update charter with new language + people

Author: emilypi

proposals/CHARTER.md

@@ -23,16 +23,16 @@ HFTT Members are tasked with the following responsibilities:
 
 None.
 
-The HFTT may make decisions regarding accepted technical projects. The CTO (or other delegated HF executive) shall arrange budgetary or resource requests as needed, based on the outcome of decisions made by the HFTT, with the budget committee and Executive Director of the HF.
+The HFTT may make decisions regarding accepted technical projects. The CTO (or other delegated authority) shall arrange budgetary or resource requests as needed, based on the outcome of decisions made by the HFTT, with the budget committee and Executive Director of the HF.
 
 
 ## Term
 
-The participation of least one HF executive is required and indefinite. General HFTT members serve for 3 years.
+The participation of least one person who is an HF Executive or delegated authority is required. General HFTT members serve for 3 years.
 
 ## Membership
 
-HF Executive:
+Delegated Authority:
 
 - Emily Pillmore ([@emilypi](https://github.com/emilypi))
 
@@ -52,15 +52,15 @@ Members:
 
 - Reporting must be accurate, consistent, and in good faith
 - Changes to HFTT membership require simple majority approval
-- 1 HF Executive and 8 general members shall be required for a functioning HFTT
-- No one may serve two terms consecutively, except for the HF Executive.
+- 1 Delegated authority and 8 general members shall be required for a functioning HFTT
+- No one may serve two terms consecutively, except for the CTO/delegated authority.
 - Elections *must* be held such that there is no period when the HFTT is not at full membership
 
 ## Election Procedure
 
-Elections shall be held in a public manner, using the forum designated by the HF bylaws for formal discussion. The delegating HF Executive shall approve all language for the election publication. All additional publication on the part of the HFTT for the purpose of socializing the election should link to the formal discussion. Elections should be announced publicly exactly 60 days before member terms expire, and submissions should cease to be accepted 14 days before member terms expire, with all membership decisions finalized and publicized 7 days before member terms expire. During this 7-day lame duck period, no votes may be made on proposals.
+Elections shall be held in a public manner, using the forum designated by the HF bylaws for formal discussion. The CTO or other HF-delegated authority shall approve all language for the election publication. All additional publication on the part of the HFTT for the purpose of socializing the election should link to the formal discussion. Elections should be announced publicly exactly 60 days before member terms expire, and submissions should cease to be accepted 14 days before member terms expire, with all membership decisions finalized and publicized 7 days before member terms expire. During this 7-day lame duck period, no votes may be made on proposals.
 
-If not enough candidates apply for the number of seats expiring, the delegating HF Executive may fill these seats as needed using their discretion.
+If not enough candidates apply for the number of seats expiring, the CTO or other HF-delegated authority may fill these seats as needed using their discretion.
 
 ## Becoming a member
 
@@ -83,7 +83,7 @@ Ranked voting is used, with the following criteria required for each status:
 
 ### Membership changes
 
-Membership changes require 66% majority for approval. All initial membership seats shall be appointed by the delegating HF Executive at their discretion.
+Membership changes require 66% majority for approval. All initial membership seats shall be appointed by the CTO at their discretion.
 
 
 ## Reporting