Use terminology consistently for all error messages within a single
product area. If you call something a "datastore" in one error message,
then call the same thing a "datastore" in all the other error messages.
Not recommended
Can't connect to cluster at 127.0.0.1:56. Check whether minikube is running.
Recommended
Can't connect to minikube at 127.0.0.1:56. Check whether minikube is running.
Error messages must appear consistently with similar formats and
non-contradictory content; that is, the same problem must generate the same
error message. For example, if different parts of an app each detect problems
with internet connection, both parts should emit the same error message.
[null,null,["Last updated 2024-08-06 UTC."],[[["Maintain consistent terminology throughout all error messages within a specific product area, avoiding the use of synonyms for the same element."],["Ensure all error messages related to a specific problem are consistent in format and content, regardless of where the problem is detected within the application."]]],["Error messages should maintain consistent terminology within a product area; for instance, a \"datastore\" should always be referred to as such. Identical problems should trigger the same error message across an application. Avoid using synonyms for the same element in messages, as this can confuse users. Consistency in error message content and format is crucial for clear user understanding.\n"]]
