docs: [no-deprecated] awkward wording about TypeScript visualizing deprecated code (typescript-eslint#10337)

* Inaccuracy in no-deprecated

TypeScript can't visualize deprecated code, editors can.

* Update packages/eslint-plugin/docs/rules/no-deprecated.mdx

Co-authored-by: Kirk Waiblinger <[email protected]>

---------

Co-authored-by: Kirk Waiblinger <[email protected]>

Author: xuhdev

packages/eslint-plugin/docs/rules/no-deprecated.mdx

@@ -14,7 +14,7 @@ It's best to avoid using code marked as deprecated.
 This rule reports on any references to code marked as `@deprecated`.
 
 :::note
-[TypeScript recognizes the `@deprecated` tag](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html#deprecated) and visualizes deprecated code with a ~strikethrough~.
+[TypeScript recognizes the `@deprecated` tag](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html#deprecated), allowing editors to visually indicate deprecated code — usually with a ~strikethrough~.
 However, TypeScript doesn't report type errors for deprecated code on its own.
 :::