Skip to content
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.

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

Remove jargon from april-2024-security-releases.md #7059

Closed
wants to merge 1 commit into from

Conversation

getsnoopy
Copy link

Description

Remove jargon from april-2024-security-releases.md

Validation

It's a change in the docs.

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run format to ensure the code follows the style guide.
  • I have run npm run test to check if all tests are passing.
  • I have run npx turbo build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@getsnoopy getsnoopy requested a review from a team as a code owner September 24, 2024 18:01
Copy link

vercel bot commented Sep 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Sep 24, 2024 6:03pm

@mikeesto
Copy link
Member

These phrases are used in all of the security release blog posts. It's not "nonsensical jargon". Please open an issue for these kinds of things in the first instance so discussion can be had.

@mikeesto mikeesto closed this Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants