Update tutorial language #47
Merged
Conversation
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
This wording is hard to read in 2025, and effectively is no longer the standard terminology.
|
oh fiddlesticks. I didn't realize there was an instance of |
|
Probably good enough for now, I'd like to investigate adding new API methods and deprecating the older ones |
|
Thanks! Let's see if this gets published on merge |
|
It published, just checked it on GH. Thanks! |
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.
This wording is hard to read in 2025, and effectively is no longer the standard terminology.
It appears to me that github should just publish this with the typical jekyll setup, and so it will be deployed if/when merged. I'm not certain tho.