Skip to content

Commit a6b1474

Browse files
Remove broken anchor link (#2717)
Co-authored-by: Jo Franchetti <jofranchetti@gmail.com>
1 parent 12b8276 commit a6b1474

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

runtime/reference/cli/unstable_flags.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ oldUrl:
55
- /runtime/manual/tools/unstable_flags/
66
---
77

8-
New features of the Deno runtime are often released behind feature flags, so
9-
users can try out new APIs and features before they are finalized. Current
10-
unstable feature flags are listed on this page, and can also be found in the CLI
11-
help text by running:
8+
New Deno runtime features are often released behind feature flags, so that users
9+
can try out new APIs and features before they are finalized. Current unstable
10+
feature flags are listed on this page, and can also be found in the CLI help
11+
text by running:
1212

1313
```sh
1414
deno --help
@@ -61,7 +61,7 @@ This flag enables you to
6161
[import Node.js built-in modules](/runtime/fundamentals/node/#node-built-in-modules)
6262
without a `node:` specifier, as in the example below. You can also use this flag
6363
to enable npm packages without an `npm:` specifier if you are manually managing
64-
your Node.js dependencies ([see `byonm` flag](#--unstable-byonm)).
64+
your Node.js dependencies.
6565

6666
```ts title="example.ts"
6767
import { readFileSync } from "fs";

0 commit comments

Comments
 (0)