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

---
 _ja/scala3/contribute-to-docs.md                   |  4 ++--
 _overviews/FAQ/index.md                            |  2 +-
 _overviews/compiler-options/optimizer.md           |  2 +-
 _overviews/contribute/bug-reporting-guide.md       |  2 +-
 _overviews/contribute/codereviews.md               |  2 +-
 _overviews/contribute/guide.md                     |  2 +-
 _overviews/contribute/index.md                     |  8 ++++----
 .../scala-standard-library-api-documentation.md    |  2 +-
 .../scala3-migration/incompat-other-changes.md     |  4 ++--
 .../scala3-migration/incompat-type-checker.md      |  2 +-
 .../scaladoc-settings-compatibility.md             | 14 +++++++-------
 .../scala3-migration/tooling-migration-mode.md     |  2 +-
 _overviews/scala3-scaladoc/docstrings.md           |  2 +-
 _overviews/scala3-scaladoc/settings.md             |  6 +++---
 _ru/scala3/contribute-to-docs.md                   |  4 ++--
 _ru/scala3/guides/scaladoc/docstrings.md           |  2 +-
 _ru/scala3/guides/scaladoc/settings.md             |  6 +++---
 _ru/scala3/scaladoc.md                             |  2 +-
 .../minutes/2016-08-16-sip-10th-august-minutes.md  |  2 +-
 _sips/minutes/2018-08-30-sip-minutes.md            |  6 +++---
 _sips/minutes/2018-11-26-sip-minutes.md            | 12 ++++++------
 _sips/minutes/2019-03-13-sip-minutes.md            |  6 +++---
 _sips/minutes/2019-06-08-sip-minutes.md            |  4 ++--
 _sips/minutes/2020-03-12-minutes.md                |  6 +++---
 _sips/minutes/2020-03-13-sip-minutes.md            |  6 +++---
 _sips/sips/binary-api.md                           | 10 +++++-----
 _sips/sips/byname-implicits.md                     |  4 ++--
 _sips/sips/clause-interleaving.md                  |  2 +-
 _sips/sips/fewer-braces.md                         |  4 ++--
 _sips/sips/interpolation-quote-escape.md           |  2 +-
 _sips/sips/match-types-spec.md                     |  4 ++--
 _sips/sips/multi-source-extension-overloads.md     |  2 +-
 _sips/sips/polymorphic-eta-expansion.md            |  2 +-
 _sips/sips/priority-based-infix-type-precedence.md |  2 +-
 _sips/sips/quote-pattern-type-variable-syntax.md   |  8 ++++----
 _sips/sips/trait-parameters.md                     |  2 +-
 _uk/scala3/scaladoc.md                             |  2 +-
 _zh-cn/scala3/reference/README.md                  |  4 ++--
 scala3/contribute-to-docs.md                       |  4 ++--
 scala3/reference/README.md                         |  4 ++--
 scala3/scaladoc.md                                 |  2 +-
 41 files changed, 84 insertions(+), 84 deletions(-)

diff --git a/_ja/scala3/contribute-to-docs.md b/_ja/scala3/contribute-to-docs.md
index e95cc31b5..90b123e08 100644
--- a/_ja/scala3/contribute-to-docs.md
+++ b/_ja/scala3/contribute-to-docs.md
@@ -55,8 +55,8 @@ Scala 3 コンパイラとライブラリへの貢献と内部に関する包括
 ## Scala 3 Language Reference
 The [Dotty reference]({{ site.scala3ref }}/overview.html) は Scala 3 になる予定である。これにはさまざまな言語仕様に関する公式のプレゼンテーションや技術的情報が含まれている。
 
-- [Sources](https://github.com/lampepfl/dotty/tree/main/docs/_docs)
-- [Issues](https://github.com/lampepfl/dotty/issues)
+- [Sources](https://github.com/scala/scala3/tree/main/docs/_docs)
+- [Issues](https://github.com/scala/scala3/issues)
 
 
 [scala3-book]: {% link _overviews/scala3-book/introduction.md %}
diff --git a/_overviews/FAQ/index.md b/_overviews/FAQ/index.md
index 3ef56d786..d9d6b66d2 100644
--- a/_overviews/FAQ/index.md
+++ b/_overviews/FAQ/index.md
@@ -321,7 +321,7 @@ tool you are using.  For sbt, add it to `.jvmopts`.
 If the stack overflow doesn't go away no matter how much stack you
 give the compiler, then it's a compiler bug. Please report it on the
 [Scala 2 bug tracker](https://github.com/scala/bug/issues) or [Scala 3
-bug tracker](https://github.com/lampepfl/dotty/issues), but check
+bug tracker](https://github.com/scala/scala3/issues), but check
 first if it's a duplicate of an existing ticket.
 
 ### I set a setting in sbt but nothing happened. Why?
diff --git a/_overviews/compiler-options/optimizer.md b/_overviews/compiler-options/optimizer.md
index 52705558b..5f35867bb 100644
--- a/_overviews/compiler-options/optimizer.md
+++ b/_overviews/compiler-options/optimizer.md
@@ -55,7 +55,7 @@ However, even when staying within these constraints, some changes performed by t
 - Inlined methods disappear from call stacks.
 
   - This can lead to unexpected behaviors when using a debugger.
-  - Related: line numbers (stored in bytecode) are discarded when a method is inlined into a different classfile, which also impacts debugging experience. (This [could be improved](https://github.com/scala/scala-dev/issues/3) and is expected to [progress](https://github.com/lampepfl/dotty/pull/11492).)
+  - Related: line numbers (stored in bytecode) are discarded when a method is inlined into a different classfile, which also impacts debugging experience. (This [could be improved](https://github.com/scala/scala-dev/issues/3) and is expected to [progress](https://github.com/scala/scala3/pull/11492).)
 
 - Inlining a method can delay class loading of the class where the method is defined.
 
diff --git a/_overviews/contribute/bug-reporting-guide.md b/_overviews/contribute/bug-reporting-guide.md
index 9f0364c98..303fd51d1 100644
--- a/_overviews/contribute/bug-reporting-guide.md
+++ b/_overviews/contribute/bug-reporting-guide.md
@@ -3,7 +3,7 @@ title: Bug Reporting Guide
 num: 8
 ---
 
-The Scala compiler and standard library bug tracker is located at [https://github.com/scala/bug](https://github.com/scala/bug), and for Scala 3, it is located at [github.com/lampepfl/dotty](https://github.com/lampepfl/dotty/issues). Before you submit a bug make sure that it is certainly a bug by following instructions
+The Scala compiler and standard library bug tracker is located at [https://github.com/scala/bug](https://github.com/scala/bug), and for Scala 3, it is located at [github.com/scala/scala3](https://github.com/scala/scala3/issues). Before you submit a bug make sure that it is certainly a bug by following instructions
 in [Is it a Bug?](#is-it-a-bug).
 
 ## Is it a Bug?
diff --git a/_overviews/contribute/codereviews.md b/_overviews/contribute/codereviews.md
index 619e91718..cb4922062 100644
--- a/_overviews/contribute/codereviews.md
+++ b/_overviews/contribute/codereviews.md
@@ -28,7 +28,7 @@ own pull requests.
 <div class="container">
   <div class="row">
      <div class="span4 doc-block">
-       <h4><a href="https://github.com/scala/scala/pulls">lampepfl/dotty</a></h4>
+       <h4><a href="https://github.com/scala/scala3/pulls">scala/scala3</a></h4>
        <p>Scala 3 bug fixes and changes in the language, core libs and included tools.</p>
      </div>
      <div class="span4 doc-block">
diff --git a/_overviews/contribute/guide.md b/_overviews/contribute/guide.md
index 056bfcded..beffb0186 100644
--- a/_overviews/contribute/guide.md
+++ b/_overviews/contribute/guide.md
@@ -34,7 +34,7 @@ unencumbered by copyrights or patents.
 
 ### Bug-fix Check List
 > Originally these steps cover the [Scala 2 compiler](https://github.com/scala/scala), but they also are relevant to
-> the [Scala 3 compiler](https://github.com/lampepfl/dotty).
+> the [Scala 3 compiler](https://github.com/scala/scala3).
 
 This is the impatient developer's checklist for the steps to submit a bug-fix pull request to the Scala project. For more information, description and justification for the steps, follow the links in that step. Further specific instructions for the release of Scala you are targeting can be found in the `CONTRIBUTING.md` file for that [GitHub branch](https://github.com/scala/scala)
 
diff --git a/_overviews/contribute/index.md b/_overviews/contribute/index.md
index 574ec761a..73fdaaf47 100644
--- a/_overviews/contribute/index.md
+++ b/_overviews/contribute/index.md
@@ -54,7 +54,7 @@ scala_resources:
     icon: fa fa-bug
     link: /contribute/guide.html
   - title: Code Reviews
-    description: "Review pull requests against scala/scala, lampepfl/dotty, scala/scala-lang, scala/docs.scala-lang, and others."
+    description: "Review pull requests against scala/scala, scala/scala3, scala/scala-lang, scala/docs.scala-lang, and others."
     icon: fa fa-eye
     link: /contribute/codereviews.html
   - title: Core Libraries
@@ -109,7 +109,7 @@ In the spree, regular project maintainers will mentor you to create your first c
 
 ### So you want to improve the Scala 3 compiler...
 
-The [Scala 3 compiler](https://github.com/lampepfl/dotty) is an open source project.
+The [Scala 3 compiler](https://github.com/scala/scala3) is an open source project.
 If you are curious about contributing but don't know how to begin, the [Scala Center](https://scala.epfl.ch)
 runs the **Scala Compiler Academy** project to onboard and educate new people to the project. You can join the regular
 **Issue Spree**, watch in-depth videos, and read the contributing guide:
@@ -119,7 +119,7 @@ runs the **Scala Compiler Academy** project to onboard and educate new people to
 #### Which areas are perfect for newcomers?
 - Adding new linting options, which help enforce cleaner code.
 - Improving the clarity of error messages, so that the user understands better what went wrong.
-- Add IDE quick-fix actions to error messages, e.g. PR [lampepfl/dotty#18314](https://github.com/lampepfl/dotty/pull/18314).
+- Add IDE quick-fix actions to error messages, e.g. PR [scala/scala3#18314](https://github.com/scala/scala3/pull/18314).
 
 ### So you want to write a library...
 
@@ -162,7 +162,7 @@ When contributing, please follow:
 
 ### Community tickets
 
-All issues can be found in the [Scala bug tracker](https://github.com/scala/bug), or the [Scala 3 issue tracker](https://github.com/lampepfl/dotty/issues). Most issues are labeled
+All issues can be found in the [Scala bug tracker](https://github.com/scala/bug), or the [Scala 3 issue tracker](https://github.com/scala/scala3/issues). Most issues are labeled
 to make it easier to find issues you are interested in.
 
 ### Tools and libraries
diff --git a/_overviews/contribute/scala-standard-library-api-documentation.md b/_overviews/contribute/scala-standard-library-api-documentation.md
index 692cf00a7..27f2093d9 100644
--- a/_overviews/contribute/scala-standard-library-api-documentation.md
+++ b/_overviews/contribute/scala-standard-library-api-documentation.md
@@ -39,7 +39,7 @@ package objects for important packages (these often get overlooked for documenta
 and are a good place for API overviews).
 
 If you find an issue, please log it in the [Scala bug tracker](https://github.com/scala/bug),
-(or else the [Scala 3 issue tracker](https://github.com/lampepfl/dotty/issues) for Scala 3 library additions)
+(or else the [Scala 3 issue tracker](https://github.com/scala/scala3/issues) for Scala 3 library additions)
 **after making sure it is not already logged as an issue**. To help with
 disambiguation, please use the following format for issue title:
 
diff --git a/_overviews/scala3-migration/incompat-other-changes.md b/_overviews/scala3-migration/incompat-other-changes.md
index 57dc8998d..a7a003d8e 100644
--- a/_overviews/scala3-migration/incompat-other-changes.md
+++ b/_overviews/scala3-migration/incompat-other-changes.md
@@ -124,7 +124,7 @@ class C extends B // In Scala 3, Error: class C needs to be abstract, since def
 {% endtab %}
 {% endtabs %}
 
-This behavior was decided in [Dotty issue #4770](https://github.com/lampepfl/dotty/issues/4770).
+This behavior was decided in [Dotty issue #4770](https://github.com/scala/scala3/issues/4770).
 
 An easy fix is simply to remove the abstract def, since in practice it had no effect in Scala 2.
 
@@ -264,7 +264,7 @@ val pojo = new Pojo()
 
 A type of the form `=> T` cannot be used as an argument to a type parameter anymore.
 
-This decision is explained in [this comment](https://github.com/lampepfl/dotty/blob/0f1a23e008148f76fd0a1c2991b991e1dad600e8/compiler/src/dotty/tools/dotc/core/ConstraintHandling.scala#L144-L152) of the Scala 3 source code.
+This decision is explained in [this comment](https://github.com/scala/scala3/blob/0f1a23e008148f76fd0a1c2991b991e1dad600e8/compiler/src/dotty/tools/dotc/core/ConstraintHandling.scala#L144-L152) of the Scala 3 source code.
 
 For instance, it is not allowed to pass a function of type `Int => (=> Int) => Int` to the `uncurried` method since it would assign `=> Int` to the type parameter `T2`. 
 
diff --git a/_overviews/scala3-migration/incompat-type-checker.md b/_overviews/scala3-migration/incompat-type-checker.md
index 09a6ea0bc..41afc5ebc 100644
--- a/_overviews/scala3-migration/incompat-type-checker.md
+++ b/_overviews/scala3-migration/incompat-type-checker.md
@@ -14,7 +14,7 @@ Scala 3 being based on stronger theoretical foundations, these unsoundness bugs
 ## Unsoundness Fixes in Variance checks
 
 In Scala 2, default parameters and inner-classes are not subject to variance checks.
-It is unsound and might cause runtime failures, as demonstrated by this [test](https://github.com/lampepfl/dotty/blob/10526a7d0aa8910729b6036ee51942e05b71abf6/tests/neg/variances.scala) in the Scala 3 repository.
+It is unsound and might cause runtime failures, as demonstrated by this [test](https://github.com/scala/scala3/blob/10526a7d0aa8910729b6036ee51942e05b71abf6/tests/neg/variances.scala) in the Scala 3 repository.
 
 The Scala 3 compiler does not permit this anymore.
 
diff --git a/_overviews/scala3-migration/scaladoc-settings-compatibility.md b/_overviews/scala3-migration/scaladoc-settings-compatibility.md
index 8b1faf210..7c6d63a59 100644
--- a/_overviews/scala3-migration/scaladoc-settings-compatibility.md
+++ b/_overviews/scala3-migration/scaladoc-settings-compatibility.md
@@ -7,15 +7,15 @@ previous-page: options-new
 next-page: plugin-intro
 ---
 
-The current page is stating the status of scaladoc settings. The related Github issue can be found here for [discussion](https://github.com/lampepfl/dotty/issues/11907)
+The current page is stating the status of scaladoc settings. The related Github issue can be found here for [discussion](https://github.com/scala/scala3/issues/11907)
 
 
 | Scala2 | Scala3 | Description | Comment | Is implemented?
 | ------------- | ------------- | --- | --- | --- |
 | -doc-format | _ | Selects in which format documentation is rendered. | Actually, old scaladoc supports only html, so it is in some way consistent with new scaladoc, which provides only html | <i class="fa fa-times fa-lg"></i> |  
-| -doc-title | -project | The overall name of the Scaladoc site | Aliased in [#11965](https://github.com/lampepfl/dotty/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
-| -doc-version | -project-version | | Aliased in [#11965](https://github.com/lampepfl/dotty/issues/11965)  | <i class="fa fa-check fa-lg"></i> | 
-| -doc-footer | -project-footer | A footer on every Scaladoc page, by default the EPFL/Lightbend copyright notice. Can be overridden with a custom footer. | Fixed by [#11965](https://github.com/lampepfl/dotty/issues/11965) | <i class="fa fa-check fa-lg"></i> |  
+| -doc-title | -project | The overall name of the Scaladoc site | Aliased in [#11965](https://github.com/scala/scala3/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
+| -doc-version | -project-version | | Aliased in [#11965](https://github.com/scala/scala3/issues/11965)  | <i class="fa fa-check fa-lg"></i> | 
+| -doc-footer | -project-footer | A footer on every Scaladoc page, by default the EPFL/Lightbend copyright notice. Can be overridden with a custom footer. | Fixed by [#11965](https://github.com/scala/scala3/issues/11965) | <i class="fa fa-check fa-lg"></i> |  
 | -doc-no-compile | _ | A directory containing sources which should be parsed for docstrings without compiling (e.g. AnyRef.scala) | We don't need this as we have completely different approach to that issue using -Ydocument-synthetic-types flag for synthetic types | <i class="fa fa-check fa-lg"></i> | 
 | -doc-source-url | -source-links | A URL pattern used to link to the source file, with some variables supported... | Scala3 implementation provides richer syntax. You can find migration steps below this [table](#source-links). | <i class="fa fa-check fa-lg"></i> |
 | -doc-external-doc | -external-mappings | Links describing locations of external dependencies' documentations. | Scala3 implementation provides richer syntax. You can find migration steps below this [table](#external-mappings). | <i class="fa fa-check fa-lg"></i> |
@@ -34,7 +34,7 @@ The current page is stating the status of scaladoc settings. The related Github
 | -diagrams-max-implicits | _ |  | We don't need this in Scala3 | <i class="fa fa-times fa-lg"></i> |
 | -diagrams-dot-timeout | _ |  | We don't need this in Scala3 | <i class="fa fa-times fa-lg"></i> |
 | -diagrams-dot-restart | _ |  | We don't need this in Scala3 |  <i class="fa fa-times fa-lg"></i> |
-| -author | -author |  | Fixed by [#11965](https://github.com/lampepfl/dotty/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
+| -author | -author |  | Fixed by [#11965](https://github.com/scala/scala3/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
 | -raw-output | _ |  | We don't need this in Scala3 | <i class="fa fa-check fa-lg"></i> |
 | -no-prefixes | _ |  | We don't need this in Scala3 | <i class="fa fa-check fa-lg"></i> |
 | -skip-packages | -skip-packages |  |  | <i class="fa fa-check fa-lg"></i> |
@@ -42,8 +42,8 @@ The current page is stating the status of scaladoc settings. The related Github
 | -expand-all-types | _ | | Setting has been removed | <i class="fa fa-times fa-lg"></i> |
 | -groups | -groups | | | <i class="fa fa-check fa-lg"></i> | 
 | -no-java-comments | _ |  | We don't need this in Scala3 |  <i class="fa fa-check fa-lg"></i> |
-| -doc-canonical-base-url | -doc-canonical-base-url |  A base URL to use as prefix and add `canonical` URLs to all pages. The canonical URL may be used by search engines to choose the URL that you want people to see in search results. If unset no canonical URLs are generated. | Fixed by [#11965](https://github.com/lampepfl/dotty/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
-| -private | -private | Show all types and members. Unless specified, show only public and protected types and members. | Fixed by [#11965](https://github.com/lampepfl/dotty/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
+| -doc-canonical-base-url | -doc-canonical-base-url |  A base URL to use as prefix and add `canonical` URLs to all pages. The canonical URL may be used by search engines to choose the URL that you want people to see in search results. If unset no canonical URLs are generated. | Fixed by [#11965](https://github.com/scala/scala3/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
+| -private | -private | Show all types and members. Unless specified, show only public and protected types and members. | Fixed by [#11965](https://github.com/scala/scala3/issues/11965) | <i class="fa fa-check fa-lg"></i> | 
 | _ | -siteroot | | We don't backport it to old scaladoc | N/A |
 | _ | -project-logo | | Should we backport it to the old scaladoc? | N/A |
 | _ | -comment-syntax | | We don't backport it to the old scaladoc | N/A |
diff --git a/_overviews/scala3-migration/tooling-migration-mode.md b/_overviews/scala3-migration/tooling-migration-mode.md
index 1bcc4d0b0..82c79bc69 100644
--- a/_overviews/scala3-migration/tooling-migration-mode.md
+++ b/_overviews/scala3-migration/tooling-migration-mode.md
@@ -11,7 +11,7 @@ The Scala 3 compiler provides some helpful utilities to ease the migration.
 
 Try running `scalac` to have a glimpse of those utilities:
 
-> `scalac` is the executable of the Scala compiler, it can be downloaded from [Github](https://github.com/lampepfl/dotty/releases/).
+> `scalac` is the executable of the Scala compiler, it can be downloaded from [Github](https://github.com/scala/scala3/releases/).
 > 
 > It can also be installed using Coursier with `cs install scala3-compiler`, in which case `scalac` is aliased `scala3-compiler`.
 
diff --git a/_overviews/scala3-scaladoc/docstrings.md b/_overviews/scala3-scaladoc/docstrings.md
index f1036b3d2..0aed8c373 100644
--- a/_overviews/scala3-scaladoc/docstrings.md
+++ b/_overviews/scala3-scaladoc/docstrings.md
@@ -52,7 +52,7 @@ In the example above, this Scaladoc comment is associated with the method square
 
 Scaladoc comments can go before fields, methods, classes, traits, objects.
 For now, scaladoc doesn't support straightforward solution to document packages. There is a dedicated github
-[issue](https://github.com/lampepfl/dotty/issues/11284), where you can check the current status of the problem.
+[issue](https://github.com/scala/scala3/issues/11284), where you can check the current status of the problem.
 
 For class primary constructors which in Scala coincide with the definition of the class itself, a @constructor tag is used to target a comment to be put on the primary constructor documentation rather than the class overview.
 
diff --git a/_overviews/scala3-scaladoc/settings.md b/_overviews/scala3-scaladoc/settings.md
index fe93ad639..9408e6d9c 100644
--- a/_overviews/scala3-scaladoc/settings.md
+++ b/_overviews/scala3-scaladoc/settings.md
@@ -12,7 +12,7 @@ This chapter lists the configuration options that can be used when calling scala
 ## Parity with scaladoc for Scala 2
 
 Scaladoc has been rewritten from scratch and some of the features turned out to be useless in the new context.
-If you want to know what is current state of compatibility with scaladoc old flags, you can visit this issue for tracking [progress](https://github.com/lampepfl/dotty/issues/11907).
+If you want to know what is current state of compatibility with scaladoc old flags, you can visit this issue for tracking [progress](https://github.com/scala/scala3/issues/11907).
 
 ## Providing settings
 
@@ -49,7 +49,7 @@ Revision (branch or ref) used to build project. Useful with sourcelinks to preve
 Source links provide a mapping between file in documentation and code repository.
 
 Example source links is:
-`-source-links:docs=github://lampepfl/dotty/master#docs`
+`-source-links:docs=github://scala/scala3/main#docs`
 
 Accepted formats:
 
@@ -87,7 +87,7 @@ A mapping is of the form `<regex>::[scaladoc3|scaladoc|javadoc]::<path>`. You ca
 
 Links to social sites. For example:
 
-`-social-links:github::https://github.com/lampepfl/dotty,discord::https://discord.com/invite/scala,twitter::https://twitter.com/scala_lang`
+`-social-links:github::https://github.com/scala/scala3,discord::https://discord.com/invite/scala,twitter::https://twitter.com/scala_lang`
 
 Valid values are of the form: `[github|twitter|gitter|discord]::link`. Scaladoc also supports `custom::link::white_icon_name::black_icon_name`. In this case icons must be present in `images/` directory.
 
diff --git a/_ru/scala3/contribute-to-docs.md b/_ru/scala3/contribute-to-docs.md
index a96a1a0fa..d01570ac6 100644
--- a/_ru/scala3/contribute-to-docs.md
+++ b/_ru/scala3/contribute-to-docs.md
@@ -61,8 +61,8 @@ language: ru
 ## Справочник по языку Scala 3
 [Справочник по Scala 3]({{ site.scala3ref }}) содержит формальное представление и подробную техническую информацию о различных возможностях языка.
 
-- [Исходники](https://github.com/lampepfl/dotty/tree/main/docs/_docs)
-- [Вопросы](https://github.com/lampepfl/dotty/issues)
+- [Исходники](https://github.com/scala/scala3/tree/main/docs/_docs)
+- [Вопросы](https://github.com/scala/scala3/issues)
 
 
 [scala3-book]: {% link _overviews/scala3-book/introduction.md %}
diff --git a/_ru/scala3/guides/scaladoc/docstrings.md b/_ru/scala3/guides/scaladoc/docstrings.md
index c537b39da..6ba32d082 100644
--- a/_ru/scala3/guides/scaladoc/docstrings.md
+++ b/_ru/scala3/guides/scaladoc/docstrings.md
@@ -52,7 +52,7 @@ Scaladoc расширяет возможности Markdown дополнител
 
 Комментарии Scaladoc могут идти перед полями, методами, классами, трейтами, объектами. 
 На данный момент scaladoc не поддерживает прямое решение для документирования пакетов. 
-На гитхабе есть специальный [issue](https://github.com/lampepfl/dotty/issues/11284), где вы можете проверить текущий статус проблемы.
+На гитхабе есть специальный [issue](https://github.com/scala/scala3/issues/11284), где вы можете проверить текущий статус проблемы.
 
 Для первичных конструкторов класса, которые в Scala совпадают с определением самого класса, 
 тег @constructor используется для указания комментария, помещаемого в документацию первичных конструкторов, а не в обзор класса.
diff --git a/_ru/scala3/guides/scaladoc/settings.md b/_ru/scala3/guides/scaladoc/settings.md
index c36dedb13..9ce45e154 100644
--- a/_ru/scala3/guides/scaladoc/settings.md
+++ b/_ru/scala3/guides/scaladoc/settings.md
@@ -13,7 +13,7 @@ previous-page: snippet-compiler
 ## Изменения scaladoc по сравнению со Scala 2
 
 Scaladoc был переписан с нуля, и некоторые функции оказались бесполезными в новом контексте.
-Текущее состояние совместимости со старыми флагами scaladoc можно увидеть [здесь](https://github.com/lampepfl/dotty/issues/11907).
+Текущее состояние совместимости со старыми флагами scaladoc можно увидеть [здесь](https://github.com/scala/scala3/issues/11907).
 
 ## Указание настроек
 
@@ -63,7 +63,7 @@ Compile / doc / scalacOptions ++= Seq("-project", "my-project"),
 Ссылки на источники обеспечивают сопоставление между файлом в документации и репозиторием кода.
 
 Примеры исходных ссылок:
-`-source-links:docs=github://lampepfl/dotty/master#docs`
+`-source-links:docs=github://scala/scala3/main#docs`
 
 Принимаемые форматы:
 
@@ -99,7 +99,7 @@ Compile / doc / scalacOptions ++= Seq("-project", "my-project"),
 
 Ссылки на социальные сети. Например:
 
-`-social-links:github::https://github.com/lampepfl/dotty,discord::https://discord.com/invite/scala,twitter::https://twitter.com/scala_lang`
+`-social-links:github::https://github.com/scala/scala3,discord::https://discord.com/invite/scala,twitter::https://twitter.com/scala_lang`
 
 Допустимые значения имеют вид: `[github|twitter|gitter|discord]::link`.
 Scaladoc также поддерживает `custom::link::white_icon_name::black_icon_name`.
diff --git a/_ru/scala3/scaladoc.md b/_ru/scala3/scaladoc.md
index 969b4a468..9c3df2e7f 100644
--- a/_ru/scala3/scaladoc.md
+++ b/_ru/scala3/scaladoc.md
@@ -97,7 +97,7 @@ extension [T](arr: IArray[T]) def span(p: T => Boolean): (IArray[T], IArray[T])
 
 Обратите внимание, что эта функция все еще находится в разработке, поэтому в нее могут быть внесены значительные изменения. 
 Если вы столкнулись с ошибкой или у вас есть идея для улучшения, не стесняйтесь создавать issue на
-[Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) или [dotty](https://github.com/lampepfl/dotty/issues/new).
+[Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) или [dotty](https://github.com/scala/scala3/issues/new).
 
 [scaladoc]: /ru/scala3/guides/scaladoc/index.html
 [scaladoc-docstrings]: /ru/scala3/guides/scaladoc/docstrings.html
diff --git a/_sips/minutes/2016-08-16-sip-10th-august-minutes.md b/_sips/minutes/2016-08-16-sip-10th-august-minutes.md
index f2fe71d34..b0009109a 100644
--- a/_sips/minutes/2016-08-16-sip-10th-august-minutes.md
+++ b/_sips/minutes/2016-08-16-sip-10th-august-minutes.md
@@ -164,7 +164,7 @@ proposal or study it further.
 
 **Conclusion**: The Committee asks Dale to explicitly summarize the potential
 conflicts with tuple syntax, review the initial [HList proposal in
-Dotty](https://github.com/lampepfl/dotty/issues/964) to figure out potential
+Dotty](https://github.com/scala/scala3/issues/964) to figure out potential
 conflicts with his proposal. Eugene also proposes Dale to consider whether the
 Committee can salvage non-controversial parts of this proposal and reduce this
 SIP just to them, as well as discussing the utility of having two ways of doing
diff --git a/_sips/minutes/2018-08-30-sip-minutes.md b/_sips/minutes/2018-08-30-sip-minutes.md
index 164bf6e3c..218877a1d 100644
--- a/_sips/minutes/2018-08-30-sip-minutes.md
+++ b/_sips/minutes/2018-08-30-sip-minutes.md
@@ -68,7 +68,7 @@ Decision / voting / postponing the discussion
 
 **Miles Sabin**  summarised discussion on Contributors thread.
 - Focuses on the Contributors discussion rather than on the proposal itself
-- Underlines a lack of motivation in the light of a separate issue from [Dotty: Weak eta-expansion](https://github.com/lampepfl/dotty/issues/2570)
+- Underlines a lack of motivation in the light of a separate issue from [Dotty: Weak eta-expansion](https://github.com/scala/scala3/issues/2570)
 - Concludes that this proposal should be aligned with eta-extension issue
 
 Summary:
@@ -77,9 +77,9 @@ References
 
 + [Scala Contributors thread](https://contributors.scala-lang.org/t/proposal-to-remove-auto-application-from-the-language/2145).
 
-+ [Dotty issue: Weak eta-expansion](https://github.com/lampepfl/dotty/issues/2570).
++ [Dotty issue: Weak eta-expansion](https://github.com/scala/scala3/issues/2570).
 
-+ [Martin's comment on the issue above](https://github.com/lampepfl/dotty/issues/2570#issuecomment-306202339).
++ [Martin's comment on the issue above](https://github.com/scala/scala3/issues/2570#issuecomment-306202339).
 
 Comments
 
diff --git a/_sips/minutes/2018-11-26-sip-minutes.md b/_sips/minutes/2018-11-26-sip-minutes.md
index 6b9bc8f10..776257508 100644
--- a/_sips/minutes/2018-11-26-sip-minutes.md
+++ b/_sips/minutes/2018-11-26-sip-minutes.md
@@ -49,7 +49,7 @@ The SIP Committee gathered for the first time face-to-face, for an extensive 3-d
 - Outline an action plan within a set time-frame;
 - Other: Unanimously voted for Guillaume Martres to join the Committee.
 
-*Better understanding* was enabled by in depth presentations and Q&As with the EPFL Dotty team; *the Approach* was agreed upon the first day which resulted in creating “FAQs about Scala 3” (see below) and *the Action Plan* was outlined and is still under construction; several issues were opened (please see the list at the end of this document) and a project plan ["Meta-programming in Scala 3"](https://github.com/lampepfl/dotty/issues/5489) has been developed.
+*Better understanding* was enabled by in depth presentations and Q&As with the EPFL Dotty team; *the Approach* was agreed upon the first day which resulted in creating “FAQs about Scala 3” (see below) and *the Action Plan* was outlined and is still under construction; several issues were opened (please see the list at the end of this document) and a project plan ["Meta-programming in Scala 3"](https://github.com/scala/scala3/issues/5489) has been developed.
 
 As the most important points and summary is reflected in “FAQs about Scala 3”, it will stand as an official “minutes” for this unique SIP meeting.
 
@@ -144,20 +144,20 @@ The dependency of Scala 2 macros and reflection on internal implementation detai
 We recognize that important parts of the Scala ecosystem have made essential use of the Scala 2 facilities and that it is vital that as many as possible of these use cases be accommodated in Scala 3 in some form or another. This will be disruptive, but we hope to mitigate the disruption by providing facilities which make the more straightforward and important scenarios simpler while still leaving others possible.
 Our direction is still evolving; however we believe that replacing the current excessively general and expressive macro system with a suite of less powerful but complementary tools is the way forward.
 Currently we are exploring options which range from improved support for type level programming in the language itself (eg. specialized inline, match types, stable definitions, GADT improvements); intrinsifying certain features currently supported by macros (eg. by-name implicits, generic programming primitives); through to less general forms of metaprogramming (quote/splice and staging) and portable reflection via Tasty (which we [recommend](https://github.com/scalacenter/advisoryboard/pull/40)) to support in both Scala 2/3 and via compiler-independent libraries and tools. We recommend that most current uses of Scala macros and reflection can be accommodated by some combination of these tools.
-For more about the project's progress, please see https://github.com/lampepfl/dotty/issues/5489
+For more about the project's progress, please see https://github.com/scala/scala3/issues/5489
 
 ### How do we plan to address language experimentation?
 We acknowledge that language experimentation is necessary for improving the language. We also believe it requires a different vehicle than stable Scala releases. We don’t have a concrete solution for now, but we’re working on one.
 
 ### Other “documents” created during the meetings:
 
-[SIP: Structural Types](https://github.com/lampepfl/dotty/issues/5372)
+[SIP: Structural Types](https://github.com/scala/scala3/issues/5372)
 
-[SIP: TASTY changes](https://github.com/lampepfl/dotty/issues/5378)
+[SIP: TASTY changes](https://github.com/scala/scala3/issues/5378)
 
-[SIP: Underscore Syntax for Type Lambdas](https://github.com/lampepfl/dotty/issues/5379)
+[SIP: Underscore Syntax for Type Lambdas](https://github.com/scala/scala3/issues/5379)
 
-[Should we bring back rewrite methods?](https://github.com/lampepfl/dotty/issues/5381)
+[Should we bring back rewrite methods?](https://github.com/scala/scala3/issues/5381)
 
 [Features work progress overview](https://docs.google.com/spreadsheets/d/1GWJUo0U3JbBtrfg5vqgb6H5S6wlU5HnTxebLcHwD1zw/edit?usp=sharing)
 
diff --git a/_sips/minutes/2019-03-13-sip-minutes.md b/_sips/minutes/2019-03-13-sip-minutes.md
index 7668b7720..80854b32e 100644
--- a/_sips/minutes/2019-03-13-sip-minutes.md
+++ b/_sips/minutes/2019-03-13-sip-minutes.md
@@ -404,7 +404,7 @@ import implied
 
 Martin: there's a PR, not yet merged, that refines this rule considerably compared to what's on the Dotty feature page?
 
-It's [https://github.com/lampepfl/dotty/pull/6041](https://github.com/lampepfl/dotty/pull/6041) -- it has the new impl as well as the changes to the web page.
+It's [https://github.com/scala/scala3/pull/6041](https://github.com/scala/scala3/pull/6041) -- it has the new impl as well as the changes to the web page.
 
 Martin: we now have a custom error message so if something fails but changing import to import implied would fix it, the compiler will tell you.
 
@@ -508,7 +508,7 @@ What's the metaprogramming status?
 
 Martin: quote and splice are stable, but don't support pattern matching yet. TASTY reflection is not complete yet and is still undergoing revisions based on use cases that are being tried.
 
-No one has done any meaningful whitebox macros yet in the new system, but the door is now open. (<-- not sure if I should include this in the notes without understanding in what context we want to allow whitebox macros?) This only got merged "last week". The relevant PR is [https://github.com/lampepfl/dotty/pull/5846](https://github.com/lampepfl/dotty/pull/5846) "The main motivation for moving staging to typer is to support whitebox macros" but it's still very early days, no one has tried to actually use this.
+No one has done any meaningful whitebox macros yet in the new system, but the door is now open. (<-- not sure if I should include this in the notes without understanding in what context we want to allow whitebox macros?) This only got merged "last week". The relevant PR is [https://github.com/scala/scala3/pull/5846](https://github.com/scala/scala3/pull/5846) "The main motivation for moving staging to typer is to support whitebox macros" but it's still very early days, no one has tried to actually use this.
 
 # **Kind polymorphism**
 
@@ -554,7 +554,7 @@ Questions about the magic automatic extends clauses, how does the compiler know,
 
 "Generally, all covariant type parameters of the enum class are minimized in a compiler-generated extends clause whereas all contravariant type parameters are maximized", says the doc
 
-There was some discussion of the details of the rules for type parameters -- this then erupted into a full-on debate. e.g. isn't it weird that if you add an extends clause, suddenly T isn't in scope any more? see [https://github.com/lampepfl/dotty/pull/6095](https://github.com/lampepfl/dotty/pull/6095)
+There was some discussion of the details of the rules for type parameters -- this then erupted into a full-on debate. e.g. isn't it weird that if you add an extends clause, suddenly T isn't in scope any more? see [https://github.com/scala/scala3/pull/6095](https://github.com/scala/scala3/pull/6095)
 
 conclusion: Martin: I'll try to update the rules to reflect the behavior of the compiler.
 
diff --git a/_sips/minutes/2019-06-08-sip-minutes.md b/_sips/minutes/2019-06-08-sip-minutes.md
index 30072129b..247472ece 100644
--- a/_sips/minutes/2019-06-08-sip-minutes.md
+++ b/_sips/minutes/2019-06-08-sip-minutes.md
@@ -28,7 +28,7 @@ apart from the other implicits changes
 
 ### Auto-tupling
 
-Implemented but not merged: [https://github.com/lampepfl/dotty/pull/4311](https://github.com/lampepfl/dotty/pull/4311)
+Implemented but not merged: [https://github.com/scala/scala3/pull/4311](https://github.com/scala/scala3/pull/4311)
 
 The problem is when using infix (e.g. an operator method) there's confusion between a 1-argument tuple2 method
 and a 2-argument method, of which there are a few in the standard library.
@@ -96,7 +96,7 @@ Adriaan: Also let's not forget the big Scaladoc impact, can't copy because of th
 
 ### Polymorphic function types
 
-Merged but not documented: [https://github.com/lampepfl/dotty/pull/4672](https://github.com/lampepfl/dotty/pull/4672)
+Merged but not documented: [https://github.com/scala/scala3/pull/4672](https://github.com/scala/scala3/pull/4672)
 
 Presented by Guillaume.
 
diff --git a/_sips/minutes/2020-03-12-minutes.md b/_sips/minutes/2020-03-12-minutes.md
index c83443462..4e40af5e3 100644
--- a/_sips/minutes/2020-03-12-minutes.md
+++ b/_sips/minutes/2020-03-12-minutes.md
@@ -128,7 +128,7 @@ Run through https://dotty.epfl.ch/docs/reference/metaprogramming/inline.html
 * Gui: inline interacts with overriding
 * Nic: if in a subclass (say Range) you override a method (say foreach) with `inline` it only inlines if the type is cast
 * Seb: I need both, inline if statically the type is Range, and use the optimised override if it's a Seq that's a Range at runtime
-* (After the meeting, this led to [lampepfl/dotty#8543](https://github.com/lampepfl/dotty/pull/8543) and [lampepfl/dotty#8564](https://github.com/lampepfl/dotty/issues/8564).)
+* (After the meeting, this led to [scala/scala3#8543](https://github.com/scala/scala3/pull/8543) and [scala/scala3#8564](https://github.com/scala/scala3/issues/8564).)
 * Lukas: `inline` is perfect for macros, but it shouldn't exist for performance.  The runtime is where performance should be fixed (and it's in a better position to do it)
 * Lukas: inlining isn't on by default (in Scala 2) because it interacts with binary compatibility in non-obvious ways, and `inline` in Dotty does the same
 
@@ -144,7 +144,7 @@ Run through https://dotty.epfl.ch/docs/reference/metaprogramming/reflection.html
 
 ### Review match types
 
-Review https://github.com/dotty-staging/dotty/blob/fix-6709/docs/docs/reference/new-types/match-types.md (part of https://github.com/lampepfl/dotty/pull/8024)
+Review https://github.com/dotty-staging/dotty/blob/fix-6709/docs/docs/reference/new-types/match-types.md (part of https://github.com/scala/scala3/pull/8024)
 
 ```scala
 type LeafElem[X] = X match {
@@ -157,7 +157,7 @@ type LeafElem[X] = X match {
 
 * Olivier: The order of match type definitions is significant
 * Olivier: The disjointness is between `X` and `String`, not between `String` and `Array`
-* Olivier: See https://github.com/lampepfl/dotty/issues/8493 as an example of disjointness requirement (can't use traits)
+* Olivier: See https://github.com/scala/scala3/issues/8493 as an example of disjointness requirement (can't use traits)
 * Martin: Currently the use-cases can be implemented like Generic
 * Olivier: Put at a very high level, the intent is to remove some of the computation that happens in implicits and do it (better) in match types
 * Olivier: another problem is that when you type-check a type you can stackoverflow, which has bad UX, particularly given we have recursive types
diff --git a/_sips/minutes/2020-03-13-sip-minutes.md b/_sips/minutes/2020-03-13-sip-minutes.md
index 405755918..7e394ea55 100644
--- a/_sips/minutes/2020-03-13-sip-minutes.md
+++ b/_sips/minutes/2020-03-13-sip-minutes.md
@@ -285,8 +285,8 @@ Martin:
 - Used widely in compiler codebase for 6 months
   - Does find is necessary to have vertical bars in editor for indentation
 - Examples at:
-  - https://github.com/lampepfl/dotty/blob/master/compiler/src/dotty/tools/dotc/semanticdb/ExtractSemanticDB.scala
-  - https://github.com/lampepfl/dotty/blob/master/compiler/src/dotty/tools/dotc/typer/Nullables.scala
+  - https://github.com/scala/scala3/blob/main/compiler/src/dotty/tools/dotc/semanticdb/ExtractSemanticDB.scala
+  - https://github.com/scala/scala3/blob/main/compiler/src/dotty/tools/dotc/typer/Nullables.scala
 - `then` in if expression was harder to get used to
 
 Guillaume:
@@ -424,7 +424,7 @@ Sébastien:
 - Asks if the new rules allow to add an implicit definition of a priority in-between two other definitions while preserving binary compatability?
 
 Martin, in response:
-- Shows a [demo](https://github.com/lampepfl/dotty/blob/master/tests/run/implied-priority.scala) of how to insert a new implicit in between existing definitions.
+- Shows a [demo](https://github.com/scala/scala3/blob/main/tests/run/implied-priority.scala) of how to insert a new implicit in between existing definitions.
 - The new scheme of priorities is more simple to grow than before because inheritance is fragile
 
 Sébastien is satisfied with the demo, is fine either way to add to 3.0 or later. Someone should champion it.
diff --git a/_sips/sips/binary-api.md b/_sips/sips/binary-api.md
index 899730483..ba3fc8f01 100644
--- a/_sips/sips/binary-api.md
+++ b/_sips/sips/binary-api.md
@@ -32,7 +32,7 @@ Currently, the compiler automatically generates accessors for references to priv
 * Changing the implementation of an inline definition can be a binary incompatible change
 * Removing final from a class is a binary incompatible change
 
-You can find more details in [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
+You can find more details in [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
 
 ### Avoid duplication of inline accessors
 
@@ -248,7 +248,7 @@ Using references to `@publicInBinary` in inline code can cause binary incompatib
 ### Add a `@binaryAccessor`
 This annotation would generate an stable accessor. This annotation could be used on `private` definition. It would also mitigate [migration costs](https://gist.github.com/nicolasstucki/003f7293941836b08a0d53dbcb913e3c) for library authors that have published unstable accessors.
 
-* Implementation https://github.com/lampepfl/dotty/pull/16992
+* Implementation https://github.com/scala/scala3/pull/16992
 
 
 ### Make all `private[C]` part of the binary API
@@ -267,9 +267,9 @@ The drawback of this approach is that that we would need to force users to keep
 
 ## Related work
 
-* Initial discussions: [https://github.com/lampepfl/dotty/issues/16983](https://github.com/lampepfl/dotty/issues/16983)
-* Initial proof of concept (outdated): [https://github.com/lampepfl/dotty/pull/16992](https://github.com/lampepfl/dotty/pull/16992)
-* Single annotation proof of concept: [https://github.com/lampepfl/dotty/pull/18402](https://github.com/lampepfl/dotty/pull/18402)
+* Initial discussions: [https://github.com/scala/scala3/issues/16983](https://github.com/scala/scala3/issues/16983)
+* Initial proof of concept (outdated): [https://github.com/scala/scala3/pull/16992](https://github.com/scala/scala3/pull/16992)
+* Single annotation proof of concept: [https://github.com/scala/scala3/pull/18402](https://github.com/scala/scala3/pull/18402)
 * Community migration analysis: [Gist](https://gist.github.com/nicolasstucki/003f7293941836b08a0d53dbcb913e3c)
 * Kotlin: [PublishedApi](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-published-api/) plays the same role as `@publicInBinary`
   but its interaction with (inline definitions)[https://kotlinlang.org/docs/inline-functions.html#restrictions-for-public-api-inline-functions]
diff --git a/_sips/sips/byname-implicits.md b/_sips/sips/byname-implicits.md
index 4e47f9765..b9a33eb45 100644
--- a/_sips/sips/byname-implicits.md
+++ b/_sips/sips/byname-implicits.md
@@ -39,7 +39,7 @@ the knot" implicitly.
 
 ### Implementation status
 
-Byname implicits have been implemented in [Dotty](https://github.com/lampepfl/dotty/issues/1998)
+Byname implicits have been implemented in [Dotty](https://github.com/scala/scala3/issues/1998)
 with an earlier iteration of the divergence checking algorithm described below. A full
 implementation of this proposal exists as a [pull request](https://github.com/scala/scala/pull/6050)
 relative to the 2.13.x branch of the Lightbend Scala compiler and it is scheduled to be included in
@@ -851,7 +851,7 @@ object Test {
 
 because the path `foo` in `foo.Out` is not stable. Full parity with shapeless's `Lazy` would require
 lazy (rather than byname) implicit parameters (see [this Dotty
-ticket](https://github.com/lampepfl/dotty/issues/3005) for further discussion) and is orthogonal to
+ticket](https://github.com/scala/scala3/issues/3005) for further discussion) and is orthogonal to
 this SIP in that they would drop out of support for lazy parameters more generally, as described in
 [this Scala ticket](https://github.com/scala/bug/issues/240).
 
diff --git a/_sips/sips/clause-interleaving.md b/_sips/sips/clause-interleaving.md
index 120271e8d..65fb815f8 100644
--- a/_sips/sips/clause-interleaving.md
+++ b/_sips/sips/clause-interleaving.md
@@ -167,7 +167,7 @@ As discussed above, we may want to consider generalizing class parameter lists a
 
 ## Related work
 * Pre-SIP: [https://contributors.scala-lang.org/t/clause-interweaving-allowing-def-f-t-x-t-u-y-u/5525](https://contributors.scala-lang.org/t/clause-interweaving-allowing-def-f-t-x-t-u-y-u/5525)
-* An implementation of the proposal is available as a pull request at [https://github.com/lampepfl/dotty/pull/14019](https://github.com/lampepfl/dotty/pull/14019)
+* An implementation of the proposal is available as a pull request at [https://github.com/scala/scala3/pull/14019](https://github.com/scala/scala3/pull/14019)
 
 ## FAQ
 Currently empty.
diff --git a/_sips/sips/fewer-braces.md b/_sips/sips/fewer-braces.md
index 4d1f9c109..e6541ac4c 100644
--- a/_sips/sips/fewer-braces.md
+++ b/_sips/sips/fewer-braces.md
@@ -131,7 +131,7 @@ If there would be code using these idioms, it can be rewritten quite simply to a
 
 ### Tooling
 
-Since this affects parsing, the scalameta parser and any other parser used in an IDE will also need to be updated. The necessary changes to the Scala 3 parser were made here: https://github.com/lampepfl/dotty/pull/15273/commits. The commit that embodies the core change set is here: https://github.com/lampepfl/dotty/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a.
+Since this affects parsing, the scalameta parser and any other parser used in an IDE will also need to be updated. The necessary changes to the Scala 3 parser were made here: https://github.com/scala/scala3/pull/15273/commits. The commit that embodies the core change set is here: https://github.com/scala/scala3/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a.
 
 ### Handling Edge Cases
 
@@ -288,7 +288,7 @@ This is a tradeoff between conciseness and consistency. In the interest of minim
 
  - Doc page for proposed change: https://dotty.epfl.ch/docs/reference/other-new-features/indentation.html#variant-indentation-marker--for-arguments
 
- - Merged PR implementing the proposal under experimental flag: https://github.com/lampepfl/dotty/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
+ - Merged PR implementing the proposal under experimental flag: https://github.com/scala/scala3/pull/15273/commits/421bdd660b0456c2ff1ae386f032c41bb1e0212a
 
  - Latest discussion on contributors (there were several before when we discussed indentation in general): https://contributors.scala-lang.org/t/make-fewerbraces-available-outside-snapshot-releases/5024/166
 
diff --git a/_sips/sips/interpolation-quote-escape.md b/_sips/sips/interpolation-quote-escape.md
index 4639fc615..8385ed17a 100644
--- a/_sips/sips/interpolation-quote-escape.md
+++ b/_sips/sips/interpolation-quote-escape.md
@@ -129,4 +129,4 @@ proposals.
 [^4]: https://github.com/scala/bug/issues/6476#issuecomment-292412577 "@retronym said: +1 to s"$"". Because it doesn't compile today, we don't risk changing the meaning of existing programs."
 [^5]: https://github.com/Scala/Scala/pull/6953/files#diff-0023b3bfa053fb16603156b785efa7ad ""
 [^6]: https://github.com/Scala/Scala/pull/4308 "SI-6476 Accept escaped quotes in interp strings"
-[^7]: https://github.com/lampepfl/dotty/pull/7486 "PR in dotty"
+[^7]: https://github.com/scala/scala3/pull/7486 "PR in scala3"
diff --git a/_sips/sips/match-types-spec.md b/_sips/sips/match-types-spec.md
index 1624e64cc..a48500f50 100644
--- a/_sips/sips/match-types-spec.md
+++ b/_sips/sips/match-types-spec.md
@@ -95,7 +95,7 @@ It is however not possible to guarantee that property for *all* cases, since the
 #### Preamble
 
 Some of the concepts mentioned here are defined in the existing Scala 3 specification draft.
-That draft can be found in the dotty repository at https://github.com/lampepfl/dotty/tree/main/docs/_spec.
+That draft can be found in the dotty repository at https://github.com/scala/scala3/tree/main/docs/_spec.
 It is not rendered anywhere yet, though.
 
 Here are some of the relevant concepts that are perhaps lesser-known:
@@ -573,7 +573,7 @@ Notable prior work related to this proposal includes:
 - [Current reference page for Scala 3 match types](https://dotty.epfl.ch/docs/reference/new-types/match-types.html)
 - [Abstractions for Type-Level Programming](https://infoscience.epfl.ch/record/294024), Olivier Blanvillain, Chapter 4 (Match Types)
 - ["Pre-Sip" discussion in the Contributors forum](https://contributors.scala-lang.org/t/pre-sip-proper-specification-for-match-types/6265) (submitted at the same time as this SIP document)
-- [PR with the proposed implementation](https://github.com/lampepfl/dotty/pull/18262)
+- [PR with the proposed implementation](https://github.com/scala/scala3/pull/18262)
 
 ## FAQ
 
diff --git a/_sips/sips/multi-source-extension-overloads.md b/_sips/sips/multi-source-extension-overloads.md
index a8a0637a7..ab41056ae 100644
--- a/_sips/sips/multi-source-extension-overloads.md
+++ b/_sips/sips/multi-source-extension-overloads.md
@@ -226,7 +226,7 @@ A number of alternatives were mentioned in [the Contributors thread](https://con
 ## Related work
 
 - [Contributors thread acting as de facto Pre-SIP](https://contributors.scala-lang.org/t/change-shadowing-mechanism-of-extension-methods-for-on-par-implicit-class-behavior/5831)
-- [Pull Request in dotty](https://github.com/lampepfl/dotty/pull/17050) to support it under an experimental import
+- [Pull Request in dotty](https://github.com/scala/scala3/pull/17050) to support it under an experimental import
 
 ## FAQ
 
diff --git a/_sips/sips/polymorphic-eta-expansion.md b/_sips/sips/polymorphic-eta-expansion.md
index bd64ea84b..ce38bca4b 100644
--- a/_sips/sips/polymorphic-eta-expansion.md
+++ b/_sips/sips/polymorphic-eta-expansion.md
@@ -420,7 +420,7 @@ No other alternatives have been imagined, the similarity between this proposal a
 - If there is already a proof-of-concept implementation, a link to it will be welcome here. -->
 
 * Pre-SIP: https://contributors.scala-lang.org/t/polymorphic-eta-expansion/5516
-* A naive implementation can be found at https://github.com/lampepfl/dotty/pull/14015 (it is more general than this proposal and thus breaks compatibility)
+* A naive implementation can be found at https://github.com/scala/scala3/pull/14015 (it is more general than this proposal and thus breaks compatibility)
 * A compatibility-preserving implementation is in development.
 
 
diff --git a/_sips/sips/priority-based-infix-type-precedence.md b/_sips/sips/priority-based-infix-type-precedence.md
index 71d32c1ce..218913020 100644
--- a/_sips/sips/priority-based-infix-type-precedence.md
+++ b/_sips/sips/priority-based-infix-type-precedence.md
@@ -137,7 +137,7 @@ However, it is very unlikely that such interaction would occur.
 
 **Related Issues**
 
-* [Dotty Issue #1961](https://github.com/lampepfl/dotty/issues/1961)
+* [Dotty Issue #1961](https://github.com/scala/scala3/issues/1961)
 
 
 ## Backward Compatibility
diff --git a/_sips/sips/quote-pattern-type-variable-syntax.md b/_sips/sips/quote-pattern-type-variable-syntax.md
index 92d1ce83f..a6080d7a0 100644
--- a/_sips/sips/quote-pattern-type-variable-syntax.md
+++ b/_sips/sips/quote-pattern-type-variable-syntax.md
@@ -59,11 +59,11 @@ We want to be able to set the bounds of type variables to be able to match again
 ```scala
 case '[ head *: tail ] => h[tail]
 ```
-See [https://github.com/lampepfl/dotty/issues/11738](https://github.com/lampepfl/dotty/issues/11738).
+See [https://github.com/scala/scala3/issues/11738](https://github.com/scala/scala3/issues/11738).
 
 ### Support matching on any kind of type
 We want to match against higher-kinded (or `AnyKind`) types. This is not possible due to the default upper bound of `Any`.
-See [https://github.com/lampepfl/dotty/issues/10864](https://github.com/lampepfl/dotty/issues/10864).
+See [https://github.com/scala/scala3/issues/10864](https://github.com/scala/scala3/issues/10864).
 
 ### Support multiple references to the same type in quoted type patterns
 We want to be able to match using several references to the same type variable.
@@ -135,7 +135,7 @@ TASTy only contains explicit type variable definitions, and this encoding would
 
 ## Related work
 
-* Proof of concept of type variable syntax: [https://github.com/lampepfl/dotty/pull/16910](https://github.com/lampepfl/dotty/pull/16910)
-* Proof of concept of backticks (only interested in the first bullet point): [https://github.com/lampepfl/dotty/pull/16935](https://github.com/lampepfl/dotty/pull/16935)
+* Proof of concept of type variable syntax: [https://github.com/scala/scala3/pull/16910](https://github.com/scala/scala3/pull/16910)
+* Proof of concept of backticks (only interested in the first bullet point): [https://github.com/scala/scala3/pull/16935](https://github.com/scala/scala3/pull/16935)
 
 <!-- ## FAQ -->
diff --git a/_sips/sips/trait-parameters.md b/_sips/sips/trait-parameters.md
index 93bcd8bf7..633f0c0b7 100644
--- a/_sips/sips/trait-parameters.md
+++ b/_sips/sips/trait-parameters.md
@@ -69,4 +69,4 @@ the evaluation order would be `e1`, initializer of `T`, `e2`, initializer of `V`
 
 ## See Also ##
 
-[Dotty Issue #640](https://github.com/lampepfl/dotty/issues/640)
+[Dotty Issue #640](https://github.com/scala/scala3/issues/640)
diff --git a/_uk/scala3/scaladoc.md b/_uk/scala3/scaladoc.md
index f9193aa1c..66a6d1280 100644
--- a/_uk/scala3/scaladoc.md
+++ b/_uk/scala3/scaladoc.md
@@ -81,7 +81,7 @@ extension [T](arr: IArray[T]) def span(p: T => Boolean): (IArray[T], IArray[T])
 Для отримання додаткової інформації дивіться [Посібники](/scala3/guides/scaladoc/search-engine.html)
 
 Зауважте, що ця функція все ще знаходиться на стадії розробки, тому вона може зазнати значних змін.
-Якщо ви зіткнулися з помилкою або маєте ідею щодо покращення, не соромтеся створювати проблему на [Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) або [dotty](https://github.com/lampepfl/dotty/issues/new).
+Якщо ви зіткнулися з помилкою або маєте ідею щодо покращення, не соромтеся створювати проблему на [Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) або [dotty](https://github.com/scala/scala3/issues/new).
 
 [scaladoc-docstrings]: {% link _overviews/scala3-scaladoc/docstrings.md %}
 [static-documentation]: {% link _overviews/scala3-scaladoc/static-site.md %}
diff --git a/_zh-cn/scala3/reference/README.md b/_zh-cn/scala3/reference/README.md
index 4606ed70d..960554be5 100644
--- a/_zh-cn/scala3/reference/README.md
+++ b/_zh-cn/scala3/reference/README.md
@@ -1,5 +1,5 @@
-https://docs.scala-lang.org/scala3/reference 的页面内容是从 [Scala 3 编译器库](https://github.com/lampepfl/dotty) 生成的。
+https://docs.scala-lang.org/scala3/reference 的页面内容是从 [Scala 3 编译器库](https://github.com/scala/scala3) 生成的。
 
 请到这里为 Scala 3 参考文档做贡献：
 
-https://github.com/lampepfl/dotty/tree/main/docs/_docs
+https://github.com/scala/scala3/tree/main/docs/_docs
diff --git a/scala3/contribute-to-docs.md b/scala3/contribute-to-docs.md
index ca9201c5b..319660058 100644
--- a/scala3/contribute-to-docs.md
+++ b/scala3/contribute-to-docs.md
@@ -56,8 +56,8 @@ contains a comprehensive overview over contribution to and internals of the Scal
 ## Scala 3 Language Reference
 The [Scala 3 reference]({{ site.scala3ref }}) contains a formal presentation and detailed technical information about the various features of the language.
 
-- [Sources](https://github.com/lampepfl/dotty/tree/main/docs/_docs)
-- [Issues](https://github.com/lampepfl/dotty/issues)
+- [Sources](https://github.com/scala/scala3/tree/main/docs/_docs)
+- [Issues](https://github.com/scala/scala3/issues)
 
 
 [scala3-book]: {% link _overviews/scala3-book/introduction.md %}
diff --git a/scala3/reference/README.md b/scala3/reference/README.md
index b23145e7f..418bdbe3e 100644
--- a/scala3/reference/README.md
+++ b/scala3/reference/README.md
@@ -1,6 +1,6 @@
 The content of the pages https://docs.scala-lang.org/scala3/reference is 
-generated from the [Scala 3 compiler repository](https://github.com/lampepfl/dotty).
+generated from the [Scala 3 compiler repository](https://github.com/scala/scala3).
 
 Please go here to contribute to the Scala 3 reference documentation:
 
-https://github.com/lampepfl/dotty/tree/main/docs/_docs
+https://github.com/scala/scala3/tree/main/docs/_docs
diff --git a/scala3/scaladoc.md b/scala3/scaladoc.md
index 92ba09827..5a735173e 100644
--- a/scala3/scaladoc.md
+++ b/scala3/scaladoc.md
@@ -79,7 +79,7 @@ This feature is provided by the [Inkuire](https://github.com/VirtusLab/Inkuire)
 For more information see [Guides](/scala3/guides/scaladoc/search-engine.html)
 
 Note that this feature is still in development, so it can be subject to considerable change.
-If you encounter a bug or have an idea for improvement, don't hesitate to create an issue on [Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) or [dotty](https://github.com/lampepfl/dotty/issues/new).
+If you encounter a bug or have an idea for improvement, don't hesitate to create an issue on [Inkuire](https://github.com/VirtusLab/Inkuire/issues/new) or [scala3](https://github.com/scala/scala3/issues/new).
 
 [scaladoc-docstrings]: {% link _overviews/scala3-scaladoc/docstrings.md %}
 [static-documentation]: {% link _overviews/scala3-scaladoc/static-site.md %}