Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: use more consistent formatting for deprecations #39218

Merged
merged 1 commit into from
Jul 3, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/api/deprecations.md
Original file line number Diff line number Diff line change
Expand Up @@ -1799,7 +1799,7 @@ Assigning properties to the top-level `this` as an alternative
to `module.exports` is deprecated. Developers should use `exports`
or `module.exports` instead.

### DEP0093: `crypto.fips` is deprecated and replaced.
### DEP0093: `crypto.fips` is deprecated and replaced
<!-- YAML
changes:
- version: v10.0.0
Expand All @@ -1812,7 +1812,7 @@ Type: Documentation-only
The [`crypto.fips`][] property is deprecated. Please use `crypto.setFips()`
and `crypto.getFips()` instead.

### DEP0094: Using `assert.fail()` with more than one argument.
### DEP0094: Using `assert.fail()` with more than one argument
<!-- YAML
changes:
- version: v10.0.0
Expand Down Expand Up @@ -1932,7 +1932,7 @@ Type: End-of-Life

The `--with-lttng` compile-time option has been removed.

### DEP0102: Using `noAssert` in `Buffer#(read|write)` operations.
### DEP0102: Using `noAssert` in `Buffer#(read|write)` operations
<!-- YAML
changes:
- version: v10.0.0
Expand Down