diff --git a/doc/make/index.md b/doc/make/index.md
index 3dfce12c51..320d6db035 100644
--- a/doc/make/index.md
+++ b/doc/make/index.md
@@ -142,7 +142,7 @@ After building a stage, you can invoke `make -C stageN test` (or, even better,
 automatically use that stage's corresponding Lean executables, for running tests
 or compiling Lean programs manually, you need to put them into your `PATH`
 yourself. A simple option for doing that is to use
-[`elan`](https://github.com/Kha/elan), see the next section.
+[`elan`](https://github.com/leanprover/elan), see the next section.
 
 You can use any of the [supported editors](../setup.md) for editing the Lean source
 code. If you set up `elan` as below, opening `src/` as a *workspace folder* should
@@ -153,14 +153,14 @@ go-to-definition in the stdlib (automatically set when using `nix-shell`).
 Dev setup using elan
 --------------------
 
-You can use [`elan`](https://github.com/Kha/elan) to easily switch between
+You can use [`elan`](https://github.com/leanprover/elan) to easily switch between
 stages and build configurations based on the current directory, both for the
 `lean/leanc/leanmake` binaries in your shell's PATH and inside your editor.
 
 If you haven't already installed elan, you can do so, without installing a
 default version of Lean, using
 ```bash
-curl https://raw.githubusercontent.com/Kha/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain none
+curl https://raw.githubusercontent.com/leanprover/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain none
 ```
 You can use `elan toolchain link` to give a specific stage build directory a
 reference name, then use `elan override set` to associate such a name to the
diff --git a/doc/quickstart.md b/doc/quickstart.md
index 6e5158588b..4790559985 100644
--- a/doc/quickstart.md
+++ b/doc/quickstart.md
@@ -3,9 +3,9 @@
 These instructions will walk you through setting up Lean using the "basic" setup and VS Code as the editor.
 See [Setup](./setup.md) for other ways and more details on setting up Lean.
 
-1. Install the latest Lean 4 nightly through [`elan`](https://github.com/Kha/elan): in any bash-compatible shell, run
+1. Install the latest Lean 4 nightly through [`elan`](https://github.com/leanprover/elan): in any bash-compatible shell, run
     ```sh
-    $ curl https://raw.githubusercontent.com/Kha/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain leanprover/lean4:nightly
+    $ curl https://raw.githubusercontent.com/leanprover/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain leanprover/lean4:nightly
     ```
     See the `elan` link above for other installation options and details.
     Note that using Lean with multi-file projects on Windows currently comes with some [additional limitations](./setup.md#leanpkg).
diff --git a/doc/setup.md b/doc/setup.md
index 01bbd28de5..46c0f66405 100644
--- a/doc/setup.md
+++ b/doc/setup.md
@@ -2,7 +2,7 @@
 
 There are currently two ways to set up a Lean 4 development environment:
 
-* [basic setup](./setup.md#basic-setup) (Linux/macOS/Windows): uses [`elan`](https://github.com/Kha/elan) + your preinstalled editor
+* [basic setup](./setup.md#basic-setup) (Linux/macOS/Windows): uses [`elan`](https://github.com/leanprover/elan) + your preinstalled editor
 * [Nix setup](./setup.md#nix-setup) (Linux/macOS/WSL): uses the [Nix](https://nixos.org/nix/) package manager for installing all dependencies localized to your project
 
 See also the [quickstart](./quickstart.md) instructions for using the basic setup with VS Code as the editor.
@@ -10,7 +10,7 @@ See also the [quickstart](./quickstart.md) instructions for using the basic setu
 ## Basic Setup
 
 Release builds for all supported platforms are available at <https://github.com/leanprover/lean4/releases>.
-Instead of downloading these and setting up the paths manually, however, it is recommended to use the Lean version manager [`elan`](https://github.com/Kha/elan) instead:
+Instead of downloading these and setting up the paths manually, however, it is recommended to use the Lean version manager [`elan`](https://github.com/leanprover/elan) instead:
 ```sh
 $ elan self update  # in case you haven't updated elan in a while
 # download & activate latest Lean 4 release (https://github.com/leanprover/lean4/releases)