diff --git a/docs/onboarding/index.md b/docs/onboarding/index.md
index 8a980a8d99dff74f962495cd49bf0cac38729cee..2cabeb6ef914e4dfc92931d9b051d546a66e0f20 100644
--- a/docs/onboarding/index.md
+++ b/docs/onboarding/index.md
@@ -9,11 +9,13 @@ This can be considered a good starting point for any new member of the team, thu
 
 ## Mattermost
 
-Most internal discussions take place in the ~lxsoft-admins mattermost channel.
+Most internal discussions take place in the [~lxsoft-admins](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-admins) mattermost channel. We also have a channel [~lxsoft-alerts](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-alerts) which is where automated system messages are recorded.
 
-We also have a channel ~lxsoft-alerts which is where automated system messages are recorded.
+We also have a channel with 2nd level [~linux-team](https://mattermost.web.cern.ch/it-dep/channels/linux-team), [~linux-afs](https://mattermost.web.cern.ch/it-dep/channels/linux-afs) to receive alerts and discuss with the AFS team, [~linux-config-collaboration](https://mattermost.web.cern.ch/it-dep/channels/linux-config-collaboration) for discussions with the Config team and [~opensearch-for-linux](https://mattermost.web.cern.ch/it-dep/channels/opensearch-for-linux) for notifications related to our OpenSearch instance.
 
-Both channels are private, thus you will need to be invited by an existing member.
+These channels are all private, thus you will need to be invited by an existing member.
+
+You should also join the public [~linux](https://mattermost.web.cern.ch/it-dep/channels/linux) channel, where users sometimes report incidents.
 
 ## Rota
 
diff --git a/docs/rota/tasks.md b/docs/rota/tasks.md
index 614e6af513071de4e211e8ceacee64da962c41fa..2c8d7573e4306d8b770f3b190e2bd942258093a1 100644
--- a/docs/rota/tasks.md
+++ b/docs/rota/tasks.md
@@ -4,7 +4,7 @@ The Linux team is in charge of providing a supported Linux distribution for CERN
 
 Starting with RHEL 7, CERN decided to join the CentOS community and help them rather than duplicating the work for rebuilding the same sources from Red Hat. CC7 (CERN CentOS 7) is just a simple respin of CentOS 7 with additional CERN repositories and staged updates.
 
-Alma Linux 8/9, CS8 (CentOS Stream 8) follow upstream as closely as possible, with automated daily snapshots and minimal rebuilds.
+AlmaLinux and Red Hat follow upstream as closely as possible, with automated daily composes (snapshots) and minimal rebuilds.
 
 Our main method of communication as a team is via the Mattermost channel [~lxsoft-admins](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-admins). As a member of the team, **you are expected to follow that channel closely**. There's not a lot of small talk there, generally we're discussing how to solve a particular issue. Even if you're not involved in that specific issue, reading the messages helps us all learn from one another and stay up-to-date with the state of the services we run.
 
@@ -16,14 +16,13 @@ You need to attend the incredibly useful [Ticket Review Meeting](https://indico.
 
 The main tasks as a release manager are :
 
-- Keep an eye on the automation for [CC7](https://gitlab.cern.ch/linuxsupport/cronjobs/centos7_release), [CS8](https://gitlab.cern.ch/linuxsupport/cronjobs/stream8_snapshots) and [AlmaLinux](https://gitlab.cern.ch/linuxsupport/cronjobs/alma_snapshots). Every day, several emails will be sent to `lxsoft-admins` notifying you of the progress, and the full logs can also be seen in [Kibana](https://es-linux.cern.ch/?security_tenant=internal).
+- Keep an eye on the automation for [ELS7](https://gitlab.cern.ch/linuxsupport/cronjobs/els7_release), [AlmaLinux](https://gitlab.cern.ch/linuxsupport/cronjobs/alma_snapshots) and [Red Hat](https://gitlab.cern.ch/linuxsupport/cronjobs/rhel_snapshots). Every day, several emails will be sent to `lxsoft-admins` notifying you of the progress, and the full logs can also be seen in [Kibana](https://os-linux.cern.ch/?security_tenant=internal).
     - Should the automation fail or stop for any reason (new packages that need to be rebuilt, etc.), your job is to make sure the situation is corrected and the automation can continue (either that day, by rerunning the cronjob, or the next).
-    - For CC7, production updates should happen on Thursday morning, and for CS8 and Alma8/9 they should happen on Wednesday morning.
+    - For AlmaLinux and RHEL, production updates should happen on Wednesday morning and testing updates should happen every weekday.
     - Manually, these updates may be stopped or done earlier depending on issues in the upstream packages or urgent security fixes. Always check with the rest of the team before doing so.
-- Stay up-to-date with the latest Red Hat and CentOS updates. Notifications for particularly interesting packages [will be sent](https://gitlab.cern.ch/linuxsupport/cronjobs/centos_rss) to the Mattermost channel [~lxsoft-alerts](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-alerts), but from time to time there will be other interesting updates that are not [on the list](https://gitlab.cern.ch/linuxsupport/cronjobs/centos_rss/-/blob/master/centos_rss/prod.packages.yml).
-    - Notifications about ["dangerous packages"](https://linuxops.web.cern.ch/distributions/cs8/#-release-packages-the-dangerous-rpms) need to be acted upon as soon as possible. Not doing so incurrs a debt of croissants for the rest of the team.
-    - This also includes keeping track of new Red Hat point releases and [publishing them](../support/redhat.md).
-- Once a month on the first of the month, new [Openstack](https://gitlab.cern.ch/linuxsupport/koji-image-build) and Docker images ([CC7](https://gitlab.cern.ch/linuxsupport/cc7-base), [CS8](https://gitlab.cern.ch/linuxsupport/cs8-base), [Alma9](https://gitlab.cern.ch/linuxsupport/alma9-base), [Alma8](https://gitlab.cern.ch/linuxsupport/alma8-base)) will be created a Gitlab scheduled jobs. Make sure the process works and all the tests pass. Promote the resulting images to production.
+- Stay up-to-date with the latest Red Hat and CentOS updates. Notifications for particularly interesting packages [will be sent](https://gitlab.cern.ch/linuxsupport/cronjobs/package_alerts) to the Mattermost channel [~lxsoft-alerts](https://mattermost.web.cern.ch/it-dep/channels/lxsoft-alerts), but from time to time there will be other interesting updates that are not [on the list](https://gitlab.cern.ch/linuxsupport/cronjobs/package_alerts/-/blob/master/package_alerts/prod.packages.yml).
+    - Notifications about ["dangerous packages"](/distributions/snapshots/#-release-packages-the-dangerous-rpms) need to be acted upon as soon as possible. Not doing so incurs a debt of croissants for the rest of the team.
+- Once a month on the first of the month, new [Openstack](https://gitlab.cern.ch/linuxsupport/koji-image-build) and Docker images ([Alma9](https://gitlab.cern.ch/linuxsupport/alma9-base), [Alma8](https://gitlab.cern.ch/linuxsupport/alma8-base)) will be created by some Gitlab scheduled jobs. Make sure the process works and all the tests pass. Promote the resulting images to production.
 - All alerts need to be investigated and understood/fixed in a timely manner by the rota person. The rota person should also notify the rest of the team of the root cause and solution for the alerts.
 
 ## Services