Skip to content

Commit 8d8f7c6

Browse files
committed
doc: revise deepEqual() legacy assertion mode text
* Remove "potentially". It's arguably misplaced and certainly unnecessary. * Use italics for words-as-words usage of _Deep equality_ rather than using quotation marks. PR-URL: #31704 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent 7e38629 commit 8d8f7c6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/api/assert.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -200,9 +200,9 @@ An alias of [`assert.deepStrictEqual()`][].
200200
201201
Tests for deep equality between the `actual` and `expected` parameters. Consider
202202
using [`assert.deepStrictEqual()`][] instead. [`assert.deepEqual()`][] can have
203-
potentially surprising results.
203+
surprising results.
204204

205-
"Deep" equality means that the enumerable "own" properties of child objects
205+
_Deep equality_ means that the enumerable "own" properties of child objects
206206
are also recursively evaluated by the following rules.
207207

208208
### Comparison details

0 commit comments

Comments
 (0)