chore: change either to any by jmeridth · Pull Request #668 · InnerSourceCommons/InnerSourcePatterns · GitHub
Skip to content

chore: change either to any - #668

Merged
spier merged 1 commit into
InnerSourceCommons:mainfrom
jmeridth:jm-grammar
Mar 24, 2024
Merged

chore: change either to any#668
spier merged 1 commit into
InnerSourceCommons:mainfrom
jmeridth:jm-grammar

Conversation

@jmeridth

Copy link
Copy Markdown

In its current context, there are 3 choices so any is more appropriate. either is for binary decisions (between 2 choices).

In its current context, there are 3 choices so `any` is more
appropriate.  `either` is for binary decisions (between 2 choices).

Signed-off-by: jmeridth <jmeridth@gmail.com>
@welcome

welcome Bot commented Mar 24, 2024

Copy link
Copy Markdown

@spier spier left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the fix. Hope you found it easy enough to figure out how to contribute?

Many of our patterns were written by contributors that speak English as a foreign language. So I am sure there are many more language/grammar improvements like this to be made 😃

Thanks again!

@spier
spier merged commit 9394132 into InnerSourceCommons:main Mar 24, 2024
@welcome

welcome Bot commented Mar 24, 2024

Copy link
Copy Markdown

Congratulations Banner
Congrats on merging your first pull request! 🎉 We here at The InnerSource Commons are proud of you! 💖 Thank you so much for your contribution 🎁

@jmeridth
jmeridth deleted the jm-grammar branch March 24, 2024 12:49
@jmeridth

Copy link
Copy Markdown
Author

@spier Yes. Contribution process was very easy. Thank you. I'm re-reading the entire patterns book again and may have other PRs. This one was the gateway PR and felt very nitpicky but thank you for merging it. Cheers.

@spier

spier commented Mar 24, 2024

Copy link
Copy Markdown
Member

That's great @jmeridth. Looking forward to any and all contributions that you want to make.

And no worry about nitpicking, if we really don't want to make a change that you are suggesting, we can just talk about that in any future PRs. No harm done, quite the opposite actually, as it is always great to have somebody with fresh eyes read our patterns again!

@spier

spier commented Mar 24, 2024

Copy link
Copy Markdown
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants