Various minor fixes

[JostMigenda]

• replace “method” with the more generic “function”
  • There are some instances where “method” would have been correct. I have changed those as well, to avoid confusing learners when we switch back and forth between those terms, but have kept that in a separate commit in case anyone disagrees.
• Python uses Grass.eaten instead of Grass::eaten
• … and a couple of other minor fixes, rewordings, etc.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/pando-python/compare/md-outputs..md-outputs-PR-35

The following changes were observed in the rendered markdown documents:

 files/snakeviz-worked-example/example.py |  2 +-
 md5sum.txt                               | 12 ++++----
 optimisation-introduction.md             |  2 +-
 optimisation-numpy.md                    | 17 +++++-----
 profiling-conclusion.md                  |  6 ++--
 profiling-functions.md                   | 53 +++++++++++++++++---------------
 profiling-introduction.md                |  2 +-
 profiling-lines.md                       | 38 +++++++++++------------
 8 files changed, 67 insertions(+), 65 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2026-02-23 19:32:35 +0000

[Robadob]

All looks good.

I think my preference for method (albeit I'm by no means consistent) stems from a teacher we had at a-levels, whining about function not being precisely correct in some circumstances. I don't recall their exact argument, but it's stuck with me.