From 51d48322c821dce851833239ea313e6af19b1f87 Mon Sep 17 00:00:00 2001
From: Steven Bucher <stevenbucher8@gmail.com>
Date: Wed, 17 Jan 2024 14:53:48 -0800
Subject: [PATCH 1/3] Update WG members

---
 docs/community/working-group-definitions.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/community/working-group-definitions.md b/docs/community/working-group-definitions.md
index 1b03901d460..c5a76148a7b 100644
--- a/docs/community/working-group-definitions.md
+++ b/docs/community/working-group-definitions.md
@@ -61,7 +61,6 @@ However, it's expected that many issues will require input from both WGs.
 
 ### Members
 
-* @BrucePay
 * @daxian-dbw
 * @JamesWTruher
 * @rkeithhill
@@ -104,7 +103,6 @@ particularly given the long-lasting effects of language decisions.
 
 * @JamesWTruher
 * @daxian-dbw
-* @BrucePay
 * @SeeminglyScience
 
 ## Remoting
@@ -118,7 +116,6 @@ Given the commonality of serialization boundaries, the Remoting WG should also f
 ### Members
 
 * @anmenaga
-* @PaulHigin
 * @TravisEz13
 
 ## Cmdlets and Modules
@@ -147,6 +144,7 @@ These modules include:
 * @SteveL-MSFT
 * @jdhitsolutions
 * @TobiasPSP
+* @doctordns
 
 ## Security
 
@@ -156,7 +154,8 @@ in order to provide their expertise, concerns, and guidance.
 ### Members
 
 * @TravisEz13
-* @PaulHigin
+* @SydneySmithReal
+* @anamnavi
 
 ## Explicitly not Working Groups
 

From 9d8fbd8d4557bd97ffdd7e0308f2776926d228c2 Mon Sep 17 00:00:00 2001
From: Steven Bucher <stevenbucher8@gmail.com>
Date: Wed, 17 Jan 2024 17:04:14 -0800
Subject: [PATCH 2/3] Added bergmeister

---
 docs/community/working-group-definitions.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/community/working-group-definitions.md b/docs/community/working-group-definitions.md
index c5a76148a7b..876abf7673f 100644
--- a/docs/community/working-group-definitions.md
+++ b/docs/community/working-group-definitions.md
@@ -38,6 +38,7 @@ Special consideration should be given to topics like **backwards compatibility**
 * @adityapatwardhan (SDK)
 * @michaeltlombardi
 * @SeeminglyScience
+* @bergmeister
 
 ## Engine
 

From 71130970499928ba397b80e290a6924bc880da07 Mon Sep 17 00:00:00 2001
From: Steven Bucher <stevenbucher8@gmail.com>
Date: Wed, 31 Jan 2024 14:41:15 -0800
Subject: [PATCH 3/3] fix linting problems

---
 docs/community/working-group-definitions.md | 24 ++++++++++-----------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/community/working-group-definitions.md b/docs/community/working-group-definitions.md
index 876abf7673f..a56d4c4ecf2 100644
--- a/docs/community/working-group-definitions.md
+++ b/docs/community/working-group-definitions.md
@@ -50,8 +50,8 @@ This includes (but is not limited to):
 * The language parser
 * The command and parameter binders
 * The module and provider systems
-    * `*-Item` cmdlets
-    * Providers
+  * `*-Item` cmdlets
+  * Providers
 * Performance
 * Componentization
 * AssemblyLoadContext
@@ -123,7 +123,7 @@ Given the commonality of serialization boundaries, the Remoting WG should also f
 
 The Cmdlet WG should focus on core/inbox modules whose source code lives within the
 `PowerShell/PowerShell` repository,
-including the proposal of new cmdlets and parameters, improvements and bug fixes to existing
+including the proposal of new cmdlets and parameters, improvements and bugfixes to existing
 cmdlets/parameters, and breaking changes.
 
 However, some modules that ship as part of the PowerShell package are managed in other source repositories.
@@ -170,12 +170,12 @@ This bucket is also not oriented a customer-facing deliverable and is already so
 so we don't need to address it as part of the WGs.
 
 * Build
-    * `build.psm1`
-    * `install-powershell.ps1`
-    * Build infrastructure and automation
+  * `build.psm1`
+  * `install-powershell.ps1`
+  * Build infrastructure and automation
 * Packaging
-    * Scripts
-    * Infrastructure
+  * Scripts
+  * Infrastructure
 
 ### Quality
 
@@ -184,10 +184,10 @@ Similar to the topic of building PowerShell, quality
 should be managed by the PowerShell Maintainers.
 
 * Test code
-    * Pester unit tests
-    * xUnit unit tests
+  * Pester unit tests
+  * xUnit unit tests
 * Test infrastructure
-    * Nightlies
-    * CI
+  * Nightlies
+  * CI
 * Code coverage
 * Pester