Skip to content
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

Minor tidy re use of 'openSUSE' #509

Closed
phillxnet opened this issue Oct 30, 2024 · 1 comment · Fixed by #510
Closed

Minor tidy re use of 'openSUSE' #509

phillxnet opened this issue Oct 30, 2024 · 1 comment · Fixed by #510
Assignees

Comments

@phillxnet
Copy link
Member

Re recent changes in docs in our V3 to V4+ migration doc we have explicit use, though contextualised via "version" etc, of "openSUSE". This could be construed as non conformant or in lacking clear adhearance to:

https://en.opensuse.org/openSUSE:Trademark_guidelines

Which we acknowledge in our EULA.

It is proposed that we revisit recent changes in at least our sub-titles of our V3 to v4* "Built on openSUSE" migration doc so that we use our preferred elsewhere nomenclature of "Uses opeenSUSE" (Web-UI) & "Built on openSUSE" almost everywehre else. These are among the suggested/acceptale terms in the above guide.

@phillxnet
Copy link
Member Author

Linking to #508 for context.

@phillxnet phillxnet self-assigned this Oct 30, 2024
@phillxnet phillxnet changed the title Minor tidy re use of "openSUSE" Minor tidy re use of 'openSUSE' Oct 30, 2024
phillxnet added a commit to phillxnet/rockstor-doc that referenced this issue Oct 30, 2024
Light edit re semantic linefeeds, and use of the Trademark 'openSUSE'.
Specifically in the newly altered v3 to newer major versions migration
doc.

#Includes
- Additional overview (sub-title and note) re v4 no longer auto-importing
the system disk.
- Minor rewording.
phillxnet added a commit that referenced this issue Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant