-
Notifications
You must be signed in to change notification settings - Fork 105
Fix content readability issues for upgrading your project section #4171
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
Fix content readability issues for upgrading your project section #4171
Conversation
|
The PR preview for be1cb58 is available at theforeman-foreman-documentation-preview-pr-4171.surge.sh The following output files are affected by this PR:
|
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
Edit - I prematurely acked. Take a look at my suggestions.
1c2bc14 to
2997fba
Compare
2997fba to
6cc3aa3
Compare
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.
Other than this small fix, LGTM.
Shorten/split long sentences in the 'Upgrading your project' section of the connected upgrade guide. JIRA: https://issues.redhat.com/browse/SAT-35663
6cc3aa3 to
be1cb58
Compare
) * Fix content readability issues for upgrading your project section Shorten/split long sentences in the 'Upgrading your project' section of the connected upgrade guide. JIRA: https://issues.redhat.com/browse/SAT-35663
Shorten/split long sentences in the 'Upgrading your project' section of the connected upgrade guide.
JIRA: https://issues.redhat.com/browse/SAT-35663
What changes are you introducing?
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into:
Review checklists
Tech review (performed by an Engineer who did not author the PR; can be skipped if tech review is unnecessary):
Style review (by a Technical Writer who did not author the PR):