[Doc] Removed Mentions of the New Backend System

Signed-off-by: Andre Wanlin <awanlin@spotify.com>

docs/features/software-templates/authorizing-scaffolder-template-details.md

@@ -6,7 +6,13 @@ description: How to authorize parts of a template and authorize scaffolder task
 
 The scaffolder plugin integrates with the Backstage [permission framework](../../permissions/overview.md), which allows you to control access to certain parameters and steps in your templates based on the user executing the template. It also allows you to control access to scaffolder tasks.
 
-### Authorizing parameters and steps
+:::tip
+
+To better understand the following examples make sure to review the [Writing a permission policy](./../permissions/writing-a-policy.md)) documentation before moving forward.
+
+:::
+
+## Authorizing parameters and steps
 
 To mark specific parameters or steps as requiring permission, add the `backstage:permissions` property to the parameter or step with one or more tags. For example:
 
@@ -288,62 +294,3 @@ All other users are granted permissions to perform/access the following actions/
 - Read scaffolder tasks and their associated events/logs for tasks created by the user.
 
 Although the rules exported by the scaffolder are simple, combining them can help you achieve more complex use cases.
-
-### Authorizing in the New Backend System
-
-Instead of the changes in `permission.ts` noted in the above example you will make them in your `index.ts`. You will need to create a module where your permission policy will get added. Here is a very simplified example of how to do that:
-
-```ts title="packages/backend/src/index.ts"
-import { createBackendModule } from '@backstage/backend-plugin-api';
-import {
-  PolicyDecision,
-  AuthorizeResult,
-} from '@backstage/plugin-permission-common';
-import {
-  PermissionPolicy,
-  PolicyQuery,
-  PolicyQueryUser,
-} from '@backstage/plugin-permission-node';
-import { policyExtensionPoint } from '@backstage/plugin-permission-node/alpha';
-
-class ExamplePermissionPolicy implements PermissionPolicy {
-  async handle(
-    request: PolicyQuery,
-    user?: PolicyQueryUser,
-  ): Promise<PolicyDecision> {
-    // Various scaffolder permission checks ...
-
-    return {
-      result: AuthorizeResult.ALLOW,
-    };
-  }
-}
-
-const customPermissionBackendModule = createBackendModule({
-  pluginId: 'permission',
-  moduleId: 'allow-all-policy',
-  register(reg) {
-    reg.registerInit({
-      deps: { policy: policyExtensionPoint },
-      async init({ policy }) {
-        policy.setPolicy(new ExamplePermissionPolicy());
-      },
-    });
-  },
-});
-
-const backend = createBackend();
-
-// Other plugins...
-
-/* highlight-add-start */
-backend.add(import('@backstage/plugin-permission-backend'));
-backend.add(customPermissionBackendModule);
-/* highlight-add-end */
-```
-
-:::note Note
-
-The `ExamplePermissionPolicy` here could be the one from the [Authorizing parameters and steps](#authorizing-parameters-and-steps) example or from the [Authorizing actions](#authorizing-actions) example. It would work the same way for both of them.
-
-:::

docs/features/software-templates/builtin-actions.md

@@ -32,7 +32,7 @@ Here's how to add an action module, first you need to run this command:
 yarn --cwd packages/backend add @backstage/plugin-scaffolder-backend-module-github
 ```
 
-Then you need to add it to your backend, this is a simplified new backend system for example purposes:
+Then you need to add it to your backend, this is a simplified backend system for example purposes:
 
 ```ts title="/packages/backend/src/index.ts"
 import { createBackend } from '@backstage/backend-defaults';