fix: correct spelling and punctuation in Bash comments section - #776
Open
abdslam01 wants to merge 1 commit into
Open
fix: correct spelling and punctuation in Bash comments section#776abdslam01 wants to merge 1 commit into
abdslam01 wants to merge 1 commit into
Conversation
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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 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.
This PR improves the Bash comments section by:
Clarifying the distinction between single-line and multi-line comments.
Adding an explanation that single-line comments begin with # and extend to the end of the line.
Documenting that Bash does not support true multi-line comments, and explaining that the : '...' pattern works by passing a string to the no-op : builtin.
Fixing spelling and punctuation issues in the existing documentation.
These changes make the Bash cheat sheet more accurate and easier for beginners to understand.