-
Notifications
You must be signed in to change notification settings - Fork 92
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
Reviewing naming of Variable Sets #2360
Conversation
There are quite a few images in here with a missing opening
Should be:
Sending a commit to fix this and resolve some spelling issues. |
I can sort out this merge for you tomorrow. |
Ah it was the image tags! I was so confused by the spell check errors. Thank you. I'm still reviewing some of these changes later today, but this is in a much nicer position now, thank you. |
…ew this more carefully later on the backend
Thanks @steve-fenton-octopus. This one is now ready for review please 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I'll add a note to the "next edition feedback" of Exploring Octopus Deploy to also remove "library" and just use "variable set".
In preparation for Vertical Navigation's release next week, we've been reviewing docs and discovered various combinations of the wording around "Variable Sets".
This PR reviews the various wording and standardises where appropriate, based on both the current UI and the new UI coming soon. We no longer refer to "Variable Sets" as "Library Variable Sets" or "Library Sets". They are just Variable Sets.