diff --git a/communication.md b/communication.md
index 96ae9e0a7a13b1d29366f999d40aa252ff0b8179..417ca52b2db9a61fa5fc55bffc0ab2c5d5b6519d 100644
--- a/communication.md
+++ b/communication.md
@@ -4,6 +4,7 @@ This document describes how the Haskell Foundation Board communicates
 among itself and to the broader Haskell community.
 
 In thinking about communication, it is helpful to identify (at least) four different scenarios:
+
 1. Board members communicating with one another
 2. Community members talking to the Board
 3. The Board communicating out to the community
@@ -33,7 +34,7 @@ This document refers back to these scenarios by number.
    e. Certain sensitive topics (e.g. personnel) are communicated by direct email
    to the Board members; these emails are not archived.
 
-1. Communication from the Board to the community (Scenario 3) and between members of the community (Scenario 4)
+2. Communication from the Board to the community (Scenario 3) and between members of the community (Scenario 4)
    go via the [Haskell Foundation category](https://discourse.haskell.org/c/haskell-foundation/11)
    of the [Haskell Discourse instance](https://discourse.haskell.org/).
 
@@ -45,9 +46,9 @@ This document refers back to these scenarios by number.
 
    c. Members of the HF will be sure to monitor the traffic in this Category.
 
-1. All task forces, committees and ad hoc groups are invited to use
-   the Haskell Foundation chat service (details TBD), because it is great for
-   lightweight, private and informal conversations.
+3. All task forces, committees, ad hoc groups, and anyone else interested in the Haskell Foundation's activities are invited to use
+   the [Haskell Foundation Slack](https://haskell-foundation.slack.com/), 
+   because it is great for lightweight, private and informal conversations. 
 
    a. In recognition of the fact that not all Board members will be able to
    monitor chat at all times, anyone participating in a chat discussion is
@@ -78,7 +79,7 @@ This document refers back to these scenarios by number.
    apply, chat is considered private and is not subject to our transparency
    policy. Chat conversations are not archived.
 
-1. Official communication between Board members goes through the mailing list. For example, an asynchronous
+4. Official communication between Board members goes through the mailing list. For example, an asynchronous
    vote is conducted only via the mailing list, never in other modes. Board members
    are *not* required to keep up with Discourse, and so if you want to reach the entire
    Board, email `board@haskell.foundation`.
@@ -87,7 +88,7 @@ This document refers back to these scenarios by number.
 
    * To address the Board specifically (Scenario 2), email `board@haskell.foundation`.
    * To address the community (Scenario 4), including Board members, use Discourse.
-   
+
 ## Synchronous communication (meetings)
 
 The rules of official Board meetings (Scenario 1) are laid out [here](board.md).
@@ -110,14 +111,14 @@ The rules of official Board meetings (Scenario 1) are laid out [here](board.md).
    for co-editing documents (Scenario 1); GitLab is good for long-term archiving and public
    release (Scenario 3).
 
-1. Both Google Drive and GitLab are intended to be used for Board-internal communication,
+2. Both Google Drive and GitLab are intended to be used for Board-internal communication,
    communication with and within the Executive Team, communication within Task Forces as well
    general communication of the Foundation. (Scenarios 1 and 3)
 
-1. The Board will establish access policies for different parts of its Google Drive and GitLab
+3. The Board will establish access policies for different parts of its Google Drive and GitLab
    which the Chair and the Secretary will implement in their role as adminstrators.
 
-1. The Executive Team establishes their own practices for data storage and document management
+4. The Executive Team establishes their own practices for data storage and document management
    and informs the Board about those.
 
 ### Current status