docs: update doc plugin example links

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>

docs/faq/technical.md

@@ -195,10 +195,9 @@ ambition will be to keep Backstage modular.
 ### How can I get involved?
 
 Jump right in! Come help us fix some of the
-[early bugs and good first issues](https://github.com/backstage/backstage/contribute)
-or reach [a new milestone](https://github.com/backstage/backstage/milestones).
-Or write an open source plugin for Backstage, like this
-[Lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse).
+[early bugs and good first issues](https://github.com/backstage/backstage/contribute).
+Or write an open source plugin for Backstage in our
+[community plugins repository](https://github.com/backstage/community-plugins).
 See all the ways you can
 [contribute here](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md).
 We'd love to have you as part of the community.

docs/features/software-catalog/extending-the-model.md

@@ -120,7 +120,7 @@ the infrastructure tooling through plugins. Different plugins are used for
 managing different types of components.
 
 For example, the
-[Lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse)
+[Lighthouse plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/lighthouse/plugins/lighthouse)
 only makes sense for Websites. The more specific you can be in how you model
 your software, the easier it is to provide plugins that are contextual.
 

docs/overview/architecture-overview.md

@@ -61,9 +61,9 @@ The CircleCI plugin is available on `/circleci`.
 
 Each plugin is a client side application which mounts itself on the UI. Plugins
 are written in TypeScript or JavaScript. They each live in their own directory
-in `backstage/plugins`. For example, the source code for the lighthouse plugin
+in the `plugins` folder. For example, the source code for the catalog plugin
 is available at
-[backstage/plugins/lighthouse](https://github.com/backstage/backstage/tree/master/plugins/lighthouse).
+[plugins/catalog](https://github.com/backstage/backstage/tree/master/plugins/catalog).
 
 ### Installing plugins
 

docs/plugins/call-existing-api.md

@@ -137,9 +137,8 @@ router.use('/summary', async (req, res) => {
 ```
 
 For a more detailed example, see
-[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.
+[the user-settings plugin backend](https://github.com/backstage/backstage/tree/master/plugins/user-settings-backend)
+that stores some state in a database and surfaces an API for the frontend plugin to use.
 
 Internally at Spotify, this has been a fairly popular choice for different
 reasons. Commonly, the backend has been used as a caching and data massaging