From 772ce0b38a159b672ac244ac636059a3c20932f2 Mon Sep 17 00:00:00 2001 From: "Kamat, Trivikram" <16024985+trivikr@users.noreply.github.com> Date: Fri, 1 Nov 2019 07:36:14 -0700 Subject: [PATCH] doc: linkify `.setupMaster()` in cluster doc Refs: https://github.com/nodejs/node/pull/30163 PR-URL: https://github.com/nodejs/node/pull/30204 Reviewed-By: Anna Henningsen Reviewed-By: Luigi Pinca Reviewed-By: David Carlier Reviewed-By: Gireesh Punathil --- doc/api/cluster.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/api/cluster.md b/doc/api/cluster.md index c4a47539472cb3..112da9b2aa402e 100644 --- a/doc/api/cluster.md +++ b/doc/api/cluster.md @@ -644,11 +644,11 @@ added: v0.7.1 * `settings` {Object} -Emitted every time `.setupMaster()` is called. +Emitted every time [`.setupMaster()`][] is called. The `settings` object is the `cluster.settings` object at the time -`.setupMaster()` was called and is advisory only, since multiple calls to -`.setupMaster()` can be made in a single tick. +[`.setupMaster()`][] was called and is advisory only, since multiple calls to +[`.setupMaster()`][] can be made in a single tick. If accuracy is important, use `cluster.settings`. @@ -710,7 +710,7 @@ added: v0.11.2 The scheduling policy, either `cluster.SCHED_RR` for round-robin or `cluster.SCHED_NONE` to leave it to the operating system. This is a global setting and effectively frozen once either the first worker is spawned, -or `cluster.setupMaster()` is called, whichever comes first. +or [`.setupMaster()`][] is called, whichever comes first. `SCHED_RR` is the default on all operating systems except Windows. Windows will change to `SCHED_RR` once libuv is able to effectively