rewrite repo location urls

docs/auth/index.md

@@ -58,7 +58,7 @@ token used to make authenticated calls within Backstage.
 The middleware that will be provided by `@backstage/backend-common` allows
 verification of Backstage ID tokens, and optionally loading additional
 information about the user. The progress is tracked in
-https://github.com/spotify/backstage/issues/1435.
+https://github.com/backstage/backstage/issues/1435.
 
 #### Identity for App Developers
 

docs/auth/oauth.md

@@ -15,10 +15,10 @@ to various third party APIs.
 There are occasions when the user wants to perform actions towards third party
 services that require authorization via OAuth. Backstage provides standardized
 [Utility APIs](../api/utility-apis.md) such as the
-[GoogleAuthApi](https://github.com/spotify/backstage/blob/master/packages/core-api/src/apis/definitions/auth.ts)
+[GoogleAuthApi](https://github.com/backstage/backstage/blob/master/packages/core-api/src/apis/definitions/auth.ts)
 for that use-case. Backstage also includes a set of implementations of these
 APIs that integrate with the
-[auth-backend](https://github.com/spotify/backstage/tree/master/plugins/auth-backend)
+[auth-backend](https://github.com/backstage/backstage/tree/master/plugins/auth-backend)
 plugin to provide a popup-based OAuth flow.
 
 ## Background
@@ -58,9 +58,9 @@ easier to make authenticated requests inside a plugin.
 ## OAuth Flow
 
 The following describes the OAuth flow implemented by the
-[auth-backend](https://github.com/spotify/backstage/tree/master/plugins/auth-backend)
+[auth-backend](https://github.com/backstage/backstage/tree/master/plugins/auth-backend)
 and
-[DefaultAuthConnector](https://github.com/spotify/backstage/blob/master/packages/core-api/src/lib/AuthConnector/DefaultAuthConnector.ts)
+[DefaultAuthConnector](https://github.com/backstage/backstage/blob/master/packages/core-api/src/lib/AuthConnector/DefaultAuthConnector.ts)
 in `@backstage/core-api`.
 
 Component and APIs can request Access or ID Tokens from any available Auth