49 change format strings into f strings

[Scottan]

Closes #49

Advice on whether I've put the box on f-strings in the best place, and if the content is ok

[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/UoMResearchIT/programming_with_python/compare/md-outputs..md-outputs-PR-74

The following changes were observed in the rendered markdown documents:

 01-introduction.md          | 57 +++++++++++++++++++++++++++++++++++++++++++++
 02-dictionaries.md          | 35 +++++++++++++---------------
 03-numpy_essential.md       | 39 +++++++++++++++----------------
 05-defensive_programming.md | 32 ++++++++++++-------------
 06-units_and_quantities.md  | 32 ++++++++++++-------------
 md5sum.txt                  | 10 ++++----
 6 files changed, 128 insertions(+), 77 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-04-21 11:10:15 +0000

[andrewgait]

The content looks fine to me aside from a few spellings.

I think the merge conflict is because I also added a callout box in the introduction, so this probably needs merging and sorting out.

[Scottan]

@andrewgait Thanks for catching my terrible spelling. I've fixed the merge conflict, please let me know if you're happy with the changes

[andrewgait]

Looks good to me - approved.