Repository navigation
Fix typos in documentation - #422
Merged
Merged
Conversation
Collaborator
|
Hello @raus7n, |
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.
I fixed a few spelling mistakes in the documentation, code comments, and vignette.
Changes made:
assesment→assessmentinR/collection-rf100-damage.Rintializer→initializerinR/models-alexnet.Rinternaly→internallyinR/models-fcn.Rbouding→boundinginR/ops-box_convert.Roccuring→occurringin a code comment inR/transforms-tensor.Rhandeling→handling(3 occurrences) invignettes/torchvision-classes.RmdI found these with
codespell, checked each one manually, regenerated the affected help pages (rf100_damage_collection,model_alexnet,model_fcn_resnet,box_xywh_to_xyxy) usingdevtools::document()with roxygen2 8.1.1, and added an entry toNEWS.md.One thing I left unchanged:
codespellalso flagsclasssesin the 0.9.0 section ofNEWS.md. I left it as it is since it's part of an older release, but I'm happy to fix it if needed.These are just spelling and documentation fixes. No code logic or functionality was changed.