Various typos needed fixing

[waydabber]

Hi waydabber, it's @niklasbogensperger from the German translation thread 👋

Like I mentioned in the comment thread on GitHub, here is my list of minor corrections in the original strings:

If source and target control ranges differ, synchronized values are remaped (rebased) accordingly.
-> "remapped"

MacOS can mute digital streams natively [...]
-> "macOS" (lowercase even at start of sentence)

Newly connected displays are normally treated as possible affected displays only. [...]
-> "possibly" (?)

Phyiscal dimensions are used by the app for UI scale matching [...]
-> "Physical"

[...] This lets change GUI size (display scaling) freely via the resolution slider.
-> "This lets you"

[...] Helps if a display is strandled disconnected in case of an app crash of forced quit.
-> "stranded" / "stranded as"
-> "crash or forced"

Select one or more filters to specify which displays are allowed be sync sources for this configuration!
-> "allowed to be"

Show currently off-line displays in Settings
[...] Allows some configuration changes even when a display is off-line.
-> "offline" (consistency)

The app menu will show this name instead of the system name in the app menu for the display. [...]
-> app menu twice?

The app was launched using the Rosetta. [...]
-> "using Rosetta"

[...] Physically reconnect  display to revert back to the original in case of serious trouble.
-> double space after "reconnect"

[...] Alternatively you can disable auto-connect (it can be enable any time under association settings).
-> "be enabled"
There are no at least two display group members present.
There is no at least one display group member present.
-> "There is not" / "There are not"

These three identifiers (serial number, vendor and model ID) serves as the basis [...]
-> "serve"

Let the application control ... [...] (x2)
-> "app" (consistency)

A pop-up notification will appear when the app detects [...]
-> "popup" (consistency)

[...] Use only if you want to finetune the dimming curve below the configured XDR brightness scale minimum
-> "fine-tune" (consistency and recommended spelling)

%@%%
%@Hz
%.3fHz
%@mm
%1$@mm x %2$@mm
%1$lld x %2$lld %3$@ @ %4$lldHz
-> missing spaces? (SI) units should always be preceded by a space (except for º (degree), ' (arcmin), " (arcsec))

Screen Rotation%@
-> missing space?

Apple Silicon Macs tend freeze the display instead of letting [...]
-> "tend to"

By default the keys controls change one OSD chiclet worth of value [...]
-> "the key controls" / "the keys change" / "the controls change" ? (sentence structure is confusing)

[niklasbogensperger]

[...] Helps if a display is strandled disconnected in case of an app crash of forced quit.

In the newest version of the strings the extra "l" in stranded is still there, otherwise it's all fixed (I'm assuming the unit spacing is/has to be handled differently?)

[waydabber]

Oh sorry, will fix that, thank you.

The `Screen Rotation%@' is good as it is as the space is added by the app before the degree which must always be at the end of the string.

The units are ambiguous. I could make a change that but would raise various compatibility issues as some of the values are actually persisted as a string for various reasons and if I make a change it might mess things up. I looked up on the net how prevalent '60Hz' is versus '60 Hz' and to me it seems like in the context of computer monitors omitting the space is actually quite common and accepted (at least it does not hurt my eyes). I asked ChatGPT about it - it says it is better to use "60Hz" as this is how people are used to it, but if I write a scientific paper or in a formal setting, it might indeed be better to add a space to align with SI standards.