paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 38 Packages Projects Releases Wiki Activity

fix(docs): spelling mistake fixed

Browse Source 
Co-authored-by: Fredrik Adelöw <freben@gmail.com>
Signed-off-by: Valentin Grégoire <32612304+valentingregoire@users.noreply.github.com>
This commit is contained in:
Valentin Grégoire
2025-06-06 09:08:32 +02:00
committed by GitHub
parent f09921955b
commit c4a18f4334
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/permissions/frontend-integration.md
+1 -1
View File
@@ -5,7 +5,7 @@ description: How to place your Backstage frontend components behind authorizatio
---
:::info
Starting with a [fresh Backstage installation](https://backstage.io/docs/getting-started/), the code example below is already implemented, so there are no code actual code changes required.
Starting with a [fresh Backstage installation](https://backstage.io/docs/getting-started/), the code example below is already implemented, so there are no actual code changes required.
:::
Now that we understand how to [author a permission policy](./writing-a-policy.md), let's consider cases where we'll need to supplement our policy with authorization checks on the frontend.