diff options
| author | Lance Ball <lball@redhat.com> | 2019-02-06 14:00:52 -0500 |
|---|---|---|
| committer | Lance Ball <lball@redhat.com> | 2019-02-06 14:00:52 -0500 |
| commit | 8b06da9d53c65c63c58e82287e37c084f9b16fe8 (patch) | |
| tree | b748d0ad2f67c097234f968e1ae84a182153f367 | |
| parent | a19cd87fdee32d81c95185590cdd016dc4f96317 (diff) | |
| download | node-new-pull-request-doc-updates.tar.gz | |
squash: incorporate feedback from contributorspull-request-doc-updates
| -rw-r--r-- | doc/guides/contributing/pull-requests.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/guides/contributing/pull-requests.md b/doc/guides/contributing/pull-requests.md index d43106c8c9..0e324211ee 100644 --- a/doc/guides/contributing/pull-requests.md +++ b/doc/guides/contributing/pull-requests.md @@ -116,9 +116,8 @@ time to ensure that the changes follow the Node.js code style guide. Any documentation you write (including code comments and API documentation) should follow the [Style Guide](../../STYLE_GUIDE.md). Code samples included in the API docs will also be checked when running `make lint` (or -`vcbuild.bat lint` on Windows). If you are adding to or deprecating the API, -be sure to use `REPLACEME` for the version numbers as specified in -[releases.md](../../releases.md#step-3-update-any-replaceme-and-dep00xx-tags-in-the-docs). +`vcbuild.bat lint` on Windows). If you are adding to or deprecating an API, +use `REPLACEME` for the version number in the documentation YAML. For contributing C++ code, you may want to look at the [C++ Style Guide](../../../CPP_STYLE_GUIDE.md). |