Skip to content

improved clarity in workshop documentation#1196

Closed
rthivisha wants to merge 2 commits intofreeCodeCamp:mainfrom
rthivisha:improve-workshop-docs
Closed

improved clarity in workshop documentation#1196
rthivisha wants to merge 2 commits intofreeCodeCamp:mainfrom
rthivisha:improve-workshop-docs

Conversation

@rthivisha
Copy link

  • I have read freeCodeCamp's contribution guidelines.
  • My pull request has a descriptive title.

This PR improves grammar, formatting, and clarity in the workshop documentation.
No structural or functional changes were made.

@rthivisha rthivisha requested a review from a team as a code owner February 19, 2026 11:53
## Styling pointers

Workshops should alternate steps in which new concepts are introduced small piece by piece, and steps where there is freedom of implementation.
Workshops should introduce new concepts gradually. Break complex ideas into small, easy-to-understand steps.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this changes the meaning of the sentence completely, have you moved somewhere else the part about "steps where there is freedom of implementation"?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for pointing that out. I did not move that part elsewhere — my intention was to improve clarity, but I see that it changes the meaning.I can revise the sentence to preserve the original idea about freedom of implementation.

#### How to Run the Script

1. Change to the directory of the project.
1. Change the directory to the currrent project by copying the path and running in terminal.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Change the directory to the currrent project by copying the path and running in terminal.
1. Change to the directory of the currrent project.

## Proposing a Pull Request (PR)

After you've committed your changes, check here for [how to open a Pull Request](/how-to-open-a-pull-request/).
After you've committed your changes, check here for [how to open a Pull Request](/how-to-open-a-pull-request/) and thats's a quick step .
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After you've committed your changes, check here for [how to open a Pull Request](/how-to-open-a-pull-request/) and thats's a quick step .
After you've committed your changes, check here for [how to open a Pull Request](/how-to-open-a-pull-request/).

what does "and that's a quick step" mean?

@majestic-owl448
Copy link
Contributor

majestic-owl448 commented Feb 19, 2026

closing this PR. If there is something unclear please open an issue about this.

It would be great if you had some experience with contributing with workshops first.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants