Typo Update README.md #1687
Open
Typo Update README.md #1687
Conversation
This file contains 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
Fix typo in Git command in "Docker Dev Environments" section
mdqst
requested review from
Cashmaney,
toml01,
liorbond and
valdok
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
In the "Docker Dev Environments" section of the documentation, there was a typo in the Git command. The command incorrectly used
get fetch, which is not a valid Git command. The correct command isgit fetch.Changes made:
get fetchwithgit fetch.Importance of the fix
This typo could lead to confusion for users who are trying to follow the instructions, especially those who are not familiar with Git. Using the incorrect command (
get fetch) would result in an error, preventing users from updating their Git repository correctly. Correcting this ensures that the instructions are clear and functional, allowing users to proceed with setting up the Docker development environment without issues.