sig-architecture: Update references to WG Naming

Signed-off-by: Stephen Augustus <foo@auggie.dev>

1 files changed, 19 insertions, 19 deletions

diff --git a/sig-architecture/naming/workflow.md b/sig-architecture/naming/workflow.md
index 2ce4cc4c..b2f30343 100644
--- a/sig-architecture/naming/workflow.md
+++ b/sig-architecture/naming/workflow.md
@@ -1,17 +1,17 @@
 # Recommendations Workflow
 
-This document is a workflow for proposing language recommendations to
-WG Naming.
+This document is a workflow for proposing language recommendations for the
+Kubernetes project.
 
 ## Make a proposal
 
 Begin by sending a message outlining the proposed change to
-the [WG Naming mailing list][mailing-list].
+the [SIG Architecture mailing list][mailing-list].
 
-While WG Naming also discusses proposals in [#wg-naming][Slack], Slack is a lossy
-communication forum which is much harder to review than the mailing list.
+While proposals can also be discussed in [Slack], it is a lossy communication
+forum which is much harder to review than the mailing list.
 
-Proposals should include information required to file a WG Naming
+Proposals should include information required to file a Naming
 Architecture Decision Record (ADR):
 
 - The recommendation to be made
@@ -20,29 +20,29 @@ Architecture Decision Record (ADR):
 - Alternative recommendations
 - A reasonable guess at the work required to make the change
 
-For more information about the WG Naming ADR, review the [template].
+For more information about the Naming ADR, review the [template].
 
 Following a mailing list proposal, contributors can continue discussion both on Slack
-and at WG Naming meetings.
+and at SIG Architecture meetings.
 
 ### Filing a recommendation ADR
 
-If the working group's discussion determines that the recommendation is
+If the SIG's discussion determines that the recommendation is
 reasonable and in line with our [framework] for language evaluation,
-WG Naming leads formalize the recommendation with an ADR.
+SIG Architecture leads will formalize the recommendation with an ADR.
 
-For more information about the WG Naming ADR, review the [template].
+For more information about the Naming ADR, review the [template].
 
 An ADR must include:
 
-- Groups responsible for implementing the change
+- The groups responsible for implementing the change
 - The scope of the change in the Kubernetes project, as well as downstream
   implications
 
 ADRs must be opened with a `/hold` to give an opportunity to seek approval
 with the governance groups that with be responsible for implementation.
 
-After opening an ADR pull request, WG Naming leads
+After opening an ADR pull request, SIG Architecture leads
 should:
 
 - Reply to any mailing list threads about the recommendation with a link to the
@@ -76,17 +76,17 @@ agree to it.
 - ADR is on hold until approved by scoped areas (e.g., SIG Architecture, SIG
   Docs)
 - Steering is tagged on the ADR for approval
-- WG Naming lead establishes a Steering review/approval period with a lazy
+- SIG Architecture lead establishes a Steering review/approval period with a lazy
   consensus deadline of 3-5 business days
-- WG Naming lead releases the hold and merges ADR
+- SIG Architecture lead releases the hold and merges ADR
 
 ## Implementation
 
-- WG Naming leads record accepted recommendation in a canonical location (TBD)
+- SIG Architecture leads record accepted recommendation in a canonical location (TBD)
   (for example, a style guide)
 - Areas in scope are now responsible for implementation
 
 [framework]: language-evaluation-framework.md
-[mailing-list]: https://groups.google.com/forum/#!forum/kubernetes-wg-naming
-[slack]: https://kubernetes.slack.com/messages/wg-naming
-[template]: ./recommendations/template.md
+[mailing-list]: https://groups.google.com/forum/#!forum/kubernetes-sig-architecture
+[slack]: https://kubernetes.slack.com/messages/sig-architecture
+[template]: ./recommendations/000-template.md