-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update to use code samples #136
Update to use code samples #136
Conversation
This pull request has been linked to Shortcut Story #38459: Tutorials need updating to refer to Quix Samples rather than Library. |
Docs preview site available at https://quixdocsdev.blob.core.windows.net/prdev/index.html |
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.
I think because these samples are a Quix-specific thing, and correspond to a UI item, and a repo, we are OK to refer to them as Quix Code Samples, or just Code Samples if the context is clear. At the moment we appear to be using a mix of case. I think word case is appropriate here, so "Code Samples" would be preferred, when referring to the entity contained in the samples repo. WDYT?
I think for the UI nav/menu item itself we should consistently use Code Samples
.
@tbedford updated. Please let me know what you think. |
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.
Looks good.
A few minor suggested changes.
docs/platform/tutorials/data-stream-processing/data-stream-processing.md
Outdated
Show resolved
Hide resolved
@tbedford how does this look? |
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!
No description provided.