@@ -587,7 +587,7 @@ assert.fail(new TypeError('need array'));
587587Using ` assert.fail() ` with more than two arguments is possible but deprecated.
588588See below for further details.
589589
590- ## assert.fail(actual, expected[ , message[ , operator[ , stackStartFunction ]]] )
590+ ## assert.fail(actual, expected[ , message[ , operator[ , stackStartFn ]]] )
591591<!-- YAML
592592added: v0.1.21
593593changes:
@@ -600,7 +600,7 @@ changes:
600600* ` expected ` {any}
601601* ` message ` {string|Error}
602602* ` operator ` {string} ** Default:** ` '!=' `
603- * ` stackStartFunction ` {Function} ** Default:** ` assert.fail `
603+ * ` stackStartFn ` {Function} ** Default:** ` assert.fail `
604604
605605> Stability: 0 - Deprecated: Use ` assert.fail([message]) ` or other assert
606606> functions instead.
@@ -610,7 +610,7 @@ If `message` is falsy, the error message is set as the values of `actual` and
610610` expected ` arguments are provided, ` operator ` will default to ` '!=' ` . If
611611` message ` is provided as third argument it will be used as the error message and
612612the other arguments will be stored as properties on the thrown object. If
613- ` stackStartFunction ` is provided, all stack frames above that function will be
613+ ` stackStartFn ` is provided, all stack frames above that function will be
614614removed from stacktrace (see [ ` Error.captureStackTrace ` ] ). If no arguments are
615615given, the default message ` Failed ` will be used.
616616
@@ -636,7 +636,7 @@ assert.fail(1, 2, new TypeError('need array'));
636636In the last three cases ` actual ` , ` expected ` , and ` operator ` have no
637637influence on the error message.
638638
639- Example use of ` stackStartFunction ` for truncating the exception's stacktrace:
639+ Example use of ` stackStartFn ` for truncating the exception's stacktrace:
640640
641641``` js
642642function suppressFrame () {
0 commit comments