Wording and clarity edits#458
Conversation
maxim-belkin
left a comment
There was a problem hiding this comment.
Thank you for your contribution, @zoews! I have a few comments/requests but this is an excellent PR! 👍
|
I'm helping the current lesson Maintainers process outstanding pull requests on this repository, in preparation for transition to the new lesson infrastructure. Thank you for contributing these changes, @zoews. I agree with @maxim-belkin's suggestions for how the changes could be improved further. If you would like to return and update this pull request to address his comments before the end of this month, I would be delighted to merge your enhancements. When the infrastructure transition takes place in May 2023, this pull request will become invalid and will have to be closed. |
|
I converted the changes @maxim-belkin proposed into code change suggestions, so @zoews or @tobyhodges can easily commit them if they accept them to merge this PR before May. Only for the last change (to move a sentence to below a code box) I had to create a new commit. I hope that's alright with everyone involved. |
|
Thanks you, @LilithElina! Glad this lesson is in good hands now. |
Phrasing changes to increase clarity in some parts of lesson, such as:
dataframe(without.head()orprint(df)Note that the clarity around methods would be compatible with the edits in #452 (which I think are great!)
Thank you for considering!