Fix misc. typos

[luzpaz]

codespell -q 3 -S *.ts,./libs,./sample-projects -L searchin

[gedakc]

Thank you @luzpaz for your interest in Manuskript and your efforts to make it better.

This PR identifies a number of spelling mistakes to fix which is a good thing.

However some of the spelling changes involve automatically generated content, and one spelling change affects executable code. As such I have some suggestions for this Pull Request.

1. Because the CHANGELOG.md file is automatically generated from the github project (see bottom of CHANGELOG.md), I do not know the implications of making manual changes. Will these manual changes be overwritten on the next automatic generation? Is it better to try to fix the spelling mistakes in the title of the original Issue or Pull Request?

   Would you please test automatic generation, or else remove all the changes to CHANGELOG.md in this PR.

2. This PR identifies itself as fixing spelling mistakes, but also changes executable code (see misspelled "stlye" in manuskript/ui/highlighters/markdownHighlighter.py#L679.

   Please place this executable code change in a separate PR. Please also test to see what this change fixes and include this in the PR description / commit message.

[luzpaz]

I will follow-up when I have another moment. Thanks.

[worstje]

@luzpaz What is the status on this?

[luzpaz]

forgot about this. Will look in to it

[luzpaz]

@worstje
Both 4ddab3d & fe5777b are the reverted code requested by @gedakc
b714864 are a few more typos I just found, that need review

[worstje]

Can you rebase your entire set of changes against the current develop branch?

I am not entirely sure happened here, but I think you left your Feb 10 changes in (8830ea1), pulled in new more recent changes from develop, and then wrote these new patches against your old patch, leading to the commits where you 'revert'.

Ideally your PR only has the 'Misc. typos' and 'Add a few more typos' fixes. (And even those can be squashed together into a single commit.

Edit: Nevermind. Github confused me with the old date. It seems like everything is properly on top of the current develop. All you need is a squash.

[luzpaz]

squashed and ready to go

[worstje]

I'd amend the commit message a bit still because some of that description doesn't make sense anymore now that you've tidied it up. Other than that, it looks good! 👍

[luzpaz]

Yea, makes sense. Amended.

[gedakc]

@luzpaz are you able to make the suggested "save" -> "saved" changes in the next day or so?

If not then I will plan to merge this as-is and make the change afterwards.

[luzpaz]

@gedakc i don't follow? was there a suggestion that I missed ?

[gedakc]

This looks like my bad. I must have been reviewing an older commit in my comments above.

When pulled your changes into my local repo, I can clearly see that you did change "save" to "saved" in both the files:

• manuskript/ui/settings_ui.py
• manuskript/ui/settings_ui.ui

I will plan to merge this PR for inclusion in the next release of Manuskript.

Thank you for your help.

[luzpaz]

@gedakc you're absolutely right, I did miss a fix. Apologies. Added in #648

[gedakc]

@luzpaz no worries. I just remembered that yesterday I had pulled down your other PR with the typo fixes and then had made the "save" -> "saved" change locally. But with all the other work I did yesterday I forgot.

I'm glad you double-checked. I will merge this with the develop branch after the current Travis CI processes complete.