Remove makeup of TAC, left to charter

Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>

organizational-structure-overview.md

@@ -12,7 +12,6 @@ The OpenSSF is comprised of instances of the following categories of official gr
 - The **Governing Board** (GB) oversees the budget and legal status/structure of the OpenSSF. Board meetings may or may not be open to the public.
 - **Committees** are formed by, and report to, the Board. Broadly speaking, Committees handle non-technical matters as needed by the GB, wherein a named set of people are tasked with handling a specific objective. Like the Board meetings, Committee meetings may or may not be open to the public.
 - The **Technical Advisory Council** (TAC) is responsible for the general success of all Technical Initiatives (defined below). TAC meetings are generally open to the public, with the exception of special sessions. 
-  - TAC membership is composed of three representatives elected bi-annually by all active contributors (as defined by the TAC) and four representatives elected on alternating years by the Governing Board. Contributors to Technical Initiatves may run, and each contributor may vote once in TAC elections. 
 - **Technical Initiatives** are groups formed in support of the overall mission of the OpenSSF. Technical Initiatives include Working Groups (WG), Special Interest Groups (SIG), Projects, and services governed by their own Charters with various objectives, reporting relationships, and funding models described below.
    - All Technical Initiatives are open groups focused on a technical objective, with transparent proceedings that are open to the public, and vary in their objectives.
    - Technical Initiatives usually manage one or more GitHub repos of their own and may have separate meetings.

process/project-lifecycle.md

@@ -4,7 +4,7 @@ The OpenSSF's mission is to inspire and enable the community to secure the open
 
 ## Project Life Cycle
 
-New projects to the OpenSSF, and progression through the project lifecycle, are approved by the Technical Advisory Council (TAC). A project's oversight is provided by either the Technical Advisory Council (TAC) or a specific Working Group (WG). When a Project reports into a specific WG, that WG can support the Project's progression and provide recommendations to the TAC.
+New [Projects](../organizational-structure-overview.md#definitions) to the OpenSSF, and progression through the project lifecycle, are approved by the Technical Advisory Council (TAC). A project's oversight is provided by either the Technical Advisory Council (TAC) or a specific Working Group (WG). When a Project reports into a specific WG, that WG can support the Project's progression and provide recommendations to the TAC.
 
 Projects follow the Sandbox, Incubating, Graduated, and Archived lifecycle stages defined below. Projects that seek widespread adoption and end user use are expected to progress through the stages. Projects coming to OpenSSF that already meet the entry requirements may enter the Incubating stage directly.
 

process/request_resources.md

@@ -33,7 +33,7 @@ Requests that go through the OpenSSF Budget Committee are reviewed at regularly
 ### Infrastructure
 
 _Program TBD as of June 2022. Intended program details below._
-Central infrastructure is available to qualifying projects for test and build support. Projects should submit requests on an annual basis to the OpenSSF Budget Committee, a minimum of three months before the requested start date. Projects are responsible for submitting a resource forecast with their request. The Budget Committee and project will work together to agree on minimum infrastructure support based on annual budget. Projects are responsible for communicating to the Budget Committee if unanticipated increases (including spike events) arise. 
+Central infrastructure is available to qualifying projects for test and build support. Projects should submit requests on an annual basis to the OpenSSF Budget Committee, a minimum of three months before the requested start date. Projects are responsible for submitting a resource forecast with their request. The Budget Committee and project will work together to agree on minimum infrastructure support based on annual budget. Projects are responsible for communicating to the Budget Committee if unexpected increases (including spike events) arise. 
 
 ### Maintainer stipends