docs(oxfmt): Include links for the VS Code extension in the formatter FAQ (#658)

Lead with the VS Code extension since that's the best route for many users. Also rephrase the wording slightly.

Signed-off-by: Connor Shea <connor.james.shea@gmail.com>

Author: connorshea

src/docs/guide/usage/formatter.md

@@ -162,10 +162,10 @@ For import sorting functionality, we provide experimental behavior based on `esl
 
 ### How does editor integration work?
 
-By running `oxfmt --lsp`, you can start a language server that responds to `textDocument/formatting` requests.
+For VS Code, the Oxc extension is available from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=oxc.oxc-vscode) and [Open VSX Registry](https://open-vsx.org/extension/oxc/oxc-vscode).
 
-Formatting via stdin and stdout are not supported, but we have confirmed that some editors and extensions can work with the CLI by configuring them to use temporary files.
+For other editors, by running `oxfmt --lsp` you can start a language server that responds to standard `textDocument/formatting` requests.
 
-Oxc VS Code extension is also available.
+Formatting via stdin and stdout are not supported, but we have confirmed that some editors and extensions can work with the CLI by configuring them to use temporary files.
 
-However, both methods have some limitations, such as not supporting formatting of embedded parts.
+However, these methods have some limitations, such as not supporting formatting of embedded parts.