chore: update current term length (#466)

Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>

Author: beeme1mr

community-members.md

@@ -4,10 +4,10 @@
 
 This is the current Governance Committee, per the Governance Committee Charter, in alphabetical order:
 
-- [Alois Reitbauer](https://github.com/aloisreitbauer), Dynatrace, term: February 1st, 2024 - January 31st 2025
-- [Ben Rometsch](https://github.com/dabeeeenster), Flagsmith, term: February 1st, 2024 - January 31st 2025
-- [Michael Beemer](https://github.com/beeme1mr), Dynatrace, term: February 1st, 2024 - January 31st 2025
-- [Pete Hodgson](https://github.com/moredip), Independent, term: February 1st, 2024 - January 31st 2025
+- [Alois Reitbauer](https://github.com/aloisreitbauer), Dynatrace, term: February 1st, 2025 - January 31st 2027
+- [Ben Rometsch](https://github.com/dabeeeenster), Flagsmith, term: February 1st, 2025 - January 31st 2027
+- [Michael Beemer](https://github.com/beeme1mr), Dynatrace, term: February 1st, 2025 - January 31st 2027
+- [Pete Hodgson](https://github.com/moredip), Independent, term: February 1st, 2025 - January 31st 2027
 - [Johan Rydberg](https://github.com/jrydberg), Spotify, term: February 1st, 2024 - January 31st 2026
 - [Jonathan Norris](https://github.com/jonathannorris), DevCycle, term: February 1st, 2024 - January 31st 2026
 - [Weyert de Boer](https://github.com/weyert), FNZ, term: February 1st, 2024 - January 31st 2026
@@ -44,13 +44,3 @@ _Bootstrap Governance Committee Member_,
 _Emeritus_.
 
 See [Contributor Ladder](./CONTRIBUTOR_LADDER.md) for additional information.
-
-
-
-
-
-
-
-
-
-

governance-charter.md

@@ -41,7 +41,7 @@ hosted by its maintainers and contributors.
 These meetings are used as additional discussion and consensus building
 but not for making decisions without prior discussion in async channels.
 
-#### Governance Committee Members
+### Governance Committee Responsibilities
 
 _Governance Committee_ members are responsible for representing the project in communications with organizations,
 including but not limited to contributor companies, adopters, vendors and foundations.
@@ -90,7 +90,7 @@ representation is achieved. If it is impossible to find sufficient members to
 resign, the entire company’s representation will be removed and new special
 elections held. In the event of a question of company membership (for example
 evaluating independence of corporate subsidiaries) a majority of all
-non-involved _Governance Committee_ members will decide. 
+non-involved _Governance Committee_ members will decide.
 
 ### Initial Election
 
@@ -154,5 +154,3 @@ of the _Governance Committee_ once their term ends.
 
 - For inquiries, please reach out to:
   - members of the [Governance Committee](https://github.com/open-feature/community/blob/main/community-members.md#governance-board)
-
-

tech-committee-charter.md

@@ -30,7 +30,6 @@ Changes to TC membership should be posted in the agenda document, and may be sug
 
 No more than one-third (33%) of the TC members may be affiliated with the same employer (same employer defined as "representing the same legal entity/project"). If removal or resignation of a TC member, or a change of employment by a TC member, creates a situation where more than one-third of the TC membership shares an employer, then the situation must be immediately remedied by the election of one or more TC members.
 
-
 ## Responsibilities of the Technical Committee
 
 The TC ensures that the project maintains a high level of technical excellence while continuing to meet the needs of its adopters, and facilitates ongoing community contribution.
@@ -69,8 +68,6 @@ In such cases, TC members will inform the the wider TC of the perceived conflict
 
 ## Elections
 
-
-
 ### Election of TC Members
 
 New TC members can be nominated by an existing TC Member. A candidate can be elected to the TC by the super-majority vote (greater than two thirds) of the existing TC members. The GC will have a veto for the new members.