IRC to matrix changes.

Signed-off-by: James Antill <james@and.org>

modules/sysadmin_guide/pages/outage.adoc

@@ -30,7 +30,7 @@ outage.
 Owner::
   Fedora Infrastructure Team
 Contact::
-  #fedora-admin, sysadmin-main group
+  https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org, sysadmin-main group
 Location::
   Anywhere
 Servers::
@@ -58,8 +58,9 @@ a koji outage, let someone know.
 
 ==== Contacts
 
-Pretty much all coordination occurs in #fedora-admin on
-https://libera.chat/[libera.chat]. Stop by there to watch more about what's going on.
+Pretty much all coordination occurs in
+https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Infra on matrix].
+Stop by there to watch more about what's going on.
 Just stay on topic.
 
 === Unplanned Outage
@@ -88,8 +89,8 @@ Don't be general::
   after 60 seconds"
 
 Don't report an outage that's already been reported::
-  * BAD: "/join #fedora-admin; Is the build system broken?"
-  * Good: "/join #fedora-admin; wait a minute or two; I noticed I can't
+  * BAD: "/join #admin; Is the build system broken?"
+  * Good: "/join #admin; wait a minute or two; I noticed I can't
   submit builds, here's the error I get:"
 
 Don't suggest drastic or needless changes during an outage (send it to the list)::
@@ -105,7 +106,7 @@ Do research the technologies we're using and answer questions that may come up::
   http://httpd.apache.org/docs/2.2/mod/mod_mime.html#addencoding"
 
 Please try to contact OnCall first. This could be done by typing `.oncall`
-in #fedora-admin channel.
+in #admin matrix room.
 
 == Infrastructure Members (Admin Access)
 
@@ -148,7 +149,7 @@ Prior to beginning an outage to any monitored service on
 http://status.fedoraproject.org please push an update to reflect the
 outage (see xref:status-fedora.adoc[status-fedora SOP]).
 
-Report all information in #fedora-admin. Coordination is extremely
+Report all information in #admin. Coordination is extremely
 important, it's rare for our group to meet in person and matrix is our only
 real-time communication device. If a web site is out please put up some
 sort of outage page in its place.
@@ -157,7 +158,7 @@ sort of outage page in its place.
 
 Once the outage is over ensure that all services are up and running.
 Ensure all nagios services are back to green. Notify everyone in
-#fedora-admin to scan our services for issues. Once all services are
+#admin to scan our services for issues. Once all services are
 cleared update the status.fp.o dashboard. If the outage included a new
 feature or major change for a group, please notify that group that the
 change is ready. Make sure to close the ticket for the outage when it's
@@ -182,7 +183,7 @@ let the team know. Messes can always be cleaned up after the outage.
 ==== Determine Severity
 
 Some outages require immediate fixing, some don't. A page should never
-go out because someone can't sign the cla. Most of our admins are in US
+go out because someone can't sign the cla. Lots of our admins are in US
 time, use your best judgment.
 
 Use the following as loose guidelines, just use your best judgment.
@@ -204,7 +205,7 @@ After an outage has been verified, acknowledge the outage in nagios:
 https://admin.fedoraproject.org/nagios/, update the related system on
 the status dashboard (see the xref:status-fedora.adoc[status-fedora SOP])
 and verify changes at http://status.fedoraproject.org, then head in to
-#fedora-admin to figure out who is around and coordinate the next course
+#admin to figure out who is around and coordinate the next course
 of action. Consult any relevent SOP's for corrective actions.
 
 ==== Fix it

modules/sysadmin_guide/pages/wiki.adoc

@@ -7,7 +7,8 @@ Managing our wiki.
 Owner::
   Fedora Infrastructure Team / Fedora Website Team
 Contact::
-  #fedora-admin or #fedora-websites on libera.chat 
+  https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org
+  https://chat.fedoraproject.org/#/room/#websites:fedoraproject.org
 Location::
   https://fedoraproject.org/wiki/
 Servers::