Monitoring docs: Adjust Discord channels names

As we migrated the monitoring to another Discord server, we need to adjust
channel names occurring in the document.

monitoring/docs/monitoring-and-telemetry.adoc

@@ -297,19 +297,19 @@ that collects alerts (i.e. warning/critical system events) from the test
 === Alerts
 
 As mentioned earlier, Sentry uses the collected monitoring and telemetry data
-to raise alerts that are propagated to PagerDuty and Discord `pass:[*]-alerts` channels.
+to raise alerts that are propagated to PagerDuty and Discord channels.
 Here is the exact summary of configured alert rules:
 
 [%header,cols=4]
 |===
 |Alert name |Project |Firing conditions |Notified entities
 
-|https://keep-ko.sentry.io/alerts/rules/prod-threshold-dashboard/13626376/details[Mainnet deposit second track verification failure] |https://keep-ko.sentry.io/projects/prod-threshold-dashboard/?project=4504566725607424[prod-threshold-dashboard] |When deposit address returned by the second track deposit verifier is different from the address generated by the dashboard |PagerDuty and Discord `mainnet-alerts` channel
+|https://keep-ko.sentry.io/alerts/rules/prod-threshold-dashboard/13626376/details[Mainnet deposit second track verification failure] |https://keep-ko.sentry.io/projects/prod-threshold-dashboard/?project=4504566725607424[prod-threshold-dashboard] |When deposit address returned by the second track deposit verifier is different from the address generated by the dashboard |PagerDuty and Discord `tbtc-alerts` channel
 
-|https://keep-ko.sentry.io/alerts/rules/test-threshold-dashboard/13626401/details[Testnet deposit second track verification failure] |https://keep-ko.sentry.io/projects/test-threshold-dashboard/?project=4504564892827648[test-threshold-dashboard] |When deposit address returned by the second track deposit verifier is different from the address generated by the dashboard |Discord `testnet-alerts` channel
+|https://keep-ko.sentry.io/alerts/rules/test-threshold-dashboard/13626401/details[Testnet deposit second track verification failure] |https://keep-ko.sentry.io/projects/test-threshold-dashboard/?project=4504564892827648[test-threshold-dashboard] |When deposit address returned by the second track deposit verifier is different from the address generated by the dashboard |Discord `tbtc-testnet-notifications` channel
 
-|https://keep-ko.sentry.io/alerts/rules/prod-tbtc-v2-monitoring/13795336/details[Mainnet monitoring alerts Discord router] |https://keep-ko.sentry.io/projects/prod-tbtc-v2-monitoring/?project=4504684945342464[prod-tbtc-v2-monitoring] |When a new alert (i.e. warning/critical system event) is received from the TBTCv2 monitoring component |Discord `mainnet-alerts` channel
+|https://keep-ko.sentry.io/alerts/rules/prod-tbtc-v2-monitoring/13795336/details[Mainnet monitoring alerts Discord router] |https://keep-ko.sentry.io/projects/prod-tbtc-v2-monitoring/?project=4504684945342464[prod-tbtc-v2-monitoring] |When a new alert (i.e. warning/critical system event) is received from the TBTCv2 monitoring component |Discord `tbtc-alerts` channel
 
 |https://keep-ko.sentry.io/alerts/rules/prod-tbtc-v2-monitoring/13795667/details[Mainnet monitoring alerts PagerDuty router] |https://keep-ko.sentry.io/projects/prod-tbtc-v2-monitoring/?project=4504684945342464[prod-tbtc-v2-monitoring] |When a new critical alert (i.e. critical system event) is received from the TBTCv2 monitoring component |PagerDuty
 
-|https://keep-ko.sentry.io/alerts/rules/test-tbtc-v2-monitoring/13795270/details[Testnet monitoring alerts Discord router] |https://keep-ko.sentry.io/projects/test-tbtc-v2-monitoring/?project=4504672363806720[test-tbtc-v2-monitoring] |When a new alert (i.e. warning/critical system event) is received from the TBTCv2 monitoring component |Discord `testnet-alerts` channel
+|https://keep-ko.sentry.io/alerts/rules/test-tbtc-v2-monitoring/13795270/details[Testnet monitoring alerts Discord router] |https://keep-ko.sentry.io/projects/test-tbtc-v2-monitoring/?project=4504672363806720[test-tbtc-v2-monitoring] |When a new alert (i.e. warning/critical system event) is received from the TBTCv2 monitoring component |Discord `tbtc-testnet-notifications` channel