docs: clarify the operator design doc a bit #167
Merged
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.
I the operator design document, custom resource definition(CRD) seems to have been used as a synonym for custom resource(CR) which is usually not correct.
This change makes the wording a little clearer by using CRD only when technically correct and using CR when appropriate.
Describe what this PR does
Make some wording in the operator design doc a little clearer and more correct.
Is there anything that requires special attention
no
Do you have any questions?
no
Is the change backward compatible?
yes
Are there concerns around backward compatibility?
no
Provide any external context for the change, if any.
none
Related issues
none
Future concerns
none
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.