consistent writing and typo fixes of English resource strings

[tolot27]

This PR addresses many points of #1554

[tolot27]

Will check the wear strings this evening. Afterwards, I'll remove the draft flag.

[tolot27]

Is the base language en-gb or en-us? I suspect en-gb.

[tolot27]

I've double checked the strings by visual inspection and a word processor. Maybe, it is necessary to adjust the translations as well, especially for 4dfdcfd.

[tolot27]

@jamorham Feel free to cherry-pick any of the commits if you don't want to merge all at once.

[jamorham]

Hi thanks. Can you confirm that you've checked the execution of the positional argument changes to the format strings within the app? They look okay to me but as its effectively a code change I would like confirmation of testing. I believe positional formatting is supported down to the minimum sdk level but I haven't checked that to confirm.

[tolot27]

Renaming of "barcode" is suggested in #1151, too.

[tolot27]

Hi thanks. Can you confirm that you've checked the execution of the positional argument changes to the format strings within the app? They look okay to me but as its effectively a code change I would like confirmation of testing. I believe positional formatting is supported down to the minimum SDK level but I haven't checked that to confirm.

I've tested that the positional arguments work. Argument indices (=positional arguments) are supported since very early Java versions long before Android was developed.

[Navid200]

I don't see invite_follower in the strings file. So, how is the first change (android:text="@string/invite_follower") going to work?

[tolot27]

I don't see invite_follower in the strings file. So, how is the first change (android:text="@string/invite_follower") going to work?

Commit 1c1b972 contains it.