Change some messages and documentation to Welkin, as part of our rebranding

[cristiklein]

Warning

This is a public repository, ensure not to disclose:

• personal data beyond what is necessary for interacting with this pull request, nor
• business confidential information, such as customer names.

What kind of PR is this?

Required: Mark one of the following that is applicable:

• kind/feature
• kind/improvement
• kind/deprecation
• kind/documentation
• kind/clean-up
• kind/bug
• kind/other

Optional: Mark one or more of the following that are applicable:

Important

Breaking changes should be marked kind/admin-change or kind/dev-change depending on type
Critical security fixes should be marked with kind/security

• kind/admin-change
• kind/dev-change
• kind/security
• [kind/adr](set-me)

Release notes

Change some messages and documentation to Welkin, as part of our rebranding

What does this PR do / why do we need this PR?

The purpose of this PR is for me to test how simple it is to use the instructions in DEVELOPMENT.md to make a simple improvement to Welkin.

As a side-effect, I decided to actually contribute. 😄

• Fixes #

Information to reviewers

Checklist

• Proper commit message prefix on all commits
• Change checks:
  • [] The change is transparent
  • The change is disruptive
  • The change requires no migration steps
  • The change requires migration steps
  • The change updates CRDs
  • The change updates the config and the schema
• Documentation checks:
  • The public documentation required no updates
  • The public documentation required an update - [link to change](set-me)
• Metrics checks:
  • The metrics are still exposed and present in Grafana after the change
  • The metrics names didn't change (Grafana dashboards and Prometheus alerts required no updates)
  • The metrics names did change (Grafana dashboards and Prometheus alerts required an update)
• Logs checks:
  • The logs do not show any errors after the change
• PodSecurityPolicy checks:
  • Any changed Pod is covered by Kubernetes Pod Security Standards
  • Any changed Pod is covered by Gatekeeper Pod Security Policies
  • The change does not cause any Pods to be blocked by Pod Security Standards or Policies
• NetworkPolicy checks:
  • Any changed Pod is covered by Network Policies
  • The change does not cause any dropped packets in the NetworkPolicy Dashboard
• Audit checks:
  • The change does not cause any unnecessary Kubernetes audit events
  • The change requires changes to Kubernetes audit policy
• Falco checks:
  • The change does not cause any alerts to be generated by Falco
• Bug checks:
  • The bug fix is covered by regression tests

[llarsson]

Good changes so stuff works without redirects!

I see the addition of the Registered Trademark symbol. If we use that, we ought to ensure that we always write it as "Elastisys Welkin®", because our registered trademark is actually for those two words -- the Elastisys part is required as well.

Edit: is it possible to set something like that up using the "vale" or whatever the not-a-spellchecker-but-almost tool is called?

[cristiklein]

Good changes so stuff works without redirects!

Thanks!

I see the addition of the Registered Trademark symbol. If we use that, we ought to ensure that we always write it as "Elastisys Welkin®", because our registered trademark is actually for those two words -- the Elastisys part is required as well.

Nice catch. Fixed!

Edit: is it possible to set something like that up using the "vale" or whatever the not-a-spellchecker-but-almost tool is called?

In my experience, Vale is rather bad at "multi-word" spellchecking. I added a custom pre-commit hook.

[linus-astrom]

LGTM

[aarnq]

LGTM, nice to see more of the branding being updated 👍

[llarsson]

Nice, a lot of really good changes that are also visible to Application Developers! Love it!