Zulip streams have been renamed to channels
https://blog.zulip.com/2024/07/25/zulip-9-0-released
diff --git a/src/backend/debugging.md b/src/backend/debugging.md
index 4f8712d..3dc95f2 100644
--- a/src/backend/debugging.md
+++ b/src/backend/debugging.md
@@ -183,7 +183,7 @@
### Getting help and asking questions
If you have some questions, head over to the [rust-lang Zulip] and
-specifically the `#t-compiler/wg-llvm` stream.
+specifically the `#t-compiler/wg-llvm` channel.
[rust-lang Zulip]: https://rust-lang.zulipchat.com/
diff --git a/src/compiler-team.md b/src/compiler-team.md
index 9922ee7..6be5283 100644
--- a/src/compiler-team.md
+++ b/src/compiler-team.md
@@ -12,7 +12,7 @@
Currently the compiler team chats in Zulip:
- Team chat occurs in the [`t-compiler`][zulip-t-compiler] stream on the Zulip instance
-- There are also a number of other associated Zulip streams,
+- There are also a number of other associated Zulip channels,
such as [`t-compiler/help`][zulip-help], where people can ask for help
with rustc development, or [`t-compiler/meetings`][zulip-meetings],
where the team holds their weekly triage and steering meetings.
diff --git a/src/notification-groups/arm.md b/src/notification-groups/arm.md
index 3abc32c..5b79030 100644
--- a/src/notification-groups/arm.md
+++ b/src/notification-groups/arm.md
@@ -9,7 +9,7 @@
ARM-related issues as well as suggestions on how to resolve
interesting questions regarding our ARM support.
-The group also has an associated Zulip stream ([`#t-compiler/arm`])
+The group also has an associated Zulip channel ([`#t-compiler/arm`])
where people can go to pose questions and discuss ARM-specific
topics.
diff --git a/src/notification-groups/emscripten.md b/src/notification-groups/emscripten.md
index 100dbdf..9e4086c 100644
--- a/src/notification-groups/emscripten.md
+++ b/src/notification-groups/emscripten.md
@@ -9,7 +9,7 @@
Emscripten-related issues as well as suggestions on how to resolve
interesting questions regarding our Emscripten support.
-The group also has an associated Zulip stream ([`#t-compiler/wasm`])
+The group also has an associated Zulip channel ([`#t-compiler/wasm`])
where people can go to pose questions and discuss Emscripten-specific
topics.
diff --git a/src/notification-groups/risc-v.md b/src/notification-groups/risc-v.md
index 1b31297..7c8a3cd 100644
--- a/src/notification-groups/risc-v.md
+++ b/src/notification-groups/risc-v.md
@@ -9,7 +9,7 @@
RISC-V-related issues as well as suggestions on how to resolve
interesting questions regarding our RISC-V support.
-The group also has an associated Zulip stream ([`#t-compiler/risc-v`])
+The group also has an associated Zulip channel ([`#t-compiler/risc-v`])
where people can go to pose questions and discuss RISC-V-specific
topics.
diff --git a/src/notification-groups/rust-for-linux.md b/src/notification-groups/rust-for-linux.md
index 696f203..ed1de91 100644
--- a/src/notification-groups/rust-for-linux.md
+++ b/src/notification-groups/rust-for-linux.md
@@ -12,7 +12,7 @@
for resolving the breakage or decide to temporarily accept the breakage
and unblock CI by temporarily removing the RfL CI jobs.
-The group also has an associated Zulip stream ([`#rust-for-linux`])
+The group also has an associated Zulip channel ([`#rust-for-linux`])
where people can go to ask questions and discuss topics related to Rust
for Linux.
diff --git a/src/notification-groups/wasi.md b/src/notification-groups/wasi.md
index e438ee4..88b9465 100644
--- a/src/notification-groups/wasi.md
+++ b/src/notification-groups/wasi.md
@@ -9,7 +9,7 @@
WASI-related issues as well as suggestions on how to resolve
interesting questions regarding our WASI support.
-The group also has an associated Zulip stream ([`#t-compiler/wasm`])
+The group also has an associated Zulip channel ([`#t-compiler/wasm`])
where people can go to pose questions and discuss WASI-specific
topics.
diff --git a/src/notification-groups/wasm.md b/src/notification-groups/wasm.md
index c8b674c..6f52b04 100644
--- a/src/notification-groups/wasm.md
+++ b/src/notification-groups/wasm.md
@@ -9,7 +9,7 @@
WebAssembly-related issues as well as suggestions on how to resolve
interesting questions regarding our WASM support.
-The group also has an associated Zulip stream ([`#t-compiler/wasm`])
+The group also has an associated Zulip channel ([`#t-compiler/wasm`])
where people can go to pose questions and discuss WASM-specific
topics.
diff --git a/src/notification-groups/windows.md b/src/notification-groups/windows.md
index e615a2c..d245208 100644
--- a/src/notification-groups/windows.md
+++ b/src/notification-groups/windows.md
@@ -9,7 +9,7 @@
Windows-related issues as well as suggestions on how to resolve
interesting questions regarding our Windows support.
-The group also has an associated Zulip stream ([`#t-compiler/windows`])
+The group also has an associated Zulip channel ([`#t-compiler/windows`])
where people can go to pose questions and discuss Windows-specific
topics.
diff --git a/src/traits/chalk.md b/src/traits/chalk.md
index 844f42b..ca5ed52 100644
--- a/src/traits/chalk.md
+++ b/src/traits/chalk.md
@@ -5,7 +5,7 @@
Its goal is to enable a lot of trait system features and bug fixes
that are hard to implement (e.g. GATs or specialization). If you would like to
help in hacking on the new solver, drop by on the rust-lang Zulip in the [`#t-types`]
-stream and say hello!
+channel and say hello!
[Types team]: https://github.com/rust-lang/types-team
[`#t-types`]: https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types
diff --git a/src/typing_parameter_envs.md b/src/typing_parameter_envs.md
index db15467..fd77f42 100644
--- a/src/typing_parameter_envs.md
+++ b/src/typing_parameter_envs.md
@@ -82,7 +82,7 @@
- In the next-gen trait solver all `Goal`s have a [`param_env` field][goal_param_env] specifying what environment to prove the goal in
- When editing an existing [`TypeRelation`][typerelation] if it implements [`PredicateEmittingRelation`][predicate_emitting_relation] then a [`param_env` method][typerelation_param_env] will be available.
-If you aren't sure if there's a `ParamEnv` in scope somewhere that can be used it can be worth opening a thread in the [`#t-compiler/help`][compiler_help] zulip stream where someone may be able to point out where a `ParamEnv` can be acquired from.
+If you aren't sure if there's a `ParamEnv` in scope somewhere that can be used it can be worth opening a thread in the [`#t-compiler/help`][compiler_help] zulip channel where someone may be able to point out where a `ParamEnv` can be acquired from.
Manually constructing a `ParamEnv` is typically only needed at the start of some kind of top level analysis (e.g. hir typeck or borrow checking). In such cases there are three ways it can be done:
- Calling the [`tcx.param_env(def_id)` query][param_env_query] which returns the environment associated with a given definition.
