docs: fix unclosed table row in security section - #535
Open
Mohit-001-hash wants to merge 1 commit into
Open
Conversation
|
@Mohit-001-hash is attempting to deploy a commit to the 007's projects Team on Vercel. A member of the Team first needs to authorize it. |
Thanks for creating a PR for your Issue!
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
The final row of the features table in the "Security & Access Control" section was missing a closing pipe (
|). This is a markdown syntax error that can break table rendering across different markdown viewers, making the documentation look broken or hard to read.What changes are included in this PR?
|) to the "Password Hashing" row in the### 🔐 Security & Access Controltable to complete the markdown syntax.Are these changes tested?
Yes, the markdown changes were verified locally using a markdown previewer to ensure the table now renders correctly. No code tests are required since this is a documentation-only change.
Are there any user-facing changes?
No functional user-facing changes. This is strictly a documentation formatting update.