fix(docs): Correct typos in README.md#251
Open
nishioka-shinji wants to merge 1 commit intoimgproxy:masterfrom
Open
fix(docs): Correct typos in README.md#251nishioka-shinji wants to merge 1 commit intoimgproxy:masterfrom
nishioka-shinji wants to merge 1 commit intoimgproxy:masterfrom
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
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.
Hi maintainers,
I noticed a couple of minor typos in the
README.mdwhile reading through the documentation. This small PR fixes them.Changes
Spelling error in heading:
In the "Complex processing options" section, the subheading
Using named arguments with usupported optionshas been corrected toUsing named arguments with unsupported options.Syntax error in code example:
In the "Unnamed arguments" section, the code example for
trimhad a syntax error (1. 1instead of1, 1). This has been corrected to match the resulting URL example shown below it.This is just a documentation fix and introduces no functional changes.
Cheers!