fix: Removed misleading info

[Wellitsabhi]

Description

Removed the misleading info as mentioned in issue #6853

Validation

Related Issues

Fixes: #6853

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.

[vercel]

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

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jul 7, 2024 4:29am

[TenzDelek]

@Wellitsabhi I think reverting the changes directly from the merged PR page will be a better choice for clarity and consistency rather than merging a new PR with a manual revert might create unnecessary changes.

[Wellitsabhi]

I agree but I don't have access to perform reverts, also @ovflowd might have put some thought before allowing to raise PR.

[bmuenzenmeyer]

I don't follow why this approach would be bad. Don't worry about it. Clean git history is overrated.

That said, we're not meeting anything until monorepo conversion stabilizes.

[TenzDelek]

I don't follow why this approach would be bad. Don't worry about it. Clean git history is overrated.

That said, we're not meeting anything until monorepo conversion stabilizes.

Can't agree more on this, :)

[bmuenzenmeyer]

This PR will need to be rebased or recreated now that #6850 merged.

[Wellitsabhi]

I really don't understand how it got closed, i shall be adding new PR again.