Closed cdong03 closed 2 months ago
@amyjko May I ask why this issue was closed? I was working on it, and there still seem to be errors.
I assigned myself to the issue 2 days ago and resolved it this morning. The person assigned to the issue is the one responsible for fixing it; if you were working on it, you should have assigned yourself to the issue so I and others would know. There's no other way I could know you're working on it; this is how we coordinate our work.
If you have new typos that you're resolving, you can open a new issue and assign yourself to it so that everyone knows you're working on it. If you're working through the tutorial to find typos, consider opening a draft pull request to track that work, making commits every time you fix something, so everyone knows you're working on it.
Thanks, I understand; I'll make a new issue.
Sounds good! Sorry about the process confusion; think of GitHub as the ground truth: everything happening needs to be visible here.
Oh, and a draft Pull Request is definitely a better format for a bunch of typo fixes. You're welcome to submit one of those instead, if it's going to be a bunch of straightforward commits for fixing typos.
Expected behavior
We expect the tutorial's instructions and storyline to lack typos and grammatical errors.
Actual behavior
When reading through the tutorial, there are typos and grammatical errors like comma splicing.
Screenshots
Environment
Laptop