docs: Fix WireGuard spelling

[gandro]

According to WireGuard's Trademark Usage Policy [1], WireGuard must be
written with a capital W and a capital G.

[1] https://www.wireguard.com/trademark-policy/

[qmonnet]

PR looks good, but I wonder if we have a way to prevent adding Wireguard again in the future. The spell file currently contains Wireguard, I'm curious to see if it complains on your changes. But even if it does, we are likely to change it anyway to have wireguard (all lowercase) in #16238, and this will result of Sphinx spellchecks being case insensitive :/.

[qmonnet]

Experimenting with Sphinx's spell-check: The current Wireguard shouldn't trigger any complaint on your changes, because it seems to be case-insensitive when there is no upper case or when only the first letter is upper case.

Would you consider to change the spelling file to WireGuard for now, even if we change back in a future PR? Would seem cleaner to me. Ok you just did while I was writing, thanks!

[gandro]

PR looks good, but I wonder if we have a way to prevent adding Wireguard again in the future. The spell file currently contains Wireguard, I'm curious to see if it complains on your changes. But even if it does, we are likely to change it anyway to have wireguard (all lowercase) in #16238, and this will result of Sphinx spellchecks being case insensitive :/.

Good question, I don't have a good answer either. I at least updated the spelling in the dictionary. It's also complicated by the fact that we still have some uses of "Wireguard" in the cilium status command output, so a simple grep lint would still need to deal with exceptions.

[qmonnet]

we still have some uses of "Wireguard" in the cilium status command output

Should these be updated, too?

[qmonnet]

(Looking at the docs we can maybe implement some custom filter to allow either wireguard (for Helm values) or WireGuard, but reject Wireguard.)

[gandro]

we still have some uses of "Wireguard" in the cilium status command output

Should these be updated, too?

Probably, yes. But I want to do that in a separate PR, as it is a code change and I want to be sure to test that separately.

[gandro]

(Looking at the docs we can maybe implement some custom filter to allow either wireguard (for Helm values) or WireGuard, but reject Wireguard.)

So interestingly enough, now that I fixed the spelling in the dictionary, it seems to actually consider upper/lowercase (because I missed one):

If the words are not misspelled, run:
Documentation/update-spelling_wordlist.sh Wireguard 

[qmonnet]

So interestingly enough, now that I fixed the spelling in the dictionary, it seems to actually consider upper/lowercase

My understanding (from playing with it a little) is:

• wireguard -> case insensitive
• Wireguard -> “probably wireguard with a capital because it was at the beginning of a sentence” -> case insensitive
• WireGuard -> capital elsewhere than first letter only -> case sensitive