-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update guidance for "go to" #569
Comments
I don't have a strong preference here - the proposed change sounds good to me! |
Sounds like a good change. |
Some examples from David:
|
As expected (and described at least in part in IBM), there's going to be some I don't have a "ruleset" at this point, but these sorts of things are showing
I'll add more as I think of them. |
I guess it might be a question of something along the following lines: |
I noticed another section where "navigate to" is documented in the Style Guide. I'm noting it here so that we can update this mention as well when the "go to" guidance is adopted. Section 3.4.1.1 (under 3.4.1 https://stylepedia.net/style/6.2/#gui-elements-punctuation): "Navigating Through Multiple UI Options". |
https://stylepedia.net/style/6.2/#n
Includes an entry for "navigate to".
This has been discussed more than once in the past and is now in direct conflict with IBM:
navigate verb
Use only when a more direct verb, such as click, select, browse, or go to, is not applicable. Use only to provide
direction to a location (for example, “Navigate to the directory that contains the files that you want to edit”).
"Go to" is much simpler language and "covers more bases" (sometimes there's no actual navigation involved) and is also suitable when directing readers to other web sites, etc. For everyday purposes, click, select, and browse are more restrictive. So far I haven't encountered a case where "go to" doesn't work, but many cases where one or more of the other options do not work.
https://github.com/RedHatTraining/vale-styles/issues/365 is in place to work on this.
The text was updated successfully, but these errors were encountered: