From ab2b651b0ed22855ca61c552f7807541e610e567 Mon Sep 17 00:00:00 2001
From: Uli <8657779+ulrichstark@users.noreply.github.com>
Date: Thu, 23 Nov 2023 08:02:18 +0100
Subject: [PATCH] Fix incorrect example command

- the package name crossenv is parked by NPM (https://www.npmjs.com/package/crossenv). cross-env is the intended one

- there's no npm command "lint" (https://docs.npmjs.com/cli/v6/commands)
---
 docs/linting/Troubleshooting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/linting/Troubleshooting.mdx b/docs/linting/Troubleshooting.mdx
index 847f6ff66bf6..ec964d14e843 100644
--- a/docs/linting/Troubleshooting.mdx
+++ b/docs/linting/Troubleshooting.mdx
@@ -335,7 +335,7 @@ Make sure you're using the latest versions of each of your ESLint plugins (and o
 
 If you've using many ESLint plugins, have updated each to their latest version, and you're not sure which one this complaint is coming from, try either or both of:
 
-- Running with [`--trace-deprecation`](https://nodejs.org/api/cli.html#--trace-deprecation) (e.g. `npx crossenv NODE_OPTIONS=--trace-deprecation npm lint`)
+- Running with [`--trace-deprecation`](https://nodejs.org/api/cli.html#--trace-deprecation) (e.g. `npx cross-env NODE_OPTIONS=--trace-deprecation npm run lint`)
 - Disabling half of them at a time to narrow down which plugin it is
 
 Then make sure each of those plugins has a GitHub issue asking that they release a version supporting typescript-eslint v6.