diff --git a/working-conventions.md b/working-conventions.md
index 33d20dada2aa2e3bc719a07895cc498ad4df4987..b66b3b885120af683a1116106c5ae83ff4ce78f3 100644
--- a/working-conventions.md
+++ b/working-conventions.md
@@ -57,22 +57,22 @@ We therefore adopt the following working conventions:
 The HF encompasses many people, and it can be challenging for large groups of people
 to collaborate to Get Things Done. Accordingly, we often break into smaller groups,
 focused on a particular goal. Broadly, these groups may be classified as either Committees
-or Task Forces. We define these terms here:
+or Working Groups. We define these terms here:
 
 * A **committee** is a functional group of the Board. Committees are described by and subject to
   the [relevant rules in a separate document describing the functioning of the Board](board.md#8-committees).
   Committees tend to be chaired by Board members and filled mostly or entirely with Board members.
   Committees are concerned with the high-level governance of the HF.
 
-* In contrast, a **task force** is a functional group under the (perhaps
+* In contrast, a **working group** is a functional group under the (perhaps
   indirect) control of HF's Executive Director. By "indirect" here, we mean
-  that a task force might be commissioned by any employee of the HF, not just
-  the ED. A task force is charged with furthering the HF's goals to support
+  that a working group might be commissioned by any employee of the HF, not just
+  the ED. A working group is charged with furthering the HF's goals to support
   the Haskell language, ecosystem, and community. It is typically (but not
   exclusively) led by an employee of the HF, and staffed with any relevant
   members of the community.
 
-  Task forces do not generally have concrete rules around their creation and functioning,
+  Working groups do not generally have concrete rules around their creation and functioning,
   as they serve at the pleasure of whichever HF employee created them. Naturally,
   whoever creates them can set down rules, if they like.
 
@@ -84,7 +84,7 @@ leaves or joins the HF Board, all of these places will need to be updated:
 1. Membership of [mailing lists](https://groups.google.com/): `board@hf`, `leadership-internal@hf`, and `board-internal@hf`.
 1. Membership of private channels on Slack: `hf-board-internal`, `hf-leadership-internal`, `donuts-for-the-board`, and any private channels for committees.
 1. Access on the [HF Drive](https://drive.google.com/drive/folders/1gxc2miCWM0gwMoA7ywUH3qY--q277Ifc?usp=sharing), and any subfolders. (It is unclear when changes propagate, so be careful.)
-1. The [State of the Haskell Foundation](https://docs.google.com/spreadsheets/d/1oRoa3uTCVZMWbLbM8Q_L06Os3yLzTAcrXIxFQWI-Z_I/edit?usp=sharing), including any committees and task forces. Remember to update the Prior Board Members tab for leavers.
+1. The [State of the Haskell Foundation](https://docs.google.com/spreadsheets/d/1oRoa3uTCVZMWbLbM8Q_L06Os3yLzTAcrXIxFQWI-Z_I/edit?usp=sharing), including any committees and working groups. Remember to update the Prior Board Members tab for leavers.
 1. The [Haskell GitLab instance](https://gitlab.haskell.org/groups/hf/-/group_members).
 1. The "Board Vote" [MR approval rule setting](https://gitlab.haskell.org/hf/meta/edit) needs to be adjusted if the number of Board members changes.
 1. The [website](https://github.com/haskellfoundation/haskellfoundation.github.io).