-
Notifications
You must be signed in to change notification settings - Fork 65
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
Review Migration Guide for language and consistency #182
Comments
@boczkowska, I'd say at least some of this has already been completed in devfile/docs#22, right? Could you please check if more is needed? |
@rkratky sure, I'll pick it up |
This issue can be closed as I've done a language review of migrating-to-devfile-v2 and it looks good, and the PR's been merged. |
The content does not follow our style guide and still needs to be worked on. @jc-berger, which PR are you referring to? |
@rkratky, looking at PR #22: devfile/docs#22 And at migrating to devfile 2 which I believe is the PR's rendered version after the big doc restructure: https://docs.devfile.io/devfile/user-guide/migrating-to-devfile-v2.html |
@jc-berger, yes, I know about PR #22 -- that's why I commented above: "I'd say at least some of this has already been completed in devfile/docs#22, right? Could you please check if more is needed?" A quick glance reveals that more work indeed is needed in https://docs.devfile.io/devfile/user-guide/migrating-to-devfile-v2.html |
@rkratky, will review more next week, thanks. |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
Is your feature request related to a problem? Please describe.
The Migration Guide (https://devfile.github.io/devfile/migration_guide.html) needs to be reviewed and updated to follow Red Hat documentation and style guide principles.
Describe the solution you'd like
The content is consistent with language and style principles used by upstream Red Hat documentation projects.
The text was updated successfully, but these errors were encountered: