backend -> backend-legacy, backend-next -> backend

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

docs/auth/vmware-cloud/provider.md

@@ -43,7 +43,7 @@ Cloud Console and within a Backstage app required to enable this capability.
 Apps using the [new backend system](../../backend-system/index.md),
 can enable the VMware Cloud provider with a small modification like:
 
-```ts title="packages/backend-next/src/index.ts"
+```ts title="packages/backend/src/index.ts"
 import { createBackend } from '@backstage/backend-defaults';
 
 const backend = createBackend();

docs/backend-system/index.md

@@ -10,4 +10,4 @@ description: The Backend System
 
 The new backend system is released and ready for production use, and many plugins and modules have already been migrated. We recommend all plugins and deployments to migrate to the new system.
 
-You can find an example backend setup in [the `backend-next` package](https://github.com/backstage/backstage/tree/master/packages/backend-next).
+You can find an example backend setup in [the `backend` package](https://github.com/backstage/backstage/tree/master/packages/backend).

docs/conf/reading.md

@@ -145,7 +145,7 @@ from `@backstage/core-plugin-api`.
 
 In the old backend system plugins, the configuration is passed in via options from the main
 backend package. See for example
-[packages/backend/src/plugins/auth.ts](https://github.com/backstage/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/backend/src/plugins/auth.ts#L23).
+[packages/backend-legacy/src/plugins/auth.ts](https://github.com/backstage/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/backend/src/plugins/auth.ts#L23).
 
 ### New Backend System
 

docs/features/kubernetes/proxy.md

@@ -64,8 +64,6 @@ This feature assumes your backstage instance has enabled the [permissions framew
 
 A sample policy like:
 
-[packages/backend/src/plugins/permissions.ts](https://github.com/backstage/backstage/blob/master/packages/backend/src/plugins/permission.ts)
-
 ```typescript
 import { BackstageIdentityResponse } from '@backstage/plugin-auth-node';
 import {

docs/features/search/how-to-guides.md

@@ -393,7 +393,7 @@ There are other more specific search results layout components that also accept
 
 Recently, the Backstage maintainers [announced the new Backend System](https://backstage.io/blog/2023/02/15/backend-system-alpha). The search plugins are now migrated to support the new backend system. In this guide you will learn how to update your backend set up.
 
-In "packages/backend-next/index.ts", install the search plugin [1], the search engine [2], and the search collators/decorators modules [3]:
+In "packages/backend/index.ts", install the search plugin [1], the search engine [2], and the search collators/decorators modules [3]:
 
 ```ts
 import { searchPlugin } from '@backstage/plugin-search-backend/alpha';

docs/features/software-catalog/external-integrations.md

@@ -55,7 +55,7 @@ Some defining traits of entity providers:
 
 The recommended way of instantiating the catalog backend classes is to use the
 `CatalogBuilder`, as illustrated in the
-[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend/src/plugins/catalog.ts).
+[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend-legacy/src/plugins/catalog.ts).
 We will create a new
 [`EntityProvider`](https://github.com/backstage/backstage/blob/master/plugins/catalog-node/src/api/provider.ts)
 subclass that can be added to this catalog builder.
@@ -531,7 +531,7 @@ does so!
 
 The recommended way of instantiating the catalog backend classes is to use the
 `CatalogBuilder`, as illustrated in the
-[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend/src/plugins/catalog.ts).
+[example backend here](https://github.com/backstage/backstage/blob/master/packages/backend-legacy/src/plugins/catalog.ts).
 We will create a new
 [`CatalogProcessor`](https://github.com/backstage/backstage/blob/master/plugins/catalog-node/src/api/processor.ts)
 subclass that can be added to this catalog builder.

docs/plugins/new-backend-system.md

@@ -8,7 +8,7 @@ description: Details of the new backend system
 
 The new backend system is released and ready for production use, and many plugins and modules have already been migrated. We recommend all plugins and deployments to migrate to the new system.
 
-You can find an example backend setup in [the backend-next package](https://github.com/backstage/backstage/tree/master/packages/backend-next).
+You can find an example backend setup in [the backend package](https://github.com/backstage/backstage/tree/master/packages/backend).
 
 ## Overview