diff --git a/README.md b/README.md
index cf527e1f6..c525f1503 100644
--- a/README.md
+++ b/README.md
@@ -260,7 +260,7 @@ companies that have donated miscellaneous hardware:
 
 
 If you would like to donate hardware to the Node.js Project, please reach
-out to the Build Working Group, via the [#build channel on the Node.js slack
+out to the Build Working Group, via the [#nodejs-build channel on the OpenJS Foundation Slack
 instance][1] or contact [Rod Vagg](mailto:rod@vagg.org) directly. The Build
 Working Group reserves the right to choose what hardware is actively used
 and how it is used, donating hardware does not guarantee its use within the
@@ -284,7 +284,7 @@ months after the release goes End-of-Life, in case further build or test runs
 are required. After that the configuration will be removed.
 
 
-[1]:    https://node-js.slack.com/archives/C16SCB5JQ
+[1]:    https://openjs-foundation.slack.com/archives/C03BJP63CH0
 [2]:    https://digitalocean.com/
 [3]:    https://www.rackspace.com/
 [5]:    https://www.mailgun.com/
diff --git a/doc/jenkins-guide.md b/doc/jenkins-guide.md
index 9f469d11d..2098f4199 100644
--- a/doc/jenkins-guide.md
+++ b/doc/jenkins-guide.md
@@ -51,7 +51,7 @@ ansible-playbook playbooks/jenkins/worker/create.yml --limit test-rackspace-free
 If all goes according to plan, then Ansible should be able to run the
 playbook with no errors. If you do encounter problems, there are usually
 some WG members available in the
-[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), who can try and
+[Node.js Build Slack channel][], who can try and
 lend a hand.
 
 ## Security releases
@@ -129,7 +129,7 @@ Relevant logs:
 ## Solving problems
 
 Issues with the Jenkins clusters are usually reported to either the
-[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), or to the
+[Node.js Build Slack channel][], or to the
 [`nodejs/build` issue tracker](https://github.com/nodejs/build/issues).
 
 When trying to fix a worker, ensure that you `mark the node as offline`,
@@ -369,7 +369,7 @@ to its desired state, including refreshing and restarting the Jenkins
 agent configuration.
 
 If none of the above steps work, please post in the
-[Node.js Build Slack channel](https://node-js.slack.com/archives/C16SCB5JQ), or the
+[Node.js Build Slack channel][], or the
 [`nodejs/build` issue tracker](https://github.com/nodejs/build/issues), to allow
 for escalation and other WG members to troubleshoot.
 
@@ -381,3 +381,4 @@ take a look.
 [secrets repo]: https://github.com/nodejs-private/secrets
 [ci]: https://ci.nodejs.org/computer/test-softlayer-ubuntu1804_container-x64-1/
 [1]: https://ci.nodejs.org/computer/test-softlayer-ubuntu1804_container-x64-1/
+[Node.js Build Slack channel]: https://openjs-foundation.slack.com/archives/C03BJP63CH0