Skip to content

docs: fix typo in security guide #50324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bampakoa wants to merge 1 commit into from
Closed

docs: fix typo in security guide #50324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions aio/content/guide/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,7 +198,7 @@ If an attacker can predict future nonces, they can circumvent the protections of

</div>

If you cannot generate nones in your project, you can allow inline styles by adding `'unsafe-inline'` to the `style-src` section of the CSP header.
If you cannot generate nonces in your project, you can allow inline styles by adding `'unsafe-inline'` to the `style-src` section of the CSP header.

| Sections | Details |
|:--- |:--- |
Expand Down Expand Up @@ -380,4 +380,4 @@ Angular-specific APIs that should be audited in a security review, such as the [

<!-- end links -->

@reviewed 2022-02-28
@reviewed 2023-05-16