rewrite repo location urls

docs/architecture-decisions/adr002-default-catalog-file-format.md

@@ -39,7 +39,7 @@ inside Backstage, or by push events from a CI/CD pipelines, or by webhook
 triggers from the version control system, etc.
 
 Each file describes one or more entities in accordance with the
-[Backstage System Model](https://github.com/spotify/backstage/issues/390). All
+[Backstage System Model](https://github.com/backstage/backstage/issues/390). All
 of these entities have a common structure and nomenclature, and they are stored
 in the software catalog from which they then can be queried.
 
@@ -87,7 +87,7 @@ The root envelope object has the following structure.
 ### `apiVersion` and `kind`
 
 The `kind` is the high level entity type being described, typically from the
-[Backstage system model](https://github.com/spotify/backstage/issues/390). The
+[Backstage system model](https://github.com/backstage/backstage/issues/390). The
 first versions of the catalog will focus on the `Component` kind.
 
 The `apiVersion`is the version of specification format for that particular

docs/architecture-decisions/adr007-use-msw-to-mock-service-requests.md

@@ -41,7 +41,7 @@ worker.start();
 ```
 
 and in a more real life scenario, taken from
-[CatalogClient.test.ts](https://github.com/spotify/backstage/blob/f3245c4f8f0b6b2625c4a6d5d50161b612fb4757/plugins/catalog/src/api/CatalogClient.test.ts)
+[CatalogClient.test.ts](https://github.com/backstage/backstage/blob/f3245c4f8f0b6b2625c4a6d5d50161b612fb4757/plugins/catalog/src/api/CatalogClient.test.ts)
 
 ```ts
 beforeEach(() => {

docs/architecture-decisions/adr008-default-catalog-file-name.md

@@ -11,7 +11,7 @@ While the spec for the catalog file format is well described in
 to the name of the catalog file.
 
 Following discussion in
-[Issue 1822](https://github.com/spotify/backstage/pull/1822#pullrequestreview-461253670),
+[Issue 1822](https://github.com/backstage/backstage/pull/1822#pullrequestreview-461253670),
 a decision was made.
 
 ## Name

docs/architecture-decisions/adr009-entity-references.md

@@ -13,7 +13,7 @@ There was also some confusion on how to reference entities in URLs in the
 Backstage frontend.
 
 Following discussion in
-[Issue 1947](https://github.com/spotify/backstage/issues/1947), a decision was
+[Issue 1947](https://github.com/backstage/backstage/issues/1947), a decision was
 made.
 
 ## Entity References in YAML files

docs/architecture-decisions/index.md

@@ -25,9 +25,9 @@ Records should be stored under the `architecture-decisions` directory.
 - Address and integrate feedback from the community
 - Eventually, assign a number
 - Add the path of the ADR to the microsite sidebar in
-  [`sidebars.json`](https://github.com/spotify/backstage/blob/master/microsite/sidebars.json)
+  [`sidebars.json`](https://github.com/backstage/backstage/blob/master/microsite/sidebars.json)
 - Add the path of the ADR to the
-  [`mkdocs.yml`](https://github.com/spotify/backstage/blob/master/mkdocs.yml)
+  [`mkdocs.yml`](https://github.com/backstage/backstage/blob/master/mkdocs.yml)
 - Merge the pull request
 
 ## Superseding an ADR