Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: fixes a typo in the async_hooks documentation #13666

Closed
wants to merge 2 commits into from

Conversation

chris--young
Copy link

@chris--young chris--young commented Jun 13, 2017

Fixes a minor typo as described by @mscdex in #13663

Generally it will correspond the name of the resource's constructor.

should read "will correspond with..."

fixes: #13663

Checklist
Affected core subsystem(s)

doc

@nodejs-github-bot nodejs-github-bot added async_hooks Issues and PRs related to the async hooks subsystem. doc Issues and PRs related to the documentations. labels Jun 13, 2017
Copy link
Contributor

@vsemozhetbyt vsemozhetbyt left a comment

Choose a reason for hiding this comment

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

Thank you!

@mscdex
Copy link
Contributor

mscdex commented Jun 13, 2017

Minor nit to whomever lands this, 'fixes:' should probably be 'Fixes:' in the commit message.

Otherwise LGTM.

@chris--young chris--young changed the title doc: fixes a typo in the async_hooks documentation doc: Fixes a typo in the async_hooks documentation Jun 13, 2017
> Generally it will correspond the name of the resource's constructor.
should read "will correspond with..."

Fixes: nodejs#13663
@chris--young chris--young changed the title doc: Fixes a typo in the async_hooks documentation doc: fixes a typo in the async_hooks documentation Jun 13, 2017
@@ -192,8 +192,8 @@ Every new resource is assigned a unique ID.
###### `type`

The `type` is a string that represents the type of resource that caused
`init` to be called. Generally it will correspond the name of the resource's
constructor.
`init` to be called. Generally it will correspond with the name of the
Copy link
Member

Choose a reason for hiding this comment

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

correspond to?

Copy link
Member

Choose a reason for hiding this comment

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

While we're in here, can you put a comma after Generally?

> Generally it will correspond the name of the resource's constructor.

should read "Generally, it will correspond to the name..."

Fixes: nodejs#13663
@tniessen tniessen self-assigned this Jun 14, 2017
@tniessen
Copy link
Member

Landed in 386f53f, thank you for your first contribution! 🎉

@tniessen tniessen closed this Jun 15, 2017
tniessen pushed a commit that referenced this pull request Jun 15, 2017
> Generally it will correspond the name of the resource's constructor.
should read "Generally, it will correspond to the name..."

PR-URL: #13666
Fixes: #13663
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
addaleax pushed a commit that referenced this pull request Jun 17, 2017
> Generally it will correspond the name of the resource's constructor.
should read "Generally, it will correspond to the name..."

PR-URL: #13666
Fixes: #13663
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
@addaleax addaleax mentioned this pull request Jun 17, 2017
addaleax pushed a commit that referenced this pull request Jun 21, 2017
> Generally it will correspond the name of the resource's constructor.
should read "Generally, it will correspond to the name..."

PR-URL: #13666
Fixes: #13663
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
@addaleax addaleax mentioned this pull request Jun 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
async_hooks Issues and PRs related to the async hooks subsystem. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

doc: typo in async_hooks documentation