diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a6306f0..6136b4f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -130,7 +130,7 @@
 
 If you are planning a new function, you should get agreement that your
 change will be accepted.  As early as you can, introduce the change
-via the OpenBMC IRC channel or email list to start
+via the OpenBMC Discord server or email list to start
 the discussion.  You may find a better way to do what you need.
 
 Submitting changes
@@ -395,8 +395,8 @@
 
 If you feel your patch has been missed entirely, of course, it's
 alright to email the maintainers (addresses available in MAINTAINERS file) or
-ping them on IRC - but a reasonable timeframe to do so is on the order of a week,
-not on the order of hours.
+ping them on Discord - but a reasonable timeframe to do so is on the order of a
+week, not on the order of hours.
 
 The maintainers' job is to ensure that incoming patches are as correct and easy
 to maintain as possible. Part of the nature of open source is attrition -
diff --git a/MAINTAINERS b/MAINTAINERS
index 5f41018..e393c29 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -21,7 +21,7 @@
 
     Section entries are structured according to the following scheme:
 
-    X:  NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>
+    X:  NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>
     X:  ...
     .
     .
@@ -31,10 +31,10 @@
     organization; FILE_PATH is a file path within the repository, possibly with
     wildcards; X is a tag of one of the following types:
 
-    M:  Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
+    M:  Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
         if omitted from an entry, assume one of the maintainers from the
         MAINTAINERS entry.
-    R:  Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
+    R:  Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
         these people are to be added as reviewers for a change matching the repo
         path.
     F:  Denotes forked from an external repository; has fields URL.
diff --git a/README.md b/README.md
index 204023d..ed81cbc 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,6 @@
 - Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
 - List Archive: https://lore.kernel.org/openbmc/
 - Discord: https://discord.gg/69Km47zH98
-- IRC: #openbmc on freenode.net
 
 ## OpenBMC Development
 
diff --git a/anti-patterns.md b/anti-patterns.md
index b735098..b9a995a 100644
--- a/anti-patterns.md
+++ b/anti-patterns.md
@@ -31,7 +31,7 @@
 ### Background
 (1 paragraph) Describe why the anti-pattern exists.  If you don't know, try
 running git blame and look at who wrote the code originally, and ask them on the
-mailing list or in IRC what their original intent was, so it can be documented
+mailing list or in Discord what their original intent was, so it can be documented
 here (and you may possibly discover it isn't as much of an anti-pattern as you
 thought).  If you are unable to determine why the anti-pattern exists, put:
 "Unknown" here.
diff --git a/designs/design-template.md b/designs/design-template.md
index 20dbc8b..26e9ead 100644
--- a/designs/design-template.md
+++ b/designs/design-template.md
@@ -28,13 +28,13 @@
 # Example design - this is the design title
 
 Author:
-  < Name and IRC nic >
+  < Name and Discord nic >
 
 Primary assignee:
-  < Name and/or IRC nic or None >
+  < Name and/or Discord nic or None >
 
 Other contributors:
-  < Name and/or IRC nic or None >
+  < Name and/or Discord nic or None >
 
 Created:
   < Date initially created in Month D, Yr format (e.g. June 17, 2020 or Dec 19,
diff --git a/designs/voltage-regulator-configuration.md b/designs/voltage-regulator-configuration.md
index fc7ed6f..8e618be 100644
--- a/designs/voltage-regulator-configuration.md
+++ b/designs/voltage-regulator-configuration.md
@@ -1,10 +1,10 @@
 # Voltage Regulator Configuration
 
-Author: Shawn McCarney (IRC ShawnMcCarney)
+Author: Shawn McCarney (Discord ShawnMcCarney)
 
 Primary assignee: Shawn McCarney
 
-Other contributors: Derek Howard (IRC derekh55), Matt Spinler (IRC mspinler)
+Other contributors: Derek Howard (Discord derekh55), Matt Spinler (Discord mspinler)
 
 Created: 2019-07-13
 
diff --git a/release/release-process.md b/release/release-process.md
index ff21a76..762e5d5 100644
--- a/release/release-process.md
+++ b/release/release-process.md
@@ -120,7 +120,7 @@
 
 Work groups can be formal or not depending on the work needing to be done and
 the community member style. They can consist of email to the list or formal
-weekly meetings via IRC or call to discuss designs and progress.
+weekly meetings via Discord or call to discuss designs and progress.
 
 ### Backlog
 The backlog is simply the proposed release features that did not make the