rewrite other references to spotify/backstage and sorrounding things

packages/cli/src/lib/codeowners/codeowners.ts

@@ -20,7 +20,7 @@ import path from 'path';
 const TEAM_ID_RE = /^@[-\w]+\/[-\w]+$/;
 const USER_ID_RE = /^@[-\w]+$/;
 const EMAIL_RE = /^[^@]+@[-.\w]+\.[-\w]+$/i;
-const DEFAULT_OWNER = '@spotify/backstage-core';
+const DEFAULT_OWNER = '@backstage/maintainers';
 
 type CodeownersEntry = {
   ownedPath: string;

packages/create-app/templates/default-app/catalog-info.yaml.hbs

@@ -5,7 +5,7 @@ metadata:
   description: An example of a Backstage application.
   # Example for optional annotations
   # annotations:
-    # github.com/project-slug: spotify/backstage
+    # github.com/project-slug: backstage/backstage
     # backstage.io/techdocs-ref: github:https://github.com/backstage/backstage.git
 spec:
   type: website

packages/techdocs-container/README.md

@@ -24,7 +24,7 @@ Then open up `http://localhost:8000` on your local machine.
 
 This container is published on DockerHub - https://hub.docker.com/r/spotify/techdocs
 
-The publishing is configured by [Automated Builds](https://hub.docker.com/repository/docker/spotify/techdocs/builds/edit) feature on Docker Hub which is triggered from GitHub (on new commits and releases). @spotify/techdocs-core team has access to the settings.
+The publishing is configured by [Automated Builds](https://hub.docker.com/repository/docker/spotify/techdocs/builds/edit) feature on Docker Hub which is triggered from GitHub (on new commits and releases). @backstage/techdocs-core team has access to the settings.
 
 The `latest` tag on Docker Hub points to the recent commits in the `master` branch. The [version tags](https://hub.docker.com/r/spotify/techdocs/tags) (e.g. v0.1.1-alpha.24) point to the GitHub tags created from [releases](https://github.com/backstage/backstage/releases) of this GitHub repository.