rewrite repo location urls

docs/plugins/add-to-marketplace.md

@@ -8,7 +8,7 @@ description: Documentation on Adding Plugin to Marketplace
 
 To add a new plugin to the [plugin marketplace](https://backstage.io/plugins)
 create a file in
-[`microsite/data/plugins`](https://github.com/spotify/backstage/tree/master/microsite/data/plugins)
+[`microsite/data/plugins`](https://github.com/backstage/backstage/tree/master/microsite/data/plugins)
 with your plugin's information. Example:
 
 ```yaml

docs/plugins/call-existing-api.md

@@ -137,7 +137,7 @@ router.use('/summary', async (req, res) => {
 ```
 
 For a more detailed example, see
-[the lighthouse plugin](https://github.com/spotify/backstage/tree/master/plugins/lighthouse)
+[the lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse)
 that stores some state in a database and adds new capabilities to the underlying
 API.
 

docs/plugins/index.md

@@ -22,7 +22,7 @@ To create a plugin, follow the steps outlined [here](create-a-plugin.md).
 
 If you start developing a plugin that you aim to release as open source, we
 suggest that you create a
-[new Issue](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
+[new Issue](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
 This helps the community know what plugins are in development.
 
 You can also use this process if you have an idea for a good plugin but you hope

docs/plugins/publishing.md

@@ -7,7 +7,7 @@ description: Documentation on Publishing NPM packages
 ## NPM
 
 NPM packages are published through CI/CD in the
-[.github/workflows/master.yml](https://github.com/spotify/backstage/blob/master/.github/workflows/master.yml)
+[.github/workflows/master.yml](https://github.com/backstage/backstage/blob/master/.github/workflows/master.yml)
 workflow. Every commit that is merged to master will be checked for new versions
 of all public packages, and any new versions will automatically be published to
 NPM.

docs/plugins/structure-of-a-plugin.md

@@ -106,6 +106,6 @@ environment you will probably face challenges like CORS policies and/or
 backend-side authorization. To smooth this process out you can use proxy -
 either the one you already have (like Nginx, HAProxy, etc.) or the proxy-backend
 plugin that we provide for the Backstage backend.
-[Read more](https://github.com/spotify/backstage/blob/master/plugins/proxy-backend/README.md)
+[Read more](https://github.com/backstage/backstage/blob/master/plugins/proxy-backend/README.md)
 
 [Back to Getting Started](../README.md)