From 0d90545e39b8a3b858ba1fc65219b174e067c43d Mon Sep 17 00:00:00 2001
From: Hamza REMMAL <hamza@remmal.net>
Date: Fri, 1 Mar 2024 19:52:32 +0100
Subject: [PATCH] Update links to use scala/scala3 instead of lampepfl/dotty

---
 README.md                                     |  2 +-
 _data/governance.yml                          |  4 +-
 _includes/downloads-scala3.html               |  6 +-
 _layouts/downloadpage.html                    |  4 +-
 .../2015-10-23-dotty-compiler-bootstraps.md   |  4 +-
 _posts/2015-11-16-minutes-from-nov-2015.md    |  2 +-
 _posts/2016-01-11-minutes-from-jan-2016.md    |  8 +-
 _posts/2016-02-17-scaling-dot-soundness.md    |  8 +-
 _posts/2016-05-06-multiversal-equality.md     |  4 +-
 _posts/2016-10-14-dotty-errors.md             |  2 +-
 _posts/2016-12-07-implicit-function-types.md  |  4 +-
 _posts/2017-02-28-collections-rework.md       |  2 +-
 ...017-12-01-fifth-dotty-milestone-release.md | 12 +--
 _posts/2019-12-18-road-to-scala-3.md          |  2 +-
 _posts/2020-02-20-community-build.md          |  4 +-
 ...es-bring-generic-programming-to-scala-3.md |  2 +-
 _posts/2023-02-01-release-notes-3.2.2.md      |  2 +-
 ...023-07-17-signature-polymorphic-methods.md |  2 +-
 _posts/2023-09-07-release-notes-3.3.1.md      |  2 +-
 ...017-05-31-first-dotty-milestone-release.md | 10 +--
 ...17-07-12-second-dotty-milestone-release.md | 62 +++++++--------
 ...017-09-07-third-dotty-milestone-release.md | 28 +++----
 ...17-10-16-fourth-dotty-milestone-release.md | 16 ++--
 blog/_posts/2018-04-19-scala-3.md             |  4 +-
 blog/_posts/2018-04-30-in-a-nutshell.md       |  8 +-
 ...-12-15-scala-3-crossing-the-finish-line.md |  2 +-
 blog/_posts/2021-05-14-scala3-is-here.md      |  2 +-
 .../2021-07-21-scala-3.0.2RC1-is-here.md      | 78 +++++++++----------
 .../_posts/2021-09-07-scala-3.0.2-released.md | 12 +--
 .../_posts/2021-10-21-scala-3.1.0-released.md | 10 +--
 .../_posts/2022-02-01-scala-3.1.1-released.md | 10 +--
 .../_posts/2022-04-12-scala-3.1.2-released.md |  2 +-
 .../_posts/2022-06-21-scala-3.1.3-released.md |  2 +-
 .../_posts/2022-11-07-scala-3.2.1-released.md |  2 +-
 .../2023-01-31-scala-center-2023-roadmap.md   | 14 ++--
 ...3-04-11-march-2023-scala-tooling-summit.md |  2 +-
 .../_posts/2023-05-30-scala-3.3.0-released.md |  2 +-
 ...23-10-17-feedback-wanted-error-messages.md | 18 ++---
 ...24-02-29-scala-3.4.0-and-3.3.3-released.md |  6 +-
 community/index.md                            |  2 +-
 gsoc/2015.md                                  |  2 +-
 gsoc/2016.md                                  |  4 +-
 42 files changed, 187 insertions(+), 187 deletions(-)

diff --git a/README.md b/README.md
index 4498606ac..5be57fccd 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@ This repository contains the source for the [scala-lang.org](https://scala-lang.
 
 It does not contain the source for the [docs.scala-lang.org](https://docs.scala-lang.org) subdomain. You can visit the [docs.scala-lang repository](https://github.com/scala/docs.scala-lang) if you are interested in contributing to the Scala documentation site.
 
-The repository for Scala 3 itself is https://github.com/lampepfl/dotty .
+The repository for Scala 3 itself is https://github.com/scala/scala3 .
 
 Scala 2 is at https://github.com/scala/scala. Scala 2 bug reports are at https://github.com/scala/bug.
 
diff --git a/_data/governance.yml b/_data/governance.yml
index 63a4341a2..7bb063236 100644
--- a/_data/governance.yml
+++ b/_data/governance.yml
@@ -72,9 +72,9 @@ cards:
     anchorTarget: "gov-scala-3"
     links:
       - name: Core Maintainers
-        url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md#compiler
+        url: https://github.com/scala/scala3/blob/main/MAINTENANCE.md#compiler
       - name: Maintenance Procedures
-        url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md
+        url: https://github.com/scala/scala3/blob/main/MAINTENANCE.md
   - title: "Moderation"
     description: "Learn how the Scala community is moderated."
     expandText: "Process & People"
diff --git a/_includes/downloads-scala3.html b/_includes/downloads-scala3.html
index e3886a649..c1bb03841 100644
--- a/_includes/downloads-scala3.html
+++ b/_includes/downloads-scala3.html
@@ -1,10 +1,10 @@
 <p>Are you looking for <a href="{{ site.baseurl }}/download/all.html">another release</a> of Scala?</p>
 <br/>
-<p>Scala binaries for <strong>{{page.release_version}}</strong> are available at <a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">github</a>.</p>
+<p>Scala binaries for <strong>{{page.release_version}}</strong> are available at <a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">github</a>.</p>
 
 <h3>Release Notes</h3>
 For a summary of important changes, see the <a
-  href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">GitHub release notes</a>.
+  href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">GitHub release notes</a>.
 <br /><small>(Or consult our archive of <a href="{{ site.baseurl }}/blog/announcements/">older release
     notes</a>.)</small>
 
@@ -20,7 +20,7 @@ <h2>Ways to Install This Release</h2>
       </li>
       <li>
         Download the Scala binaries for <strong>{{page.release_version}}</strong> at <a
-          href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">github</a>.
+          href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">github</a>.
         <br /><span class="install"><a href="{{ site.baseurl }}/download/install.html">Need help running the
             binaries?</a></span>
       </li>
diff --git a/_layouts/downloadpage.html b/_layouts/downloadpage.html
index 4cfc90be1..de0556587 100644
--- a/_layouts/downloadpage.html
+++ b/_layouts/downloadpage.html
@@ -34,9 +34,9 @@ <h1>{{page.title}}</h1>
         </div>
         <ul>
           {% if scala_edition == "3" %}
-            <li><a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">Release Notes</a></li>
+            <li><a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">Release Notes</a></li>
             <li class="dot">•</li>
-            <li><a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">Changelog</a></li>
+            <li><a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">Changelog</a></li>
           {% else %}
             <li><a href="https://github.com/scala/scala/releases">Release Notes</a></li>
             <li class="dot">•</li>
diff --git a/_posts/2015-10-23-dotty-compiler-bootstraps.md b/_posts/2015-10-23-dotty-compiler-bootstraps.md
index f7d4962ce..75c30b573 100644
--- a/_posts/2015-10-23-dotty-compiler-bootstraps.md
+++ b/_posts/2015-10-23-dotty-compiler-bootstraps.md
@@ -7,7 +7,7 @@ title: We got liftoff! The Dotty compiler for Scala bootstraps.
 
 ## We got liftoff!
 
-The [Dotty project](https://github.com/lampepfl/dotty)
+The [Dotty project](https://github.com/scala/scala3)
 is a platform to develop new technology for Scala
 tooling and to try out concepts of future Scala language versions.
 Its compiler is a new design intended to reflect the
@@ -67,4 +67,4 @@ Samuel Gruetter ([@samuelgruetter](https://github.com/samuelgruetter)),
 Vera Salvis ([@vsalvis](https://github.com/vsalvis)),
 and Jason Zaugg ([@retronym](https://github.com/retronym)).
 
-To get started: <https://github.com/lampepfl/dotty>.
+To get started: <https://github.com/scala/scala3>.
diff --git a/_posts/2015-11-16-minutes-from-nov-2015.md b/_posts/2015-11-16-minutes-from-nov-2015.md
index d549a0075..ba18dde48 100644
--- a/_posts/2015-11-16-minutes-from-nov-2015.md
+++ b/_posts/2015-11-16-minutes-from-nov-2015.md
@@ -155,7 +155,7 @@ Notes:
 
 ### SIP: Auto-uncurry n-ary functions
 
-There is no SIP tracking issue as yet, but information can be found here: [https://github.com/lampepfl/dotty/issues/897](https://github.com/lampepfl/dotty/issues/897)
+There is no SIP tracking issue as yet, but information can be found here: [https://github.com/scala/scala3/issues/897](https://github.com/scala/scala3/issues/897)
 
 No issue created as yet, but [@odersky](https://github.com/odersky) will create one if needed
 
diff --git a/_posts/2016-01-11-minutes-from-jan-2016.md b/_posts/2016-01-11-minutes-from-jan-2016.md
index fc557a4dc..775826810 100644
--- a/_posts/2016-01-11-minutes-from-jan-2016.md
+++ b/_posts/2016-01-11-minutes-from-jan-2016.md
@@ -26,11 +26,11 @@ Notes:
 - The SIP is a design proposal about the syntax and what the semantics of these features might be, but at this point has no code.
 - This idea has come up a few times over the years and is based on those previous discussions.
 
-This proposal and [dotty](https://github.com/lampepfl/dotty):
+This proposal and [dotty](https://github.com/scala/scala3):
 
 [@odersky](https://github.com/odersky):
 
-- have considering something like this in [dotty](https://github.com/lampepfl/dotty). Doing this involves considering quite a few rules (and their corner cases), which this SIP doesn't cover.
+- have considering something like this in [dotty](https://github.com/scala/scala3). Doing this involves considering quite a few rules (and their corner cases), which this SIP doesn't cover.
 - generally sympathetic, but not sure this has the format for a SIP.
 
 [@odersky](https://github.com/odersky) thinks there should be a wider discussion about this, involving:
@@ -41,7 +41,7 @@ This proposal and [dotty](https://github.com/lampepfl/dotty):
 
 Conclusion:
 
-[@odersky](https://github.com/odersky) thinks this is promising, but needs to be fleshed out for a SIP. He also notes that [dotty](https://github.com/lampepfl/dotty) wants to do this, so we might want to wait and synchronize rather than have [@ahmadsalim](https://github.com/ahmadsalim) spend a lot of time working on this, only to find a different approach has been made in dotty.
+[@odersky](https://github.com/odersky) thinks this is promising, but needs to be fleshed out for a SIP. He also notes that [dotty](https://github.com/scala/scala3) wants to do this, so we might want to wait and synchronize rather than have [@ahmadsalim](https://github.com/ahmadsalim) spend a lot of time working on this, only to find a different approach has been made in dotty.
 
 [@non](https://github.com/non), it's good to be clear that there are two things people want here:
 
@@ -55,4 +55,4 @@ Conclusion:
 
 Actions:
 
-Ask [@ahmadsalim](https://github.com/ahmadsalim) to talk to the [dotty](https://github.com/lampepfl/dotty) team about this.
+Ask [@ahmadsalim](https://github.com/ahmadsalim) to talk to the [dotty](https://github.com/scala/scala3) team about this.
diff --git a/_posts/2016-02-17-scaling-dot-soundness.md b/_posts/2016-02-17-scaling-dot-soundness.md
index de3380b3b..b97890397 100644
--- a/_posts/2016-02-17-scaling-dot-soundness.md
+++ b/_posts/2016-02-17-scaling-dot-soundness.md
@@ -69,9 +69,9 @@ categories:
     is not associated with a runtime value.
 
 We can in fact construct soundness issues in all of these cases. Look
-at the discussion for issues [#50](https://github.com/lampepfl/dotty/issues/50)
-and [#1050](https://github.com/lampepfl/dotty/issues/1050) in the
-[dotty](https://github.com/lampepfl/dotty/issues/1050) repository
+at the discussion for issues [#50](https://github.com/scala/scala3/issues/50)
+and [#1050](https://github.com/scala/scala3/issues/1050) in the
+[dotty](https://github.com/scala/scala3/issues/1050) repository
 on GitHub. All issues work fundamentally in the same way: Construct a type `S`
 which has a type member `T` with bad bounds, say
 
@@ -94,7 +94,7 @@ course. The promise is usually broken at run-time by failing with a
 ## Plugging the Loopholes
 
 To get back to soundness we need to plug the loopholes. Some of the
-necessary measures are taken in pull request [#1051](https://github.com/lampepfl/dotty/issues/1051).
+necessary measures are taken in pull request [#1051](https://github.com/scala/scala3/issues/1051).
 That pull request
 
  - tightens the rules for overrides of lazy values: lazy values
diff --git a/_posts/2016-05-06-multiversal-equality.md b/_posts/2016-05-06-multiversal-equality.md
index dd4659105..d71d5b3a6 100644
--- a/_posts/2016-05-06-multiversal-equality.md
+++ b/_posts/2016-05-06-multiversal-equality.md
@@ -8,7 +8,7 @@ discourse: true
 
 I have been working recently on making equality tests using `==` and
 `!=` safer in Scala. This has led to a [Language Enhancement
-Proposal](https://github.com/lampepfl/dotty/issues/1247) which I summarize in this blog.
+Proposal](https://github.com/scala/scala3/issues/1247) which I summarize in this blog.
 
 ## Why Change Equality?
 
@@ -118,7 +118,7 @@ backwards compatibility, we allow comparisons of such types as well,
 by means of a fall-back `eqAny` instance. But we do not allow comparisons
 between types that have an `Eq` instance and types that have none.
 Details are explained in the
-[proposal](https://github.com/lampepfl/dotty/issues/1247).
+[proposal](https://github.com/scala/scala3/issues/1247).
 
 ## Properties
 
diff --git a/_posts/2016-10-14-dotty-errors.md b/_posts/2016-10-14-dotty-errors.md
index cf3e6445a..6ef9e31e8 100644
--- a/_posts/2016-10-14-dotty-errors.md
+++ b/_posts/2016-10-14-dotty-errors.md
@@ -97,7 +97,7 @@ information for the error or warning.
 
 So - this is what you do:
 
-1. Go to the [Error messages issue](https://github.com/lampepfl/dotty/issues/1589)
+1. Go to the [Error messages issue](https://github.com/scala/scala3/issues/1589)
 2. Read the howto on error messages
 3. Choose an error message you want to help with and post a comment saying
    which one(s)
diff --git a/_posts/2016-12-07-implicit-function-types.md b/_posts/2016-12-07-implicit-function-types.md
index ea7017b61..c71dbc655 100644
--- a/_posts/2016-12-07-implicit-function-types.md
+++ b/_posts/2016-12-07-implicit-function-types.md
@@ -5,7 +5,7 @@ by: Martin Odersky
 isHighlight: true
 ---
 
-I just made the [first pull request](https://github.com/lampepfl/dotty/pull/1775) to add _implicit function types_ to
+I just made the [first pull request](https://github.com/scala/scala3/pull/1775) to add _implicit function types_ to
 Scala. I am pretty excited about it, because - citing the explanation
 of the pull request - "_This is the first step to bring contextual
 abstraction to Scala_". What do I mean by this?
@@ -180,7 +180,7 @@ type of `f1` is:
 
 Just like the normal function type syntax `A => B`, desugars to `scala.Function1[A, B]`
 the implicit function type syntax `implicit A => B` desugars to `scala.ImplicitFunction1[A, B]`.
-The same holds at other function arities. With dotty's [pull request #1758](https://github.com/lampepfl/dotty/pull/1758)
+The same holds at other function arities. With dotty's [pull request #1758](https://github.com/scala/scala3/pull/1758)
 merged there is no longer an upper limit of 22 for such functions.
 
 The type `ImplicitFunction1` can be thought of being defined as follows:
diff --git a/_posts/2017-02-28-collections-rework.md b/_posts/2017-02-28-collections-rework.md
index 4e960d24a..a8f81a07d 100644
--- a/_posts/2017-02-28-collections-rework.md
+++ b/_posts/2017-02-28-collections-rework.md
@@ -4,7 +4,7 @@ by: Stefan Zeiger
 title: Scala 2.13 Collections Rework
 ---
 
-In October of 2015 Martin Odersky [asked for strawman proposals](https://github.com/lampepfl/dotty/issues/818) for a new collections library design for Scala 2.13, which eventually led to the project that we are currently working on, based on his latest proposal. This was not the first redesign for the Scala collections. The [current design](https://docs.scala-lang.org/overviews/core/architecture-of-scala-collections.html) was first implemented in Scala 2.8 along with the required improvements to type inference in the Scala compiler. It can generally be considered a success, providing powerful and flexible abstractions that bring together immutable and mutable collections, both sequential and parallel, with a high amount of shared interfaces and implementations. However, it does exhibit some symptoms of [second-system syndrome](https://en.wikipedia.org/wiki/Second-system_effect) that have been problematic in practice.
+In October of 2015 Martin Odersky [asked for strawman proposals](https://github.com/scala/scala3/issues/818) for a new collections library design for Scala 2.13, which eventually led to the project that we are currently working on, based on his latest proposal. This was not the first redesign for the Scala collections. The [current design](https://docs.scala-lang.org/overviews/core/architecture-of-scala-collections.html) was first implemented in Scala 2.8 along with the required improvements to type inference in the Scala compiler. It can generally be considered a success, providing powerful and flexible abstractions that bring together immutable and mutable collections, both sequential and parallel, with a high amount of shared interfaces and implementations. However, it does exhibit some symptoms of [second-system syndrome](https://en.wikipedia.org/wiki/Second-system_effect) that have been problematic in practice.
 
 ## Goals
 
diff --git a/_posts/2017-12-01-fifth-dotty-milestone-release.md b/_posts/2017-12-01-fifth-dotty-milestone-release.md
index e0e4be59c..fd09b1632 100644
--- a/_posts/2017-12-01-fifth-dotty-milestone-release.md
+++ b/_posts/2017-12-01-fifth-dotty-milestone-release.md
@@ -24,7 +24,7 @@ support for Scala 2.12 and came with a brand new REPL.
 
 ## What’s new in the 0.5.0-RC1 technology preview?
 
-### Reworked implicit search [#3421](https://github.com/lampepfl/dotty/pull/3421)
+### Reworked implicit search [#3421](https://github.com/scala/scala3/pull/3421)
 The treatment of ambiguity errors has changed. If an ambiguity is encountered
 in some recursive step of an implicit search, the ambiguity is propagated to the caller.
 Example: Say you have the following definitions:
@@ -55,7 +55,7 @@ techniques no longer work. But there is now a new special type `scala.implicits.
 implements negation directly. For any query type `Q`: `Not[Q]` succeeds if and only if the
 implicit search for `Q` fails.
 
-### Dependent function types [#3464](https://github.com/lampepfl/dotty/pull/3464)
+### Dependent function types [#3464](https://github.com/scala/scala3/pull/3464)
 A dependent function type describes functions where the result type may depend
 on the function's parameter values. Example:
 
@@ -107,7 +107,7 @@ are currently two backends using the TASTY frontend:
    This is the first step toward linking and whole world optimisations, recompiling code to a
    different backends...
 
-### Generic java signatures [#3234](https://github.com/lampepfl/dotty/pull/3234)
+### Generic java signatures [#3234](https://github.com/scala/scala3/pull/3234)
 Dotty now emits generic signatures for classes and methods. Theses signatures are used by compilers,
 debuggers and to support runtime reflection. For example:
 
@@ -141,7 +141,7 @@ the IDE sections of the <a href="https://docs.scala-lang.org/scala3/getting-star
 ### Standalone installation
 Releases are available for download on the _Releases_
 section of the Dotty repository:
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases)
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases)
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running:
 
@@ -158,7 +158,7 @@ brew upgrade dotty
 ## Let us know what you think!
 If you have questions or any sort of feedback, feel free to send us a message on our
 [Gitter channel](https://gitter.im/lampepfl/dotty). If you encounter a bug, please
-[open an issue on GitHub](https://github.com/lampepfl/dotty/issues/new).
+[open an issue on GitHub](https://github.com/scala/scala3/issues/new).
 
 ## Contributing
 Thank you to all the contributors who made this release possible!
@@ -195,7 +195,7 @@ According to `git shortlog -sn --no-merges 0.4.0-RC1..0.5.0-RC1` these are:
 If you want to get your hands dirty and contribute to Dotty, now is a good time to get involved!
 You can have a look at our [Getting Started page for new contributors](https://dotty.epfl.ch/docs/contributing/getting-started.html),
 the [Awesome Error Messages](https://scala-lang.org/blog/2016/10/14/dotty-errors.html) project or some of
-the simple [Dotty issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
+the simple [Dotty issues](https://github.com/scala/scala3/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
 They make perfect entry-points into hacking on the compiler.
 
 We are looking forward to having you join the team of contributors.
diff --git a/_posts/2019-12-18-road-to-scala-3.md b/_posts/2019-12-18-road-to-scala-3.md
index 37220f9ff..1e6756278 100644
--- a/_posts/2019-12-18-road-to-scala-3.md
+++ b/_posts/2019-12-18-road-to-scala-3.md
@@ -167,7 +167,7 @@ If you don't have time to do a cross-build yourself, consider asking your users
 
 #### Working on Scala itself
 
-The Dotty team welcomes contributors, including first-time Scala contributors.  Scala 3 has already benefited considerably from years of active external participation [on GitHub](https://github.com/lampepfl/dotty). For guidance and getting-started help, there is an active [chat room on Gitter](https://gitter.im/lampepfl/dotty).  There are many ways to be helpful that don't require large time outlays or a background in compiler hacking.
+The Dotty team welcomes contributors, including first-time Scala contributors.  Scala 3 has already benefited considerably from years of active external participation [on GitHub](https://github.com/scala/scala3). For guidance and getting-started help, there is an active [chat room on Gitter](https://gitter.im/lampepfl/dotty).  There are many ways to be helpful that don't require large time outlays or a background in compiler hacking.
 
 If you are already a Scala 2 contributor, you are welcome to move to the new repo, but you might also choose to stay focused on Scala 2 for now if you prefer. Scala 2 will be maintained for several more years, and many kinds of improvements remain possible and desirable in the 2.13 series, subject to the usual compatibility constraints.  Standard library fixes are directly applicable to both versions; back end improvements benefit both compilers; improved linting could help Scala 2 users get their codebases ready for 3.
 
diff --git a/_posts/2020-02-20-community-build.md b/_posts/2020-02-20-community-build.md
index 221fde99f..c0163591d 100644
--- a/_posts/2020-02-20-community-build.md
+++ b/_posts/2020-02-20-community-build.md
@@ -134,8 +134,8 @@ And what about Scala 3?  Dotty has its own community build,
 and it continues to grow. It now contains 25 repos, compared to 5
 a year ago.
 
-Here is the [list of included repos](https://github.com/lampepfl/dotty/tree/master/community-build/community-projects).  If you want to add something,
-there are [instructions](https://github.com/lampepfl/dotty/tree/master/community-build/test/scala/dotty/communitybuild).
+Here is the [list of included repos](https://github.com/scala/scala3/tree/main/community-build/community-projects).  If you want to add something,
+there are [instructions](https://github.com/scala/scala3/tree/main/community-build/test/scala/dotty/communitybuild).
 
 ## Credits
 
diff --git a/_posts/2021-02-26-tuples-bring-generic-programming-to-scala-3.md b/_posts/2021-02-26-tuples-bring-generic-programming-to-scala-3.md
index 88eedefd5..f3b034cf8 100644
--- a/_posts/2021-02-26-tuples-bring-generic-programming-to-scala-3.md
+++ b/_posts/2021-02-26-tuples-bring-generic-programming-to-scala-3.md
@@ -332,5 +332,5 @@ instead of `concat((1, 2), (3, 4))`, similarly to how we implemented `*:`.
 
 We can use the same approach for other functions on tuples, I invite you to
 have a look at the [source code of the standard
-library](https://github.com/lampepfl/dotty/blob/87102a0b182849c71f61a6febe631f767bcc72c3/library/src-bootstrapped/scala/Tuple.scala)
+library](https://github.com/scala/scala3/blob/87102a0b182849c71f61a6febe631f767bcc72c3/library/src-bootstrapped/scala/Tuple.scala)
 to see how the other operators are implemented.
diff --git a/_posts/2023-02-01-release-notes-3.2.2.md b/_posts/2023-02-01-release-notes-3.2.2.md
index ceb8a52b5..25e28fce8 100644
--- a/_posts/2023-02-01-release-notes-3.2.2.md
+++ b/_posts/2023-02-01-release-notes-3.2.2.md
@@ -3,7 +3,7 @@ category: announcement
 permalink: /news/3.2.2
 title: "Scala 3.2.2 is now available!"
 ---
-[Scala 3.2.2](https://github.com/lampepfl/dotty/releases/tag/3.2.2) is now available!
+[Scala 3.2.2](https://github.com/scala/scala3/releases/tag/3.2.2) is now available!
 
 This version not only fixes bugs but also brings two new flags:
 
diff --git a/_posts/2023-07-17-signature-polymorphic-methods.md b/_posts/2023-07-17-signature-polymorphic-methods.md
index c37f33a54..652546d7b 100644
--- a/_posts/2023-07-17-signature-polymorphic-methods.md
+++ b/_posts/2023-07-17-signature-polymorphic-methods.md
@@ -194,7 +194,7 @@ overloaded, with each individual overload only being brought into
 existence as needed.
 
 For details, see [the pull
-request](https://github.com/lampepfl/dotty/pull/16225).
+request](https://github.com/scala/scala3/pull/16225).
 
 ### The path not taken
 
diff --git a/_posts/2023-09-07-release-notes-3.3.1.md b/_posts/2023-09-07-release-notes-3.3.1.md
index 78188b617..72b855a7b 100644
--- a/_posts/2023-09-07-release-notes-3.3.1.md
+++ b/_posts/2023-09-07-release-notes-3.3.1.md
@@ -3,7 +3,7 @@ category: announcement
 permalink: /news/3.3.1
 title: "Scala 3.3.1 LTS is now available!"
 ---
-[Scala 3.3.1 LTS](https://github.com/lampepfl/dotty/releases/tag/3.3.1) is now available!
+[Scala 3.3.1 LTS](https://github.com/scala/scala3/releases/tag/3.3.1) is now available!
 
 This version adds support for records in Java dependencies of Scala projects. It also brings improvements to the bytecode generation and a new linting rule: `-Wnonunit-statement`.
 
diff --git a/blog/_posts/2017-05-31-first-dotty-milestone-release.md b/blog/_posts/2017-05-31-first-dotty-milestone-release.md
index cb1d8a43b..03e9f21d4 100644
--- a/blog/_posts/2017-05-31-first-dotty-milestone-release.md
+++ b/blog/_posts/2017-05-31-first-dotty-milestone-release.md
@@ -47,7 +47,7 @@ using Dotty with sbt, see the
 
 Releases are available for download on the _Releases_
 section of the Dotty repository: 
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases).
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases).
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running
 
@@ -92,9 +92,9 @@ At the end of 6 weeks, the milestone will be promoted to a stable release.
 
 Over the coming weeks and months, we plan to work on the following topics:
 
- - [Integrate Local optimizations developed in Dotty linker](https://github.com/lampepfl/dotty/pull/2513);
- - [Add Language-level support for HMaps and HLists](https://github.com/lampepfl/dotty/pull/2199);
- - [Port global optimizations from Dotty linker](https://github.com/lampepfl/dotty/pull/1840).
+ - [Integrate Local optimizations developed in Dotty linker](https://github.com/scala/scala3/pull/2513);
+ - [Add Language-level support for HMaps and HLists](https://github.com/scala/scala3/pull/2199);
+ - [Port global optimizations from Dotty linker](https://github.com/scala/scala3/pull/1840).
 
 If you want to get your hands dirty with any of this, now is a good
 moment to get involved! Join the team of contributors, including
@@ -115,7 +115,7 @@ Join our [community build](https://github.com/lampepfl/dotty-community-build)
  to make sure that our regression suite includes your library.
 
 
-To get started, see <https://github.com/lampepfl/dotty>.
+To get started, see <https://github.com/scala/scala3>.
 
 
 [Scastie]: https://scastie.scala-lang.org/R5kUfVbTRpmS4l4CrO1HlA
diff --git a/blog/_posts/2017-07-12-second-dotty-milestone-release.md b/blog/_posts/2017-07-12-second-dotty-milestone-release.md
index 670fdd955..3bc494f1c 100644
--- a/blog/_posts/2017-07-12-second-dotty-milestone-release.md
+++ b/blog/_posts/2017-07-12-second-dotty-milestone-release.md
@@ -35,52 +35,52 @@ The [previous technology preview](/blog/2017/05/31/first-dotty-milestone-release
 
 This technology preview is geared towards improving stability and reliability. It includes:
 
-  - [Local optimizations upstreamed from the Dotty Linker](https://github.com/lampepfl/dotty/pull/2513), [2647](https://github.com/lampepfl/dotty/pull/2647) by ([@OlivierBlanvillain](https://github.com/OlivierBlanvillain)). See more details below.
-  - [Optimizing Pattern Matcher](https://github.com/lampepfl/dotty/pull/2829) by ([@odersky](https://github.com/odersky))
-  - [Idempotency checks](https://github.com/lampepfl/dotty/pull/2756) are the first step to reproducible builds
-  - [Faster Base class sets](https://github.com/lampepfl/dotty/pull/2676) by ([@odersky](https://github.com/odersky)) and ([@darkdimius](https://twitter.com/darkdimius)) 
+  - [Local optimizations upstreamed from the Dotty Linker](https://github.com/scala/scala3/pull/2513), [2647](https://github.com/scala/scala3/pull/2647) by ([@OlivierBlanvillain](https://github.com/OlivierBlanvillain)). See more details below.
+  - [Optimizing Pattern Matcher](https://github.com/scala/scala3/pull/2829) by ([@odersky](https://github.com/odersky))
+  - [Idempotency checks](https://github.com/scala/scala3/pull/2756) are the first step to reproducible builds
+  - [Faster Base class sets](https://github.com/scala/scala3/pull/2676) by ([@odersky](https://github.com/odersky)) and ([@darkdimius](https://twitter.com/darkdimius)) 
   - Numerous fixes to IDE and Dotty Language Server covering:
    
-     - [Windows support for VS Code plugin](https://github.com/lampepfl/dotty/pull/2776)
-     - [Fix hover-on-type for implicitly converted expressions](https://github.com/lampepfl/dotty/pull/2836)
-     - [Fixes to find all references in external projects](https://github.com/lampepfl/dotty/pull/2810), [2773](https://github.com/lampepfl/dotty/pull/2773/files)
-     - [Fix conflict with  dragos-vscode-scala](https://github.com/lampepfl/dotty/pull/2777)
-     - [Fix ide crash on non-parsable file](https://github.com/lampepfl/dotty/pull/2752)
-     - [Fix hover functionality for enum classes](https://github.com/lampepfl/dotty/pull/2722)
-     - [Report errors on Dotty Language Server initialization](https://github.com/lampepfl/dotty/pull/2708)
-     - [Fixes to sbt setting up Dotty IDE](https://github.com/lampepfl/dotty/pull/2690)
-     - General stability improvements [2838](https://github.com/lampepfl/dotty/pull/2838), [2787](https://github.com/lampepfl/dotty/pull/2787), [2692](https://github.com/lampepfl/dotty/pull/2692)
+     - [Windows support for VS Code plugin](https://github.com/scala/scala3/pull/2776)
+     - [Fix hover-on-type for implicitly converted expressions](https://github.com/scala/scala3/pull/2836)
+     - [Fixes to find all references in external projects](https://github.com/scala/scala3/pull/2810), [2773](https://github.com/scala/scala3/pull/2773/files)
+     - [Fix conflict with  dragos-vscode-scala](https://github.com/scala/scala3/pull/2777)
+     - [Fix ide crash on non-parsable file](https://github.com/scala/scala3/pull/2752)
+     - [Fix hover functionality for enum classes](https://github.com/scala/scala3/pull/2722)
+     - [Report errors on Dotty Language Server initialization](https://github.com/scala/scala3/pull/2708)
+     - [Fixes to sbt setting up Dotty IDE](https://github.com/scala/scala3/pull/2690)
+     - General stability improvements [2838](https://github.com/scala/scala3/pull/2838), [2787](https://github.com/scala/scala3/pull/2787), [2692](https://github.com/scala/scala3/pull/2692)
      
   - Scalac compatibility improvements:
   
-     - [Support Scala 2.12 traits](https://github.com/lampepfl/dotty/pull/2685)
-     - [Fixes to handling of Scala 2 classfiles](https://github.com/lampepfl/dotty/pull/2834/files)
-     - [Scalac parser crashes on Dotty.jar](https://github.com/lampepfl/dotty/pull/2719)
+     - [Support Scala 2.12 traits](https://github.com/scala/scala3/pull/2685)
+     - [Fixes to handling of Scala 2 classfiles](https://github.com/scala/scala3/pull/2834/files)
+     - [Scalac parser crashes on Dotty.jar](https://github.com/scala/scala3/pull/2719)
   
   - Java compatibility improvements:
   
-     - [Fixes to handing of Java generic signatures](https://github.com/lampepfl/dotty/pull/2831)
-     - [java.lang.System.out is final but that's a lie](https://github.com/lampepfl/dotty/pull/2781)
+     - [Fixes to handing of Java generic signatures](https://github.com/scala/scala3/pull/2831)
+     - [java.lang.System.out is final but that's a lie](https://github.com/scala/scala3/pull/2781)
       
   - Improved error messages:
      
-     - [Nicer error message for "implicit function type needs non-empty parameter list"](https://github.com/lampepfl/dotty/pull/2821)
-     - [Nicer error message for nonsensical modifier combination](https://github.com/lampepfl/dotty/pull/2807/files), [2747](https://github.com/lampepfl/dotty/pull/2747)
-     - [Nicer error message for supercall inside @inline method](https://github.com/lampepfl/dotty/pull/2740)
-     - [Check that case classes don't inherit case classes](https://github.com/lampepfl/dotty/pull/2790)
-     - [Check that named parameters don't conflict with positional ones](https://github.com/lampepfl/dotty/pull/2785)
+     - [Nicer error message for "implicit function type needs non-empty parameter list"](https://github.com/scala/scala3/pull/2821)
+     - [Nicer error message for nonsensical modifier combination](https://github.com/scala/scala3/pull/2807/files), [2747](https://github.com/scala/scala3/pull/2747)
+     - [Nicer error message for supercall inside @inline method](https://github.com/scala/scala3/pull/2740)
+     - [Check that case classes don't inherit case classes](https://github.com/scala/scala3/pull/2790)
+     - [Check that named parameters don't conflict with positional ones](https://github.com/scala/scala3/pull/2785)
 
   - Improved command line handling:
   
-     - [Support params in a file like @file.txt](https://github.com/lampepfl/dotty/pull/2765)
+     - [Support params in a file like @file.txt](https://github.com/scala/scala3/pull/2765)
    
   - Type system stability:
      
-     - [Handle wildcard types in unions and intersections](https://github.com/lampepfl/dotty/pull/2742) 
+     - [Handle wildcard types in unions and intersections](https://github.com/scala/scala3/pull/2742) 
 
   - Fixes to implicit search:
     
-     - [Fix shadowing of higher order implicits](https://github.com/lampepfl/dotty/pull/2739)
+     - [Fix shadowing of higher order implicits](https://github.com/scala/scala3/pull/2739)
 
     
 ### Better generated code:
@@ -314,7 +314,7 @@ using Dotty with sbt, see the
 
 Releases are available for download on the _Releases_
 section of the Dotty repository:
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases)
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases)
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running:
 
@@ -339,10 +339,10 @@ You can try it out there without installing anything.
 
 Over the coming weeks and months, we plan to work on the following topics:
 
- - [Add support for using Dotty generated classes with Scala 2.12](https://github.com/lampepfl/dotty/pull/2827)
- - [Add Language-level support for HMaps and HLists](https://github.com/lampepfl/dotty/pull/2199);
+ - [Add support for using Dotty generated classes with Scala 2.12](https://github.com/scala/scala3/pull/2827)
+ - [Add Language-level support for HMaps and HLists](https://github.com/scala/scala3/pull/2199);
  - Upstream more optimizations from Dotty Linker
- - [Add support for existing in the same classpath with Scala 2.12](https://github.com/lampepfl/dotty/pull/2827)
+ - [Add support for existing in the same classpath with Scala 2.12](https://github.com/scala/scala3/pull/2827)
 
 If you want to get your hands dirty with any of this, now is a good
 moment to get involved! Join the team of contributors, including
@@ -363,7 +363,7 @@ Join our [community build](https://github.com/lampepfl/dotty-community-build)
  to make sure that our regression suite includes your library.
 
 
-To get started, see [https://github.com/lampepfl/dotty](https://github.com/lampepfl/dotty).
+To get started, see [https://github.com/scala/scala3](https://github.com/scala/scala3).
 
 
 [Scastie]: https://scastie.scala-lang.org/R5kUfVbTRpmS4l4CrO1HlA
diff --git a/blog/_posts/2017-09-07-third-dotty-milestone-release.md b/blog/_posts/2017-09-07-third-dotty-milestone-release.md
index 8163c57b3..f9f383a72 100644
--- a/blog/_posts/2017-09-07-third-dotty-milestone-release.md
+++ b/blog/_posts/2017-09-07-third-dotty-milestone-release.md
@@ -30,12 +30,12 @@ stability and reliability:
 ## What’s in the 0.3.0-RC2 technology preview?
 This technology preview further improves stability and reliability. Some highlighted PRs are:
  - IDE bug fixes:
- [#2986](https://github.com/lampepfl/dotty/pull/2986),
- [#2932](https://github.com/lampepfl/dotty/pull/2932),
- [#2885](https://github.com/lampepfl/dotty/pull/2885),
- [#2876](https://github.com/lampepfl/dotty/pull/2876),
- [#2870](https://github.com/lampepfl/dotty/pull/2870),
- [#2872](https://github.com/lampepfl/dotty/pull/2872) by [@odersky] and [@smarter].
+ [#2986](https://github.com/scala/scala3/pull/2986),
+ [#2932](https://github.com/scala/scala3/pull/2932),
+ [#2885](https://github.com/scala/scala3/pull/2885),
+ [#2876](https://github.com/scala/scala3/pull/2876),
+ [#2870](https://github.com/scala/scala3/pull/2870),
+ [#2872](https://github.com/scala/scala3/pull/2872) by [@odersky] and [@smarter].
 
 
 ## How can you try it out?
@@ -62,7 +62,7 @@ using Dotty with sbt, see the
 ### Standalone installation
 Releases are available for download on the _Releases_
 section of the Dotty repository:
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases)
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases)
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running:
 
@@ -84,16 +84,16 @@ You can try it out there without installing anything.
 ## What are the next steps?
 Over the coming weeks and months, we plan to work on the following topics:
 
- - [Add support for using Dotty generated classes with Scala 2.12](https://github.com/lampepfl/dotty/pull/2827)
- - [Add Language-level support for HMaps and HLists](https://github.com/lampepfl/dotty/pull/2199);
+ - [Add support for using Dotty generated classes with Scala 2.12](https://github.com/scala/scala3/pull/2827)
+ - [Add Language-level support for HMaps and HLists](https://github.com/scala/scala3/pull/2199);
  - Upstream more optimizations from Dotty Linker
- - [Add support for existing in the same classpath with Scala 2.12](https://github.com/lampepfl/dotty/pull/2827)
- - [Add native Dotty REPL](https://github.com/lampepfl/dotty/pull/2991)
+ - [Add support for existing in the same classpath with Scala 2.12](https://github.com/scala/scala3/pull/2827)
+ - [Add native Dotty REPL](https://github.com/scala/scala3/pull/2991)
 
 ## Questions / Reporting Bugs
 If you have questions or any sort of feedback, feel free to send us a message on our
 [Gitter channel](https://gitter.im/lampepfl/dotty). If you encounter a bug, please
-[open an issue on GitHub](https://github.com/lampepfl/dotty/issues/new).
+[open an issue on GitHub](https://github.com/scala/scala3/issues/new).
 
 ## Contributing
 Thank you to all the contributors who made this release possible!
@@ -119,7 +119,7 @@ According to `git shortlog -sn --no-merges 0.2.0-RC1..0.3.0-RC2` these are:
 If you want to get your hands dirty with any of this, now is a good moment to get involved!
 You can have a look at our [Getting Started page](https://dotty.epfl.ch/docs/contributing/getting-started.html),
 our [Awesome Error Messages](https://scala-lang.org/blog/2016/10/14/dotty-errors.html) or some of
-the simple [Dotty issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
+the simple [Dotty issues](https://github.com/scala/scala3/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
 They make perfect entry-points into hacking on the compiler.
 
 We are looking forward to having you join the team of contributors.
@@ -132,7 +132,7 @@ Join our [community build](https://github.com/lampepfl/dotty-community-build)
 to make sure that our regression suite includes your library.
 
 
-To get started, see [https://github.com/lampepfl/dotty](https://github.com/lampepfl/dotty).
+To get started, see [https://github.com/scala/scala3](https://github.com/scala/scala3).
 
 
 [Scastie]: https://scastie.scala-lang.org/?target=dotty
diff --git a/blog/_posts/2017-10-16-fourth-dotty-milestone-release.md b/blog/_posts/2017-10-16-fourth-dotty-milestone-release.md
index 167119a93..86cce0f73 100644
--- a/blog/_posts/2017-10-16-fourth-dotty-milestone-release.md
+++ b/blog/_posts/2017-10-16-fourth-dotty-milestone-release.md
@@ -24,14 +24,14 @@ stability and reliability.
 
 ## What’s new in the 0.4.0-RC1 technology preview?
 
-### Rewritten REPL [#2991](https://github.com/lampepfl/dotty/pull/2991)
+### Rewritten REPL [#2991](https://github.com/scala/scala3/pull/2991)
 The original Dotty REPL was a proof of concept hacked together
 from
-[an ancient version of the scalac REPL](https://github.com/lampepfl/dotty/pull/1082#issuecomment-183905504).
+[an ancient version of the scalac REPL](https://github.com/scala/scala3/pull/1082#issuecomment-183905504).
 It worked by creating Scala source files from the user input using string
 concatenation, this made it easy to adapt it for Dotty since it did not rely on
 the internals of scalac, but it was also fragile and hard to reason about.
-The [new REPL](https://github.com/lampepfl/dotty/pull/2991) instead works by
+The [new REPL](https://github.com/scala/scala3/pull/2991) instead works by
 manipulating ASTs (Abstract Syntax Trees), this is more robust and will make it
 easier to develop new features: we have already implemented auto-completion
 support (by reusing the APIs we had created for
@@ -42,7 +42,7 @@ Note that the user interface of the REPL has not changed: like in the old REPL
 we use code adapted from the [Ammonite REPL](https://ammonite.io/#Ammonite-REPL)
 to provide syntax highlighting, multi-line editing, history, etc.
 
-### Scala 2.12 support [#2827](https://github.com/lampepfl/dotty/pull/2827)
+### Scala 2.12 support [#2827](https://github.com/scala/scala3/pull/2827)
 Since our first release, it has been possible to use Scala 2 libraries in a
 Dotty project as explained in the
 [dotty-example-project](https://github.com/smarter/dotty-example-project#getting-your-project-to-compile-with-dotty).
@@ -82,7 +82,7 @@ the IDE guide.
 ### Standalone installation
 Releases are available for download on the _Releases_
 section of the Dotty repository:
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases)
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases)
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running:
 
@@ -99,7 +99,7 @@ brew upgrade dotty
 ## Let us know what you think!
 If you have questions or any sort of feedback, feel free to send us a message on our
 [Gitter channel](https://gitter.im/lampepfl/dotty). If you encounter a bug, please
-[open an issue on GitHub](https://github.com/lampepfl/dotty/issues/new).
+[open an issue on GitHub](https://github.com/scala/scala3/issues/new).
 
 ## Contributing
 Thank you to all the contributors who made this release possible!
@@ -131,7 +131,7 @@ According to `git shortlog -sn --no-merges 0.3.0-RC2..0.4.0-RC1` these are:
 If you want to get your hands dirty and contribute to Dotty, now is a good time to get involved!
 You can have a look at our [Getting Started page for new contributors](https://dotty.epfl.ch/docs/contributing/getting-started.html),
 the [Awesome Error Messages](https://scala-lang.org/blog/2016/10/14/dotty-errors.html) project or some of
-the simple [Dotty issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
+the simple [Dotty issues](https://github.com/scala/scala3/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
 They make perfect entry-points into hacking on the compiler.
 
 We are looking forward to having you join the team of contributors.
@@ -142,7 +142,7 @@ snapshot. Currently this includes ScalaPB, algebra, scalatest, scopt and squants
 Join our [community build](https://github.com/lampepfl/dotty-community-build)
 to make sure that our regression suite includes your library.
 
-To get started, see [https://github.com/lampepfl/dotty](https://github.com/lampepfl/dotty).
+To get started, see [https://github.com/scala/scala3](https://github.com/scala/scala3).
 
 
 [Scastie]: https://scastie.scala-lang.org/?target=dotty
diff --git a/blog/_posts/2018-04-19-scala-3.md b/blog/_posts/2018-04-19-scala-3.md
index 6177e21ff..d2839e674 100644
--- a/blog/_posts/2018-04-19-scala-3.md
+++ b/blog/_posts/2018-04-19-scala-3.md
@@ -6,7 +6,7 @@ title: "Towards Scala 3"
 ---
 
 Now that Scala 2.13 is only a few months away, it's time to consider the
-roadmap beyond it. It's been no secret that the work on [Dotty](https://github.com/lampepfl/dotty) over the
+roadmap beyond it. It's been no secret that the work on [Dotty](https://github.com/scala/scala3) over the
 last 5 years was intended to explore what a new Scala could look
 like. We are now at a stage where we can commit: Dotty will become
 Scala 3.0.
@@ -102,7 +102,7 @@ about that issue.
 ### How can I help?
 
 Scala 3 is developed completely in the open at
-[https://github.com/lampepfl/dotty](https://github.com/lampepfl/dotty).
+[https://github.com/scala/scala3](https://github.com/scala/scala3).
 Get involved there, by fixing and
 opening issues, making pull requests, and participating in the
 discussions.
diff --git a/blog/_posts/2018-04-30-in-a-nutshell.md b/blog/_posts/2018-04-30-in-a-nutshell.md
index c402f959f..6ce507f26 100644
--- a/blog/_posts/2018-04-30-in-a-nutshell.md
+++ b/blog/_posts/2018-04-30-in-a-nutshell.md
@@ -40,7 +40,7 @@ very interesting possibilities to pursue in the future.
 
 OK, but what is Tasty _exactly_? An up-to-date version of the Tasty
 file format is described in file
-[TastyFormat.scala](https://github.com/lampepfl/dotty/blob/master/tasty/src/dotty/tools/tasty/TastyFormat.scala)
+[TastyFormat.scala](https://github.com/scala/scala3/blob/master/tasty/src/dotty/tools/tasty/TastyFormat.scala)
 of the `dotc` compiler for Scala 3.
 
 ## What Does Tasty Have to Do with Macros?
@@ -120,7 +120,7 @@ compiler frontend!
 
 ## Next Steps
 
-The next step, [currently under way](https://github.com/lampepfl/dotty/pull/4279), is to connect these definitions to the Tasty file format. We do this by rewriting them as
+The next step, [currently under way](https://github.com/scala/scala3/pull/4279), is to connect these definitions to the Tasty file format. We do this by rewriting them as
 [extractors](https://docs.scala-lang.org/tour/extractor-objects.html)
 that implement each data type in terms of the data structures used by
 the `dotc` compiler which are then pickled and unpickled in the Tasty
@@ -170,7 +170,7 @@ driven by the annotation happens after type checking.
 
 We believe the lack of whitebox macros can be alleviated to some degree by having
 more expressive forms of computed types. A sketch of such as system is outlined
-in [Dotty PR 3844](https://github.com/lampepfl/dotty/pull/3844).
+in [Dotty PR 3844](https://github.com/scala/scala3/pull/3844).
 
 The Scala 3 language will also directly incorporate some constructs
 that so far required advanced macro code to define. In particular:
@@ -194,5 +194,5 @@ The future Scala 3 macro design is intended to replace the existing def macros a
 What do you think of the macro roadmap? To discuss, there's a [thread](https://contributors.scala-lang.org/t/what-kinds-of-macros-should-scala-3-support/1850) on
 [Scala Contributors](https://contributors.scala-lang.org). Your feedback
 there will be very valuable. There is also lots of scope to shape the
-future by contributing to the development in the [Dotty](https://github.com/lampepfl/dotty) repo.
+future by contributing to the development in the [Dotty](https://github.com/scala/scala3) repo.
 
diff --git a/blog/_posts/2020-12-15-scala-3-crossing-the-finish-line.md b/blog/_posts/2020-12-15-scala-3-crossing-the-finish-line.md
index e47816f9c..abf151b80 100644
--- a/blog/_posts/2020-12-15-scala-3-crossing-the-finish-line.md
+++ b/blog/_posts/2020-12-15-scala-3-crossing-the-finish-line.md
@@ -27,7 +27,7 @@ _All Scala Users_
 _Contributors (authors and maintainers)_
 
 * Share your opinion on [Contributors forum](https://contributors.scala-lang.org/) (any topic that you deem important)
-* Get involved on the [Scala 3 repo](https://github.com/lampepfl/dotty/)
+* Get involved on the [Scala 3 repo](https://github.com/scala/scala3/)
 
 _Companies and organizations who are trying out Scala 3_
 
diff --git a/blog/_posts/2021-05-14-scala3-is-here.md b/blog/_posts/2021-05-14-scala3-is-here.md
index cc3bcd7de..6af907692 100644
--- a/blog/_posts/2021-05-14-scala3-is-here.md
+++ b/blog/_posts/2021-05-14-scala3-is-here.md
@@ -36,7 +36,7 @@ Of course, we intend to continue the development of the language in ways other t
 
 Scala 3 now has a set of widely-used community libraries that are built against every nightly Scala 3
 snapshot. At present, there are 67 projects included, and the number is growing rapidly.
-Join our [community build](https://github.com/lampepfl/dotty/tree/master/community-build)
+Join our [community build](https://github.com/scala/scala3/tree/main/community-build)
 to make sure that our regression suite includes your library.
 
 ## Contributors
diff --git a/blog/_posts/2021-07-21-scala-3.0.2RC1-is-here.md b/blog/_posts/2021-07-21-scala-3.0.2RC1-is-here.md
index e5ea7fc8e..7f35d40f5 100644
--- a/blog/_posts/2021-07-21-scala-3.0.2RC1-is-here.md
+++ b/blog/_posts/2021-07-21-scala-3.0.2RC1-is-here.md
@@ -7,7 +7,7 @@ title: Scala 3.0.1 and 3.0.2-RC1 are here!
 
 Greetings from the Scala 3 team! We are glad to announce that Scala 3.0.1 and 3.0.2-RC1 are now officially out.
 
-As no critical bugs have been found in the previously released Scala 3.0.1-RC2, it has been promoted to 3.0.1. It is the first stable release after 3.0.0 and it incorporates the changes described in detail in the articles for its pre-releases: [3.0.1-RC1](https://dotty.epfl.ch/blog/2021/06/07/scala3.0.1-rc1-release.html) and [3.0.1-RC2](https://dotty.epfl.ch/blog/2021/06/25/scala301-rc2.html). The unified changelog can be found [here](https://github.com/lampepfl/dotty/releases/tag/3.0.1).
+As no critical bugs have been found in the previously released Scala 3.0.1-RC2, it has been promoted to 3.0.1. It is the first stable release after 3.0.0 and it incorporates the changes described in detail in the articles for its pre-releases: [3.0.1-RC1](https://dotty.epfl.ch/blog/2021/06/07/scala3.0.1-rc1-release.html) and [3.0.1-RC2](https://dotty.epfl.ch/blog/2021/06/25/scala301-rc2.html). The unified changelog can be found [here](https://github.com/scala/scala3/releases/tag/3.0.1).
 
 Scala 3.0.2-RC1, in turn, incorporates new language improvements and bug fixes described below.
 
@@ -17,7 +17,7 @@ You can expect the release of stable 3.0.2 and a release candidate for a the nex
 
 Scala 3's indentation based syntax is aimed at making your code more concise and readable. As it gets broader adoption, we consistently improve its specification to eliminate corner cases which might lead to ambiguities or counterintuitive behaviours.
 
-Thanks to [#12801](https://github.com/lampepfl/dotty/pull/12801) it is now allowed for a logical expression in an `if` statement or expression to continue in the following line if it starts in the same line as the `if` keyword, e.g.
+Thanks to [#12801](https://github.com/scala/scala3/pull/12801) it is now allowed for a logical expression in an `if` statement or expression to continue in the following line if it starts in the same line as the `if` keyword, e.g.
 
 ```scala
 if foo
@@ -61,7 +61,7 @@ def foo[T <: Matchable](t: T) = t match { case null => () }
 
 ## Method search by type signature
 
-You can now browse the documentation of Scala's API not only by names of methods but also by their type in a [Hoogle](https://hoogle.haskell.org)-like manner (but with Scala syntax) thanks to integration with [Inkuire](https://github.com/VirtusLab/Inkuire) brought up by [#12375](https://github.com/lampepfl/dotty/pull/12375).
+You can now browse the documentation of Scala's API not only by names of methods but also by their type in a [Hoogle](https://hoogle.haskell.org)-like manner (but with Scala syntax) thanks to integration with [Inkuire](https://github.com/VirtusLab/Inkuire) brought up by [#12375](https://github.com/scala/scala3/pull/12375).
 
 To find methods with the desired signature simply write in scaladoc's searchbar the type you would expect them to have after eta-expansion (as if they were functions rather than methods).
 
@@ -79,7 +79,7 @@ val b: { def put(x: String): Unit } = a
 
 This code won't compile. This is because when `Sink[String]` gets erased to `Sink[Object]` (as it's seen from JVM's perspective) the method's signature becomes `put(x: Object): Unit` while for the structural type it remains unchanged as `put(x: String): Unit` and they wouldn't match in runtime therefore `Sink[String]` cannot be treated as a subtype of `{ def put(x: String): Unit }`.
 
-We might however try to write a better method dispatch algorithm ourselves instead of relying on the JVM's default one to make this work. To assure the compiler that we know what we're doing we'll need to use the new `Selectable.WithoutPreciseParameterTypes` marker trait. Currently it's an experimental feature (introduced by [#12268](https://github.com/lampepfl/dotty/pull/12268)) so you'll be able to use it only with a snapshot or nightly version of the compiler and you'll need to annotate all subtypes of this trait with `@experimental`.
+We might however try to write a better method dispatch algorithm ourselves instead of relying on the JVM's default one to make this work. To assure the compiler that we know what we're doing we'll need to use the new `Selectable.WithoutPreciseParameterTypes` marker trait. Currently it's an experimental feature (introduced by [#12268](https://github.com/scala/scala3/pull/12268)) so you'll be able to use it only with a snapshot or nightly version of the compiler and you'll need to annotate all subtypes of this trait with `@experimental`.
 
 ```scala
 import annotation.experimental
@@ -103,46 +103,46 @@ This snippet will compile as the compiler won't perform the precise signature ch
 
 Keeping in mind how important metaprogramming has become to Scala developers (especially creators of libraries) we continue to make it more reliable by fixing reported bugs and more powerful by repealing formerly introduced limitations. If you're curious how it was done look at the PRs below:
 
-- Map opaque types in arguments of inlined calls to proxies [#12922](https://github.com/lampepfl/dotty/pull/12922)
-- Don't forget side effects in prefixes of inlined function calls [#12842](https://github.com/lampepfl/dotty/pull/12842)
-- Drop "no inlines with opaques" implementation restriction [#12815](https://github.com/lampepfl/dotty/pull/12815)
-- Detect abstract inline method calls after inlining [#12777](https://github.com/lampepfl/dotty/pull/12777)
-- Fix implicit ValueOf synthesis [#12615](https://github.com/lampepfl/dotty/pull/12615)
+- Map opaque types in arguments of inlined calls to proxies [#12922](https://github.com/scala/scala3/pull/12922)
+- Don't forget side effects in prefixes of inlined function calls [#12842](https://github.com/scala/scala3/pull/12842)
+- Drop "no inlines with opaques" implementation restriction [#12815](https://github.com/scala/scala3/pull/12815)
+- Detect abstract inline method calls after inlining [#12777](https://github.com/scala/scala3/pull/12777)
+- Fix implicit ValueOf synthesis [#12615](https://github.com/scala/scala3/pull/12615)
 
 ## Other notable improvements
 
-- Add Scala 3 batch commands for Windows [#13006](https://github.com/lampepfl/dotty/pull/13006)
-- Fix [#12981](https://github.com/lampepfl/dotty/issues/12981): show diagnostics levels (warn \| error) in REPL [#13000](https://github.com/lampepfl/dotty/pull/13000)
-- Add no links warning setting to scaladoc [#12936](https://github.com/lampepfl/dotty/pull/12936)
-- Use WeakHashSet instead of HashSet for hash-consing types [#12935](https://github.com/lampepfl/dotty/pull/12935)
-- Balance And/Or types when forming lubs and glbs [#12928](https://github.com/lampepfl/dotty/pull/12928)
-- Restricts isInstanceOf[Null] checks [#12905](https://github.com/lampepfl/dotty/pull/12905)
-- Add support for shallow capture sets [#12875](https://github.com/lampepfl/dotty/pull/12875)
-- Drop implementation restriction for polymorphic functions [#12863](https://github.com/lampepfl/dotty/pull/12863)
-- Preserve hard unions in more situations [#12654](https://github.com/lampepfl/dotty/pull/12654)
-- Better support type-heavy pattern matches [#12549](https://github.com/lampepfl/dotty/pull/12549)
+- Add Scala 3 batch commands for Windows [#13006](https://github.com/scala/scala3/pull/13006)
+- Fix [#12981](https://github.com/scala/scala3/issues/12981): show diagnostics levels (warn \| error) in REPL [#13000](https://github.com/scala/scala3/pull/13000)
+- Add no links warning setting to scaladoc [#12936](https://github.com/scala/scala3/pull/12936)
+- Use WeakHashSet instead of HashSet for hash-consing types [#12935](https://github.com/scala/scala3/pull/12935)
+- Balance And/Or types when forming lubs and glbs [#12928](https://github.com/scala/scala3/pull/12928)
+- Restricts isInstanceOf[Null] checks [#12905](https://github.com/scala/scala3/pull/12905)
+- Add support for shallow capture sets [#12875](https://github.com/scala/scala3/pull/12875)
+- Drop implementation restriction for polymorphic functions [#12863](https://github.com/scala/scala3/pull/12863)
+- Preserve hard unions in more situations [#12654](https://github.com/scala/scala3/pull/12654)
+- Better support type-heavy pattern matches [#12549](https://github.com/scala/scala3/pull/12549)
 
 ## Other notable bug fixes
 
-- Fix [#13046](https://github.com/lampepfl/dotty/issues/13046): override is a valid identifier in Java, not a keyword [#13048](https://github.com/lampepfl/dotty/pull/13048)
-- Don't emit Java generic signatures for constructors [#13047](https://github.com/lampepfl/dotty/pull/13047)
-- Exhaustivity warnings on nested case classes [#13030](https://github.com/lampepfl/dotty/pull/13030)
-- Refine overriding pairs in RefChecks [#12982](https://github.com/lampepfl/dotty/pull/12982)
-- Let annotations on parameters see preceding type parameters [#12980](https://github.com/lampepfl/dotty/pull/12980)
-- Retain transparent flag on exports [#12978](https://github.com/lampepfl/dotty/pull/12978)
-- Widen unions before finding members [#12925](https://github.com/lampepfl/dotty/pull/12925)
-- ProtoTypes#normalizedCompatible: keep more constraints [#12924](https://github.com/lampepfl/dotty/pull/12924)
-- Detect provisional superclasses and recompute them in Typer [#12912](https://github.com/lampepfl/dotty/pull/12912)
-- Properly handle self-types in reflection member lookup [#12893](https://github.com/lampepfl/dotty/pull/12893)
-- Use Java rules for member lookup in .java sources [#12884](https://github.com/lampepfl/dotty/pull/12884)
-- Hide problematic static forwarders [#12860](https://github.com/lampepfl/dotty/pull/12860)
-- When checking tp1 <:< tycon2[args2], widen tp1 to reveal application [#12846](https://github.com/lampepfl/dotty/pull/12846)
-- Skip contexts for implicit search when resolving imports [#12816](https://github.com/lampepfl/dotty/pull/12816)
-- Insert conversions also on selections wrapped in type applications [#12719](https://github.com/lampepfl/dotty/pull/12719)
-- Emit generic signature for static forwarders to nullary methods [#12710](https://github.com/lampepfl/dotty/pull/12710)
-- Add Matchable to the parents of Null in explicit nulls [#12697](https://github.com/lampepfl/dotty/pull/12697)
-- Always generate a partial function from a lambda [#12670](https://github.com/lampepfl/dotty/pull/12670)
-- Fix [#12572](https://github.com/lampepfl/dotty/issues/12572): Ignore default accessor bridges in non-native JS classes. [#12657](https://github.com/lampepfl/dotty/pull/12657)
+- Fix [#13046](https://github.com/scala/scala3/issues/13046): override is a valid identifier in Java, not a keyword [#13048](https://github.com/scala/scala3/pull/13048)
+- Don't emit Java generic signatures for constructors [#13047](https://github.com/scala/scala3/pull/13047)
+- Exhaustivity warnings on nested case classes [#13030](https://github.com/scala/scala3/pull/13030)
+- Refine overriding pairs in RefChecks [#12982](https://github.com/scala/scala3/pull/12982)
+- Let annotations on parameters see preceding type parameters [#12980](https://github.com/scala/scala3/pull/12980)
+- Retain transparent flag on exports [#12978](https://github.com/scala/scala3/pull/12978)
+- Widen unions before finding members [#12925](https://github.com/scala/scala3/pull/12925)
+- ProtoTypes#normalizedCompatible: keep more constraints [#12924](https://github.com/scala/scala3/pull/12924)
+- Detect provisional superclasses and recompute them in Typer [#12912](https://github.com/scala/scala3/pull/12912)
+- Properly handle self-types in reflection member lookup [#12893](https://github.com/scala/scala3/pull/12893)
+- Use Java rules for member lookup in .java sources [#12884](https://github.com/scala/scala3/pull/12884)
+- Hide problematic static forwarders [#12860](https://github.com/scala/scala3/pull/12860)
+- When checking tp1 <:< tycon2[args2], widen tp1 to reveal application [#12846](https://github.com/scala/scala3/pull/12846)
+- Skip contexts for implicit search when resolving imports [#12816](https://github.com/scala/scala3/pull/12816)
+- Insert conversions also on selections wrapped in type applications [#12719](https://github.com/scala/scala3/pull/12719)
+- Emit generic signature for static forwarders to nullary methods [#12710](https://github.com/scala/scala3/pull/12710)
+- Add Matchable to the parents of Null in explicit nulls [#12697](https://github.com/scala/scala3/pull/12697)
+- Always generate a partial function from a lambda [#12670](https://github.com/scala/scala3/pull/12670)
+- Fix [#12572](https://github.com/scala/scala3/issues/12572): Ignore default accessor bridges in non-native JS classes. [#12657](https://github.com/scala/scala3/pull/12657)
 
 ## Contributors
 Thank you to all the contributors who made this release possible 🎉
@@ -208,7 +208,7 @@ According to `git shortlog -sn --no-merges 3.0.1-RC2..3.0.2-RC1` these are:
 ## Library authors: Join our community build
 
 Scala 3 now has a set of widely-used community libraries that are built against every nightly Scala 3 snapshot.
-Join our [community build](https://github.com/lampepfl/dotty/tree/master/community-build)
+Join our [community build](https://github.com/scala/scala3/tree/main/community-build)
 to make sure that our regression suite includes your library.
 
 [Scastie]: https://scastie.scala-lang.org/?target=dotty
diff --git a/blog/_posts/2021-09-07-scala-3.0.2-released.md b/blog/_posts/2021-09-07-scala-3.0.2-released.md
index 757314873..944bb8bc0 100644
--- a/blog/_posts/2021-09-07-scala-3.0.2-released.md
+++ b/blog/_posts/2021-09-07-scala-3.0.2-released.md
@@ -14,7 +14,7 @@ Recently, we are more and more confident that we can release stable versions of
 
 Scala 3's indentation based syntax is aimed at making your code more concise and readable. As it gets broader adoption, we consistently improve its specification to eliminate corner cases which might lead to ambiguities or counterintuitive behaviours.
 
-Thanks to [#12801](https://github.com/lampepfl/dotty/pull/12801) it is now allowed for a logical expression in an `if` statement or expression to continue in the following line if it starts in the same line as the `if` keyword, e.g.
+Thanks to [#12801](https://github.com/scala/scala3/pull/12801) it is now allowed for a logical expression in an `if` statement or expression to continue in the following line if it starts in the same line as the `if` keyword, e.g.
 
 ```scala
 if foo
@@ -58,7 +58,7 @@ def foo(x: Matchable) = x match { case null => () }
 
 ### Method search by type signature
 
-You can now browse the documentation of Scala's API not only by names of methods but also by their type in a [Hoogle](https://hoogle.haskell.org)-like manner (but with Scala syntax) thanks to integration with [Inkuire](https://github.com/VirtusLab/Inkuire) brought up by [#12375](https://github.com/lampepfl/dotty/pull/12375).
+You can now browse the documentation of Scala's API not only by names of methods but also by their type in a [Hoogle](https://hoogle.haskell.org)-like manner (but with Scala syntax) thanks to integration with [Inkuire](https://github.com/VirtusLab/Inkuire) brought up by [#12375](https://github.com/scala/scala3/pull/12375).
 
 To find methods with the desired signature simply write in scaladoc's searchbar the type you would expect them to have after eta-expansion (as if they were functions rather than methods).
 
@@ -76,7 +76,7 @@ val b: { def put(x: String): Unit } = a
 
 This code won't compile. This is because when `Sink[String]` gets erased to `Sink[Object]` (as it's seen from JVM's perspective) the method's signature becomes `put(x: Object): Unit` while for the structural type it remains unchanged as `put(x: String): Unit` and they wouldn't match in runtime therefore `Sink[String]` cannot be treated as a subtype of `{ def put(x: String): Unit }`.
 
-We might however try to write a better method dispatch algorithm ourselves instead of relying on the JVM's default one to make this work. To assure the compiler that we know what we're doing we'll need to use the new `Selectable.WithoutPreciseParameterTypes` marker trait. Currently it's an experimental feature (introduced by [#12268](https://github.com/lampepfl/dotty/pull/12268)) so you'll be able to use it only with a snapshot or nightly version of the compiler and you'll need to annotate all subtypes of this trait with `@experimental`.
+We might however try to write a better method dispatch algorithm ourselves instead of relying on the JVM's default one to make this work. To assure the compiler that we know what we're doing we'll need to use the new `Selectable.WithoutPreciseParameterTypes` marker trait. Currently it's an experimental feature (introduced by [#12268](https://github.com/scala/scala3/pull/12268)) so you'll be able to use it only with a snapshot or nightly version of the compiler and you'll need to annotate all subtypes of this trait with `@experimental`.
 
 ```scala
 import annotation.experimental
@@ -98,12 +98,12 @@ This snippet will compile as the compiler won't perform the precise signature ch
 
 ### Other changes
 
-Beside that scala 3.0.2 introduced multiple small improvements, mainly in metaprogramming, and fixed handful of bugs. You can see [the detailed changelog](https://github.com/lampepfl/dotty/releases/tag/3.0.2) on GitHub.
+Beside that scala 3.0.2 introduced multiple small improvements, mainly in metaprogramming, and fixed handful of bugs. You can see [the detailed changelog](https://github.com/scala/scala3/releases/tag/3.0.2) on GitHub.
 
 ## What's next
 
 We have decided that it is the right time for the first minor version after the initial release of Scala 3. Together with stable version 3.0.2, we have released the first release candidate for Scala 3.1. You can already use 3.1.0-RC1 and test not only the new experimental features like safer exceptions but also Scastie embedded in Scaladoc pages, improvements in JVM bytecode generation, the possibility to configure the compiler warnings and lots of smaller improvements and fixes all across the board.
-You can find [the full changelog for 3.1.0-RC1](https://github.com/lampepfl/dotty/releases/tag/3.1.0-RC1) on GitHub.
+You can find [the full changelog for 3.1.0-RC1](https://github.com/scala/scala3/releases/tag/3.1.0-RC1) on GitHub.
 
 You can expect the stable release of Scala 3.1 in the middle of October.
 
@@ -173,7 +173,7 @@ According to `git shortlog -sn --no-merges 3.0.1..3.0.2` these are:
 ## Library authors: Join our community build
 
 Scala 3 now has a set of widely-used community libraries that are built against every nightly Scala 3 snapshot.
-Join our [community build](https://github.com/lampepfl/dotty/tree/master/community-build)
+Join our [community build](https://github.com/scala/scala3/tree/main/community-build)
 to make sure that our regression suite includes your library.
 
 [Scastie]: https://scastie.scala-lang.org/?target=dotty
diff --git a/blog/_posts/2021-10-21-scala-3.1.0-released.md b/blog/_posts/2021-10-21-scala-3.1.0-released.md
index 493ef671d..a4b8b7577 100644
--- a/blog/_posts/2021-10-21-scala-3.1.0-released.md
+++ b/blog/_posts/2021-10-21-scala-3.1.0-released.md
@@ -37,7 +37,7 @@ def f(x: Double): Double throws LimitExceeded =
   if x < limit then f(x) else throw LimitExceeded()
 ```
 
-You can read more in [the document proposing this feature](https://github.com/lampepfl/dotty/blob/release-3.1.0/docs/docs/reference/experimental/canthrow.md).
+You can read more in [the document proposing this feature](https://github.com/scala/scala3/blob/release-3.1.0/docs/docs/reference/experimental/canthrow.md).
 
 ### Efficient bytecode for matching over strings
 
@@ -90,7 +90,7 @@ The only change necessary for users is that they should now consider that one of
 ### Other changes
 
 - Scastie was integrated into Scaladoc to make snippets interactive.
-- `@experimental` annotation is no longer itself experimental. The users are no longer required to use a nightly build of the compiler to be able to define experimental APIs. See more detail in [the design document](https://github.com/lampepfl/dotty/blob/release-3.1.0/docs/docs/reference/other-new-features/experimental-defs.md)
+- `@experimental` annotation is no longer itself experimental. The users are no longer required to use a nightly build of the compiler to be able to define experimental APIs. See more detail in [the design document](https://github.com/scala/scala3/blob/release-3.1.0/docs/docs/reference/other-new-features/experimental-defs.md)
 - Now `TastyInspector.{inspectTastyFiles, inspectTastyFilesInJar, inspectAllTastyFiles}` return a boolean value indicating whether the process succeeded
 - A `Wildcard` was made a subtype of `Ident` in the reflection API
 - `TypedOrTest` was added as a supertype of `Typed` in the reflection API
@@ -98,11 +98,11 @@ The only change necessary for users is that they should now consider that one of
 - Unreductible match types now raise type errors
 - Scala 3.1 targets Scala.js 1.7.x+. This means that users must upgrade to Scala.js 1.7.0 or later to use Scala 3.1.
 
-Beside that Scala 3.1.0 introduced multiple small improvements and fixed a handful of bugs. You can see [the detailed changelog](https://github.com/lampepfl/dotty/releases/tag/3.1.0) on GitHub.
+Beside that Scala 3.1.0 introduced multiple small improvements and fixed a handful of bugs. You can see [the detailed changelog](https://github.com/scala/scala3/releases/tag/3.1.0) on GitHub.
 
 ## What's next
 
-During the Scala 3.1.0 stabilization period, which took the last six weeks, we haven't stopped improving the language and fixing the bugs in the compiler. You can already test the results of our work, using the published release candidate: Scala 3.1.1-RC1. [The full changelog](https://github.com/lampepfl/dotty/releases/tag/3.1.1-RC1) is as always available on GitHub.
+During the Scala 3.1.0 stabilization period, which took the last six weeks, we haven't stopped improving the language and fixing the bugs in the compiler. You can already test the results of our work, using the published release candidate: Scala 3.1.1-RC1. [The full changelog](https://github.com/scala/scala3/releases/tag/3.1.1-RC1) is as always available on GitHub.
 
 You can expect the stable release of Scala 3.1.1 in early December.
 
@@ -164,7 +164,7 @@ According to `git shortlog -sn --no-merges 3.0.2..3.1.0` these are:
 ## Library authors: Join our community build
 
 Scala 3 has a set of widely-used community libraries that are built against every nightly Scala 3 snapshot.
-Join our [community build](https://github.com/lampepfl/dotty/tree/master/community-build)
+Join our [community build](https://github.com/scala/scala3/tree/main/community-build)
 to make sure that our regression suite includes your library.
 
 [Scastie]: https://scastie.scala-lang.org/?target=dotty
diff --git a/blog/_posts/2022-02-01-scala-3.1.1-released.md b/blog/_posts/2022-02-01-scala-3.1.1-released.md
index 7c78a20a8..95a424380 100644
--- a/blog/_posts/2022-02-01-scala-3.1.1-released.md
+++ b/blog/_posts/2022-02-01-scala-3.1.1-released.md
@@ -21,12 +21,12 @@ Scala 3.1.1 is a patch release focused on bug fixes. Although there are no new a
       ???
   ```
 
-  To learn more see [PR #13662](https://github.com/lampepfl/dotty/pull/13662) and [related issue](https://github.com/lampepfl/dotty/issues/12955).
-- Mirrors can be correctly summoned for hierarchical sum types compiled by Scala 3.0.x. It is now safe to derive a type class for a type dependency that was compiled with a pre-3.1.0 compiler. ([PR #14100](https://github.com/lampepfl/dotty/pull/14100)).
-- Dual Scala 2/3 macros can be now declared in non-experimental scopes ([PR #13795](https://github.com/lampepfl/dotty/pull/13795)).
+  To learn more see [PR #13662](https://github.com/scala/scala3/pull/13662) and [related issue](https://github.com/scala/scala3/issues/12955).
+- Mirrors can be correctly summoned for hierarchical sum types compiled by Scala 3.0.x. It is now safe to derive a type class for a type dependency that was compiled with a pre-3.1.0 compiler. ([PR #14100](https://github.com/scala/scala3/pull/14100)).
+- Dual Scala 2/3 macros can be now declared in non-experimental scopes ([PR #13795](https://github.com/scala/scala3/pull/13795)).
 - Scaladoc documentation has an improved UI.
 
-For a comprehensive list of fixes, take a look at [the full changelog on GitHub](https://github.com/lampepfl/dotty/releases/tag/3.1.1).
+For a comprehensive list of fixes, take a look at [the full changelog on GitHub](https://github.com/scala/scala3/releases/tag/3.1.1).
 
 ## 3.1.2-RC1 and forward compatibility improvements
 
@@ -44,7 +44,7 @@ One important note is that the `-Yscala-release` flag is experimental and not ye
 
 Detailed description of the new flag can be found in [the reference page for the binary compatibility](https://docs.scala-lang.org/scala3/reference/language-versions/binary-compatibility.html).
 
-If you are interested in other changes brought by 3.1.2-RC1, there is, as always, [a changelog on GitHub](https://github.com/lampepfl/dotty/releases/tag/3.1.2-RC1).
+If you are interested in other changes brought by 3.1.2-RC1, there is, as always, [a changelog on GitHub](https://github.com/scala/scala3/releases/tag/3.1.2-RC1).
 
 ## Contributors
 
diff --git a/blog/_posts/2022-04-12-scala-3.1.2-released.md b/blog/_posts/2022-04-12-scala-3.1.2-released.md
index 0953e8a67..ac0bdd1da 100644
--- a/blog/_posts/2022-04-12-scala-3.1.2-released.md
+++ b/blog/_posts/2022-04-12-scala-3.1.2-released.md
@@ -82,7 +82,7 @@ We realized that there is some confusion about current output compatibility flag
 
   will print `836` on standard output and exit the Scala process.
 
-- There are new optimizations in the typer that may results in significant speedups in some cases. You can find more information and benchmark results in [the related pull request](https://github.com/lampepfl/dotty/pull/13637).
+- There are new optimizations in the typer that may results in significant speedups in some cases. You can find more information and benchmark results in [the related pull request](https://github.com/scala/scala3/pull/13637).
 
 ## Contributors
 
diff --git a/blog/_posts/2022-06-21-scala-3.1.3-released.md b/blog/_posts/2022-06-21-scala-3.1.3-released.md
index ca43e8c1f..a4cba829d 100644
--- a/blog/_posts/2022-06-21-scala-3.1.3-released.md
+++ b/blog/_posts/2022-06-21-scala-3.1.3-released.md
@@ -5,7 +5,7 @@ by: Paweł Marks, VirtusLab
 title: Scala 3.1.3 released!
 ---
 
-We are happy to announce the release of Scala 3.1.3! You can read more about all the improvements and fixes in [the full changelog](https://github.com/lampepfl/dotty/releases/tag/3.1.3). We have also prepared a short list of highlights of the most exciting additions in the new version.
+We are happy to announce the release of Scala 3.1.3! You can read more about all the improvements and fixes in [the full changelog](https://github.com/scala/scala3/releases/tag/3.1.3). We have also prepared a short list of highlights of the most exciting additions in the new version.
 
 ## Highlights of the release
 
diff --git a/blog/_posts/2022-11-07-scala-3.2.1-released.md b/blog/_posts/2022-11-07-scala-3.2.1-released.md
index b1a97f79e..9c9b38ad8 100644
--- a/blog/_posts/2022-11-07-scala-3.2.1-released.md
+++ b/blog/_posts/2022-11-07-scala-3.2.1-released.md
@@ -5,7 +5,7 @@ by: Paweł Marks, VirtusLab
 title: Scala 3.2.1 released!
 ---
 
-[Scala 3.2.1](https://github.com/lampepfl/dotty/releases/tag/3.2.1) is now available!
+[Scala 3.2.1](https://github.com/scala/scala3/releases/tag/3.2.1) is now available!
 
 This version is a bug-fixing release focusing mainly but not exclusively on solving rare issues with code not compiling after upgrading the language version to 3.2.0. This release also brings two notable enhancements:
 
diff --git a/blog/_posts/2023-01-31-scala-center-2023-roadmap.md b/blog/_posts/2023-01-31-scala-center-2023-roadmap.md
index 7524547d9..e2b3845e5 100644
--- a/blog/_posts/2023-01-31-scala-center-2023-roadmap.md
+++ b/blog/_posts/2023-01-31-scala-center-2023-roadmap.md
@@ -54,12 +54,12 @@ strategy whose goal is to establish all the necessary decision-making processes
 **We improved meta-programming, especially [generic Mirror](https://docs.scala-lang.org/scala3/reference/contextual/derivation.html#mirror)
 synthesis.** Mirrors are critical to metaprogramming in Scala 3, they enable implementation of type class derivation without
 advanced metaprogramming techniques such as macros. Mirror synthesis now supports more cases
-([generic tuples](https://github.com/lampepfl/dotty/pull/15250),
-[local and inner classes](https://github.com/lampepfl/dotty/pull/15847)), is more reliable
-([dotty#15279](https://github.com/lampepfl/dotty/pull/15279),
-[dotty#15404](https://github.com/lampepfl/dotty/pull/15404),
-[dotty#15814](https://github.com/lampepfl/dotty/pull/15814)), and provides
-[more detailed explanations in case of failure](https://github.com/lampepfl/dotty/pull/15164).
+([generic tuples](https://github.com/scala/scala3/pull/15250),
+[local and inner classes](https://github.com/scala/scala3/pull/15847)), is more reliable
+([dotty#15279](https://github.com/scala/scala3/pull/15279),
+[dotty#15404](https://github.com/scala/scala3/pull/15404),
+[dotty#15814](https://github.com/scala/scala3/pull/15814)), and provides
+[more detailed explanations in case of failure](https://github.com/scala/scala3/pull/15164).
 
 **We generalized the definition of methods in Scala** by allowing type parameters to be interleaved with regular parameters.
 This change notably allows methods to take type parameters whose bounds depend on value parameters. You can learn more
@@ -163,7 +163,7 @@ library, we will:
 - **Make the compiler error messages clearer and more actionable.** The compiler should help developers write correct code
   instead of “just complaining” about incorrect code. The compiler should also guide you to write maintainable code (ie,
   it should provide linting features). You can find a list of related issues
-  [here](https://github.com/lampepfl/dotty/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%3Areporting).
+  [here](https://github.com/scala/scala3/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%3Areporting).
 - **Bring the compiler’s suggestions into the IDEs.** Instead of emitting only text output, the compiler
   will produce structured output that IDEs (Metals and IntelliJ) will be able to read to automatically provide “quick
   fixes” to the users. This should reduce the implementation (and maintenance) costs on the IDE side.
diff --git a/blog/_posts/2023-04-11-march-2023-scala-tooling-summit.md b/blog/_posts/2023-04-11-march-2023-scala-tooling-summit.md
index 82fda04d5..dd2b6a165 100644
--- a/blog/_posts/2023-04-11-march-2023-scala-tooling-summit.md
+++ b/blog/_posts/2023-04-11-march-2023-scala-tooling-summit.md
@@ -96,7 +96,7 @@ summit!
 The idea would be that fixes like this can come directly from the compiler
 ensuring that all tooling that interacts with it can benefit. You can follow the
 progress on this work in [this Dotty mega issue on structured
-diagnostics](https://github.com/lampepfl/dotty/issues/14904).
+diagnostics](https://github.com/scala/scala3/issues/14904).
 
 ### JetBrains / Scala Center education collaboration
 
diff --git a/blog/_posts/2023-05-30-scala-3.3.0-released.md b/blog/_posts/2023-05-30-scala-3.3.0-released.md
index 417f8923b..df21a2f4d 100644
--- a/blog/_posts/2023-05-30-scala-3.3.0-released.md
+++ b/blog/_posts/2023-05-30-scala-3.3.0-released.md
@@ -70,7 +70,7 @@ class TestSuite extends munit.FunSuite:
     assert(job.isSuccess)
 ```
 
-For the record, the braceless syntax has been introduced in Scala 3.0.0. However, braces were still needed to pass function arguments. Martin Odersky proposed to address this point in the proposal [SIP-44 - Fewer braces](https://docs.scala-lang.org/sips/fewer-braces.html), which was accepted by the SIP Committee in [August 2022](https://docs.scala-lang.org/sips/results/2022-08-26-meeting.html). The final implementation was released as an experimental feature in [Scala 3.2.0](https://github.com/lampepfl/dotty/releases/tag/3.2.0) in September. Finally, in [October](https://docs.scala-lang.org/sips/results/2022-10-21-meeting.html), the SIP Committee voted to promote it to a stable feature.
+For the record, the braceless syntax has been introduced in Scala 3.0.0. However, braces were still needed to pass function arguments. Martin Odersky proposed to address this point in the proposal [SIP-44 - Fewer braces](https://docs.scala-lang.org/sips/fewer-braces.html), which was accepted by the SIP Committee in [August 2022](https://docs.scala-lang.org/sips/results/2022-08-26-meeting.html). The final implementation was released as an experimental feature in [Scala 3.2.0](https://github.com/scala/scala3/releases/tag/3.2.0) in September. Finally, in [October](https://docs.scala-lang.org/sips/results/2022-10-21-meeting.html), the SIP Committee voted to promote it to a stable feature.
 
 ### `boundary` and `break`
 
diff --git a/blog/_posts/2023-10-17-feedback-wanted-error-messages.md b/blog/_posts/2023-10-17-feedback-wanted-error-messages.md
index 0d642be18..7b645d485 100644
--- a/blog/_posts/2023-10-17-feedback-wanted-error-messages.md
+++ b/blog/_posts/2023-10-17-feedback-wanted-error-messages.md
@@ -16,7 +16,7 @@ description: "Feedback is wanted on confusing or unhelpful error messages"
 From [suggesting to import missing extension methods](https://docs.scala-lang.org/scala3/book/ca-extension-methods.html#import-extension-method) and more, Scala 3 tries to improve the ways that warnings and errors are reported to the user.
 The idea being that when the user engages with reported problems, it should feel like having a conversation with a helpful tutor. By helping users to get back on track, we can make Scala easier to learn, friendlier to newcomers, and also keep experienced users more productive.
 
-We know there is much more that can be done to continually improve the situation. As well as working to [expose diagnostics programatically](https://github.com/lampepfl/dotty/issues/14904), we are starting a new campaign to seek out confusing, annoying or unhelpful error/warning messages.
+We know there is much more that can be done to continually improve the situation. As well as working to [expose diagnostics programatically](https://github.com/scala/scala3/issues/14904), we are starting a new campaign to seek out confusing, annoying or unhelpful error/warning messages.
 
 As compiler authors, we do try to provide good messages, but it is possible for there to be shortcomings.
 For example, the message may correctly report a problem, but not provide enough information to actually help the user.
@@ -34,20 +34,20 @@ To help collect problematic errors, we have made a [new issue template][issue-te
 
 The template helps you to write the report, by asking what was so confusing/unhelpful about the message, and then gives the option for you to suggest what would make the error more helpful, actionable, etc.
 
-The improvement may be anywhere from more explicit explanation of the source of error, to even [adding a quick fix](https://github.com/lampepfl/dotty/pull/18314) that can be applied automatically. Again you can read [this issue][lambda-issue] for inspiration.
+The improvement may be anywhere from more explicit explanation of the source of error, to even [adding a quick fix](https://github.com/scala/scala3/pull/18314) that can be applied automatically. Again you can read [this issue][lambda-issue] for inspiration.
 
 **Please [click here][issue-template] to open a new issue!**
 
 ### Results so far
 
 We also opened similar threads last week on [Scala Users](https://users.scala-lang.org/t/feedback-wanted-confusing-or-unhelpful-error-messages/9553/5) and [Scala Contributors](https://contributors.scala-lang.org/t/feedback-wanted-confusing-unhelpful-error-messages/6346/2), asking for feedback. So far since we have received four reports from the community:
-1. [lampepfl/dotty#18686: Better error message when accessing private members](https://github.com/lampepfl/dotty/issues/18686)
-2. [lampepfl/dotty#18685: lazy val parameters and overrides](https://github.com/lampepfl/dotty/issues/18685)
-3. [lampepfl/dotty#18684: confusing "Not found" error when I change "def foo()" to "val foo()"](https://github.com/lampepfl/dotty/issues/18684)
-4. [lampepfl/dotty#18682: Can we have "did you mean..." for top-level names rather than just methods](https://github.com/lampepfl/dotty/issues/18682)
+1. [scala/scala3#18686: Better error message when accessing private members](https://github.com/scala/scala3/issues/18686)
+2. [scala/scala3#18685: lazy val parameters and overrides](https://github.com/scala/scala3/issues/18685)
+3. [scala/scala3#18684: confusing "Not found" error when I change "def foo()" to "val foo()"](https://github.com/scala/scala3/issues/18684)
+4. [scala/scala3#18682: Can we have "did you mean..." for top-level names rather than just methods](https://github.com/scala/scala3/issues/18682)
 
 <br/>
-And we already have a fix for `1.` thanks to Nicolas Stucki from EPFL, [see PR lampepfl/dotty#18690](https://github.com/lampepfl/dotty/pull/18690).
+And we already have a fix for `1.` thanks to Nicolas Stucki from EPFL, [see PR scala/scala3#18690](https://github.com/scala/scala3/pull/18690).
 
-[lambda-issue]: https://github.com/lampepfl/dotty/issues/18657
-[issue-template]: https://github.com/lampepfl/dotty/issues/new?assignees=&labels=itype%3Aenhancement%2C+area%3Areporting%2C+better-errors%2C+stat%3Aneeds+triage&projects=&template=improve-error.md&title=
+[lambda-issue]: https://github.com/scala/scala3/issues/18657
+[issue-template]: https://github.com/scala/scala3/issues/new?assignees=&labels=itype%3Aenhancement%2C+area%3Areporting%2C+better-errors%2C+stat%3Aneeds+triage&projects=&template=improve-error.md&title=
diff --git a/blog/_posts/2024-02-29-scala-3.4.0-and-3.3.3-released.md b/blog/_posts/2024-02-29-scala-3.4.0-and-3.3.3-released.md
index 18273f005..42dde75c5 100644
--- a/blog/_posts/2024-02-29-scala-3.4.0-and-3.3.3-released.md
+++ b/blog/_posts/2024-02-29-scala-3.4.0-and-3.3.3-released.md
@@ -23,13 +23,13 @@ Unfortunately, [a subtle bug](https://github.com/playframework/playframework/iss
 
 ## What's new in 3.3.3 LTS (and 3.4.0 too)
 
-In the release notes of Scala [3.3.3 LTS](https://github.com/lampepfl/dotty/releases/tag/3.3.3), you can see a lot of bug fixes. One area that received special attention in that regard was coverage support. With most pains fixed, we are now confident in the state of coverage.
+In the release notes of Scala [3.3.3 LTS](https://github.com/scala/scala3/releases/tag/3.3.3), you can see a lot of bug fixes. One area that received special attention in that regard was coverage support. With most pains fixed, we are now confident in the state of coverage.
 
 Another important change, not directly visible to end users, is the integration of the presentation compiler into the compiler itself. This makes building tooling easier and allows for a more stable and reliable user experience when using Metals.
 
 ## Changes exclusive to 3.4.0
 
-Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) contains many substantial changes and improvements. The most noteworthy can be grouped in a few broad categories:
+Release notes of [3.4.0](https://github.com/scala/scala3/releases/tag/3.4.0) contains many substantial changes and improvements. The most noteworthy can be grouped in a few broad categories:
 
 ### Stabilized SIPs
 
@@ -101,7 +101,7 @@ Release notes of [3.4.0](https://github.com/lampepfl/dotty/releases/tag/3.4.0) c
 
   This will improve the user experience when the class file format changes unexpectedly. This feature will be backported to Scala 3.3.3.
 - Progress reporting of compilation is now visible in IDEs. Metals IDE users will notice that compilation progress is no longer frozen at 0% when using sbt or bloop as the BSP server. IntelliJ will also correctly report progress for BSP and sbt based projects.
-- Diagnostics (including unused warnings) are now exported to SemanticDB. That will allow better handling of warnings in tooling. See [#17835](https://github.com/lampepfl/dotty/pull/17835).
+- Diagnostics (including unused warnings) are now exported to SemanticDB. That will allow better handling of warnings in tooling. See [#17835](https://github.com/scala/scala3/pull/17835).
 
 ### Experimental changes
 
diff --git a/community/index.md b/community/index.md
index 0e5990ed5..697ab18a5 100644
--- a/community/index.md
+++ b/community/index.md
@@ -117,7 +117,7 @@ Scala 2 compiler, standard library, and language spec:
 
 Scala 3 compiler and standard library additions:
 
-* [lampepfl/dotty](https://github.com/lampepfl/dotty/issues)
+* [scala/scala3](https://github.com/scala/scala3/issues)
 
 Don't forget to search past issues first to see if the issue has
 already been reported.
diff --git a/gsoc/2015.md b/gsoc/2015.md
index dae1a0293..f9fd55300 100644
--- a/gsoc/2015.md
+++ b/gsoc/2015.md
@@ -164,7 +164,7 @@ Supervised by @axel22
 
 ### TASTY support for Scala
 
-Proposed in [the scala.meta project](https://scalameta.org/), the idea of AST persistence recently gained traction in the Scala ecosystem. Last fall, [the Dotty team has adopted](https://groups.google.com/forum/#!topic/scala-internals/hshvEUF3JUk) TASTY, a typed AST pickling format, as its primary interchange format, and its implementation is already [making its way](https://github.com/lampepfl/dotty/pull/365) into the Dotty compiler.
+Proposed in [the scala.meta project](https://scalameta.org/), the idea of AST persistence recently gained traction in the Scala ecosystem. Last fall, [the Dotty team has adopted](https://groups.google.com/forum/#!topic/scala-internals/hshvEUF3JUk) TASTY, a typed AST pickling format, as its primary interchange format, and its implementation is already [making its way](https://github.com/scala/scala3/pull/365) into the Dotty compiler.
 
 The goal of this project is to implement serialization and deserialization of Scala compiler trees into TASTY to help us establish the new metaprogramming platform for the Scala ecosystem. This will facilitate interoperability between Scala and Dotty, will enable advanced metaprogramming techniques with scala.meta and provide the potential to improve code optimization facilities for Scala.
 
diff --git a/gsoc/2016.md b/gsoc/2016.md
index 5c75415ed..4a5257571 100644
--- a/gsoc/2016.md
+++ b/gsoc/2016.md
@@ -162,8 +162,8 @@ the REPL experience in Dotty. In this project you're going to expand
 current minimalistic REPL with advanced functionality to improve
 end-user's experience.
 
-[https://github.com/lampepfl/dotty/issues?utf8=✓&q=is%3Aissue+is%3Aopen+repl](
-https://github.com/lampepfl/dotty/issues?utf8=✓&q=is%3Aissue+is%3Aopen+repl)
+[https://github.com/scala/scala3/issues?utf8=✓&q=is%3Aissue+is%3Aopen+repl](
+https://github.com/scala/scala3/issues?utf8=✓&q=is%3Aissue+is%3Aopen+repl)
 
 Supervised by [@densh](https://github.com/densh)