internal: cleanup lsp-extensions docs

1 files changed, 18 insertions, 16 deletions

diff --git a/docs/dev/lsp-extensions.md b/docs/dev/lsp-extensions.md
index 98098b69a98..a6a1c73111b 100644
--- a/docs/dev/lsp-extensions.md
+++ b/docs/dev/lsp-extensions.md
@@ -27,7 +27,7 @@ https://clangd.llvm.org/extensions.html#utf-8-offsets
 
 ## Configuration in `initializationOptions`
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/567
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/567
 
 The `initializationOptions` field of the `InitializeParams` of the initialization request should contain the `"rust-analyzer"` section of the configuration.
 
@@ -43,7 +43,7 @@ If a language client does not know about `rust-analyzer`'s configuration options
 
 ## Snippet `TextEdit`
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/724
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/724
 
 **Experimental Client Capability:** `{ "snippetTextEdit": boolean }`
 
@@ -77,7 +77,7 @@ At the moment, rust-analyzer guarantees that only a single edit will have `Inser
 
 ## `CodeAction` Groups
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/994
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/994
 
 **Experimental Client Capability:** `{ "codeActionGroup": boolean }`
 
@@ -124,7 +124,7 @@ Invoking code action at this position will yield two code actions for importing
 
 ## Parent Module
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/1002
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/1002
 
 **Experimental Server Capability:** `{ "parentModule": boolean }`
 
@@ -158,7 +158,7 @@ mod foo;
 
 ## Join Lines
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/992
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/992
 
 **Experimental Server Capability:** `{ "joinLines": boolean }`
 
@@ -205,7 +205,7 @@ fn main() {
 
 ## On Enter
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/1001
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/1001
 
 **Experimental Server Capability:** `{ "onEnter": boolean }`
 
@@ -298,7 +298,7 @@ SSR with query `foo($a, $b) ==>> ($a).foo($b)` will transform, eg `foo(y + 5, z)
 
 ## Matching Brace
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/999
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/999
 
 **Experimental Server Capability:** `{ "matchingBrace": boolean }`
 
@@ -343,7 +343,7 @@ Moreover, it would be cool if editors didn't need to implement even basic langua
 
 ## Runnables
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/944
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/944
 
 **Experimental Server Capability:** `{ "runnables": { "kinds": string[] } }`
 
@@ -617,7 +617,7 @@ Such actions on the client side are appended to a hover bottom as command links:
 
 ## Open Cargo.toml
 
-**Issue:** https://github.com/rust-analyzer/rust-analyzer/issues/6462
+**Upstream Issue:** https://github.com/rust-analyzer/rust-analyzer/issues/6462
 
 **Experimental Server Capability:** `{ "openCargoToml": boolean }`
 
@@ -660,7 +660,7 @@ interface TestInfo {
 
 ## Hover Range
 
-**Issue:** https://github.com/microsoft/language-server-protocol/issues/377
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/377
 
 **Experimental Server Capability:** { "hoverRange": boolean }
 
@@ -687,7 +687,7 @@ Triggering a hover inside the selection above will show a result of `i32`.
 
 ## Move Item
 
-**Issue:** https://github.com/rust-analyzer/rust-analyzer/issues/6823
+**Upstream Issue:** https://github.com/rust-analyzer/rust-analyzer/issues/6823
 
 This request is sent from client to server to move item under cursor or selection in some direction.
 
@@ -712,7 +712,7 @@ export const enum Direction {
 
 ## Workspace Symbols Filtering
 
-**Issue:** https://github.com/rust-analyzer/rust-analyzer/pull/7698
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/941
 
 **Experimental Server Capability:** `{ "workspaceSymbolScopeKindFiltering": boolean }`
 
@@ -746,6 +746,8 @@ const enum WorkspaceSymbolSearchKind {
 
 ## Client Commands
 
+**Upstream Issue:** https://github.com/microsoft/language-server-protocol/issues/642
+
 **Experimental Client Capability:** `{ "commands?": ClientCommandOptions }`
 
 Certain LSP types originating on the server, notably code lenses, embed commands.
@@ -757,9 +759,9 @@ This extensions allows the client to communicate this info.
 
 ```typescript
 export interface ClientCommandOptions {
-	/**
-	 * The commands to be executed on the client
-	 */
-	commands: string[];
+    /**
+     * The commands to be executed on the client
+     */
+    commands: string[];
 }
 ```