Minor improvements in documentation #2080
Labels
kind/documentation
Categorizes issue or PR as related to documentation.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
What should the feature do?
As someone relatively new to Kubernetes and Operator, I was attempting to configure a cluster using the instructions provided in the official Operator documentation. During this process, I encountered some minor issues and inconsistencies.
https://operator.docs.scylladb.com/stable/generic.html
https://operator.docs.scylladb.com/stable/monitoring.html
Most of these points are trivial, and if there are plans to rewrite the documentation, they can probably be discarded. However, I believe it’s important to acknowledge what might challenge newcomers.
What is the use case behind this feature?
Improve user experience.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: