Skip to content
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 in contributor_guidelines.md: 'Close' should be 'Clone'. #6632

Closed
1 of 17 tasks
ShivamGoelOSS opened this issue Dec 14, 2023 · 2 comments · Fixed by #6636
Closed
1 of 17 tasks

Typo in contributor_guidelines.md: 'Close' should be 'Clone'. #6632

ShivamGoelOSS opened this issue Dec 14, 2023 · 2 comments · Fixed by #6636

Comments

@ShivamGoelOSS
Copy link

ShivamGoelOSS commented Dec 14, 2023

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build Process
  • Unit Testing
  • Internalization
  • Friendly Errors
  • Other (specify if possible)

Details

I found a minor typo in the documentation "contributor_guidelines.md " under the section "contributor_docs" guiding users to download a copy of the p5.js repository. In the sentence, "Next, go to the command line in your local environment and close this git repository," it appears that the word "close" was used mistakenly instead of "clone."
This could potentially confuse users who are new to version control systems or git operations. I propose correcting this typo to ensure clarity and accuracy in the instructions provided to users seeking to download the p5.js source code.
I would be happy to submit a pull request to rectify this typo if deemed appropriate. Thank you for your attention to this matter.
https://github.com/processing/p5.js/blob/main/contributor_docs/contributor_guidelines.md

Screenshot

Issue

Copy link

welcome bot commented Dec 14, 2023

Welcome! 👋 Thanks for opening your first issue here! And to ensure the community is able to respond to your issue, please make sure to fill out the inputs in the issue forms. Thank you!

@yashu6march
Copy link

@academics-shivam Can you please assign this issue to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants