fix: replace explicit with specify as verb#665
Merged
aduh95 merged 1 commit intonodejs:mainfrom Feb 26, 2025
MikeMcC399:explicit-to-specify
Merged
fix: replace explicit with specify as verb#665aduh95 merged 1 commit intonodejs:mainfrom MikeMcC399:explicit-to-specify
aduh95 merged 1 commit intonodejs:mainfrom
MikeMcC399:explicit-to-specify
Conversation
aduh95
approved these changes
Feb 26, 2025
aduh95
pushed a commit
to aduh95/corepack
that referenced
this pull request
Feb 28, 2025
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
2 participants
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.
Issue
The adjective explicit is used incorrectly as a verb.
devEngines#643 although it does not originate from this PR.Change
Replace the use of "explicit" using the transitive verb specify.
This affects only a comment and error messages.