-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
Typo: "Most likely it is already install." #6059
Closed
1 task done
matthewCmatt opened this issue
Aug 7, 2024
· 2 comments
· Fixed by #6064 · May be fixed by WontonSam/opentelemetry.io#34, WontonSam/opentelemetry.io#38 or WontonSam/opentelemetry.io#40
Closed
1 task done
Typo: "Most likely it is already install." #6059
matthewCmatt opened this issue
Aug 7, 2024
· 2 comments
· Fixed by #6064 · May be fixed by WontonSam/opentelemetry.io#34, WontonSam/opentelemetry.io#38 or WontonSam/opentelemetry.io#40
Labels
Comments
Jason3S
added a commit
that referenced
this issue
Aug 8, 2024
Jason3S
changed the title
[Bug]: Typo: "Most likely it is already install."
Typo: "Most likely it is already install."
Aug 8, 2024
Thank you. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Kind of Issue
Crash / Error
Tool or Library
cspell
Version
No response
Supporting Library
No response
OS
All of them
OS Version
No response
Description
A typo exists on the Installation doc (http://cspell.org/docs/installation/)
Under instructions for Node, the line "CSpell requires Node JS to run. Most likely it is already install." has a typo.
It should say something like "NodeJS is likely already installed". This sentence might need to be excluded completely.
Steps to Reproduce
Expected Behavior
No response
Additional Information
No response
cspell.json
No response
cspell.config.yaml
No response
Example Repository
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: