Fix some typos (found by codespell and typos)

[stweil]

Description

Related issue: #1001

Motivation and Context

I noticed a typo while using the software.

How has this been tested?

Manual review of the changes.

Screenshots (if appropriate)

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

Checklist

• I have read the contributor guide.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[stweil]

Note that I did not update the .mo files. The next regular update of these files will get the changes from the .po files automatically.

[coveralls]

coverage: 91.591%. remained the same
when pulling aa2a890 on stweil:typos
into c945d7d on rdmorganiser:main.

[MyPyDavid]

why was this merged on the main branch? Thought we have currently the dev-2.2.0 for that...

[Zack-83]

My mistake :(

[MyPyDavid]

we need to check if the changes to translations in the migration files require new migrations..
and now the dev-2.2.0 related branches need to be rebased to this new main ..

[jochenklar]

I think we should rebase dev-2.2.0 after we merge most of the feature branches.

[jochenklar]

Migrations and translations seem ok. The changed migrations are old, and the translations were changed in the same way in the code and the .po files.