Add-on Store: Revision of User Guide language for better explanation of free add-ons with paid components#14982
Merged
Conversation
…commercial add-ons.
Collaborator
Author
|
CC @ruifontes |
CyrilleB79
reviewed
Jun 7, 2023
Co-authored-by: Cyrille Bougot <cyrille.bougot2@laposte.net>
See test results for failed build of commit 97e286973c |
Contributor
|
By me, it is good... |
seanbudd
approved these changes
Jun 9, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Pursuant to #14966 (comment), #14966 (comment), and #14966 (comment)
Summary of the issue:
Consideration of the language to use in the User Guide, when describing all add-ons as free in the store, while certain add-ons require the purchase of components or licenses in order to do anything.
Description of user facing changes
Revised language.
Description of development approach
Edited the language to be more in line with the comments in #14966. It may still not be as desired, but this provides a context to revise it in.
Testing strategy:
N/A
Known issues with pull request:
WIP.