Skip to content

doc: fixes a typo in the async_hooks documentation - #13666

Closed
chris--young wants to merge 2 commits into
nodejs:masterfrom
chris--young:async-doc-typo
Closed

doc: fixes a typo in the async_hooks documentation#13666
chris--young wants to merge 2 commits into
nodejs:masterfrom
chris--young:async-doc-typo

Conversation

@chris--young

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

Copy link
Copy Markdown

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-botnodejs-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

@vsemozhetbytvsemozhetbyt left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thank you!

@mscdex

mscdex commented Jun 13, 2017

Copy link
Copy Markdown
Contributor

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

Otherwise LGTM.

@chris--youngchris--young changed the title doc: fixes a typo in the async_hooks documentationdoc: Fixes a typo in the async_hooks documentationJun 13, 2017
> Generally it will correspond the name of the resource's constructor.
should read "will correspond with..."
Fixes: nodejs#13663
@chris--youngchris--young changed the title doc: Fixes a typo in the async_hooks documentationdoc: fixes a typo in the async_hooks documentationJun 13, 2017
Comment threaddoc/api/async_hooks.md Outdated
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
Copy Markdown
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
Copy Markdown
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
@tniessentniessen self-assigned this Jun 14, 2017
@tniessen

Copy link
Copy Markdown
Member

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

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: #13666Fixes: #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: #13666Fixes: #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>
@addaleaxaddaleax 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: #13666Fixes: #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>
@addaleaxaddaleax mentioned this pull request Jun 21, 2017
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

async_hooksIssues and PRs related to the async hooks subsystem.docIssues 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

11 participants

@chris--young@mscdex@tniessen@refack@jasnell@Trott@TimothyGu@cjihrig@vsemozhetbyt@MylesBorins@nodejs-github-bot