Fix #533

[katrinabrock]

If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.

Closes #533

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

Uses wording suggested by @btovar

If any relevant discussions have taken place elsewhere, please provide links to these.

Details

For more guidance on how to contribute changes to a Carpentries project, please review the Contributing Guide and Code of Conduct.

Please keep in mind that lesson Maintainers are volunteers and it may be some time before they can respond to your contribution. Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum. If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact The Carpentries Team at team@carpentries.org.

[github-actions]

🆗 Pre-flight checks passed 😃

This pull request has been checked and contains no modified workflow files, spoofing, or invalid commits.

It should be safe to Approve and Run the workflows that need maintainer approval.

[katrinabrock]

@maneesha @quist00 Looks like you all have merged PRs on this repo most recently. Any interest in merging this tiny one to fix a small long-standing issue?

[maneesha]

I have admin access across all Carpentries resources but changes to lesson content are reviewed/approved/merged by lesson Maintainers. Tagging @datacarpentry/python-ecology-lesson-maintainers

[katrinabrock]

@datacarpentry/python-ecology-lesson-maintainers any interest in merging this small change?

[josenino95]

I'm assigned as a maintainer as currently we are working on a reorganization of the lesson, but that will take some more months to go live. I'm good with merging this small change, and if there's no additional comments this week I can merge it. Thank you @katrinabrock !