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
use present tense for porting guide entries #74021
Conversation
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.
snuck in a couple of suggestions to one of abadger's suggested edits to remove the via's, just for fun ;-) otherwise LGTM
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.
+1
I'm not sure I knew we had a style guide, but that's very helpful! In previous lives, active voice, and especially "you", were expressly prohibited in docs, so it's good to know that we're doing something different. I'll try to adjust the editing/muscle memory accordingly ;)
Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
Co-authored-by: Toshio Kuratomi <a.badger@gmail.com> Co-authored-by: Sandra McCann <samccann@redhat.com>
SUMMARY
Updates the porting guide for ansible-core 2.11 to avoid future tense, in accordance with the Ansible style guide.
The entry about validating
choices
illustrates the confusion that future tense can cause: the old text says "any settings that currently violate it and are currently ignored will now cause an error". Here "currently" means "in 2.10" and "now" means "in 2.11", but "currently" and "now" also mean the same thing. This is confusing enough in English, unless you know the context well. Translation would be difficult.ISSUE TYPE
COMPONENT NAME
porting guides
docs.ansible.com