Merge branch 'main' into vnext

api/extension-guides/custom-editors.md

@@ -163,7 +163,7 @@ When a `TextDocument` changes, your extension also needs to make sure its webvie
 
 It's important to remember that any file edits that a custom editor triggers will cause `onDidChangeTextDocument` to fire. Make sure your extension does not get into an update loop where the user makes an edit in the webview, which fires `onDidChangeTextDocument`, which causes the webview to update, which causes the webview to trigger another update on your extension, which fires `onDidChangeTextDocument`, and so on.
 
-Also remember that if you are working with a structured language such as JSON or XML, the document may not always be in a valid state. Your extension must either be able gracefully handle errors or display an error message to the user so that they understand what is wrong and how to fix it.
+Also remember that if you are working with a structured language such as JSON or XML, the document may not always be in a valid state. Your extension must either be able to gracefully handle errors or display an error message to the user so that they understand what is wrong and how to fix it.
 
 Finally, if updating your webviews is expensive, consider [debouncing](https://davidwalsh.name/javascript-debounce-function) the updates to your webview.
 

api/language-extensions/images/overview/multi-editor.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:762b2a5bed7591918628d21749e227808ef3fc22f2f7a012a11c44e774025d4a
-size 70373
+oid sha256:e353137a2ece28d266b01684884508ddd6cda51d5f4f105f4d33d000e96f7d42
+size 86710

api/language-extensions/images/overview/multi-ls.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f3e69060bd7a883b6199009a693ffd13ed04fc8da0d80f9ab23fc95dcd1e288d
-size 70342
+oid sha256:3b7c6349dcb6247273565ed97a8b38709d3a7921d8dd25fb89719072deaca9d7
+size 83009

api/working-with-extensions/publishing-extension.md

@@ -522,3 +522,7 @@ The same rule applies for the [display name](/api/references/extension-manifest)
 ### What package managers are supported?
 
 You can either use npm or yarn v1 to manage your extension's dependencies.
+
+### I need help with my VS Marketplace account or support in publishing an extension?
+
+You can reach out to the VS Marketplace support team by signing in at [Manage Publishers & Extensions](https://marketplace.visualstudio.com/manage) and clicking on the ‘Contact Microsoft’ link at the top right.

azure-pipelines.yml

@@ -41,19 +41,10 @@ jobs:
     path: vscode-website/dist
     persistCredentials: true
   - task: NodeTool@0
-    displayName: Use Node 14.19.3
+    displayName: Use Node 20.x
     inputs:
-      versionSpec: 14.19.3
+      versionSpec: 20.x
       checkLatest: true
-  - task: Npm@0
-    displayName: npm install yarn
-    inputs:
-      arguments: -g yarn
-  - task: CmdLine@2
-    displayName: yarn install
-    inputs:
-      script: 'yarn install'
-      workingDirectory: '../vscode-website'
   - task: Bash@3
     displayName: Build Dist Setup
     inputs:

docs/cpp/cmake-linux.md

@@ -78,13 +78,13 @@ sudo apt-get install build-essential gdb
 
 ## Create a CMake project
 
-If you do not have an existing CMake project, follow the steps in [Create a CMake project](cmake-quickstart.md).
+If you do not have an existing CMake project, follow the steps in [Create a CMake project](cmake-quickstart).
 
 If you already have an existing CMake project that has a `CMakeLists.txt` file in the root directory, continue to [Configure Hello World](#configure-hello-world) to configure your project.
 
 ### Configure Hello World
 
-Before you can use the CMake Tools extension to build a project, you need to configure it to know about the compilers on your system. There are two ways to configure CMake in VS Code: 
+Before you can use the CMake Tools extension to build a project, you need to configure it to know about the compilers on your system. There are two ways to configure CMake in VS Code:
 
 - Use CMake Presets (recommended)
 - Use CMake Kits/Variants

docs/datascience/images/jupyter/cell-toggle-line-num.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8964ef62735640b25f9fb5e44fdd8dda86fa4e014404badc399df6592ce6cbc8
-size 12012
+oid sha256:39a42f4748d0e24ede754282d7818128fb2091516d406afce8a5a00b1e7c57e1
+size 16235

docs/datascience/images/jupyter/code-move.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c4180dcd6971c87d7ec6b3c417cf506af9cf2c8223f55f1debdd54f8463ec8bb
-size 43835
+oid sha256:7f076626e78016b1aba8ca657215cc3b029aa1a2b00b98b053a03a581f065437
+size 35614

docs/datascience/images/jupyter/debug-cell.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8353c586326b7a6de7e7657f9a346a4dd46a40c178cb208c7c59359f19e1f982
-size 103546
+oid sha256:2a6b5eac8a6e6122bc34ace46b5091dfeb09966adfafb4190b1b695f80042e62
+size 82738

docs/datascience/images/jupyter/intellisense.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:34346c9006c79480f5b64bbd4c989e444a00ddaf9a4341b9b4bcf2cb8e0d9750
-size 56079
+oid sha256:022514be399ab1da1b76c438f53d05018db1e187003d40e26d829e7371dfe901
+size 75424

docs/datascience/images/jupyter/multiselect.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:00f1b6dcc0e17c8060930b46e8eec79be21cccddc66defe1210fcde0789bdda1
-size 12282
+oid sha256:7c8f4b2698d0f199aa81a9e2de761cb11a4958f31382084171e58e0f44d30c41
+size 45929

docs/datascience/images/jupyter/native-add-cells.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7e9f50bcd6b23a4e4afdf9cb4efe4ea0cd31869130ba4d710e2875d263b29c38
-size 24789
+oid sha256:dd03ae1bd5f661cbbfc4952685d62e7ef7cd8b0b8541728843a08968cb42bb33
+size 58099

docs/datascience/images/jupyter/native-code-cells-01.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4ed409be75c4b0ef724349605bd3abe1431460ba5ac5e148fa4a4b11d0186584
-size 16202
+oid sha256:aca484b21d0c4599848e85d77c42fad9af91bc83533d8ffdd25a5f588111e38c
+size 39418

docs/datascience/images/jupyter/native-code-cells-02.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9a0b3964d2bcefb4fb790f1b31a939ba5ddd92f39a494262b747445e0510c006
-size 5188
+oid sha256:b6e246eb6b19b828ef44b919eb788e4fac023af8db5ebf47637c826a2d4d9379
+size 18921

docs/datascience/images/jupyter/native-code-cells-03.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f22354784eadac63940cfbb416fa0cdac097211052570ed014618960da777328
-size 26002
+oid sha256:35d175ea8bdcb12f32816769e98ace30bab7950e93dd1cad690e42b451e70942
+size 62806

docs/datascience/images/jupyter/native-code-cells-04.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3aa20b621a860c3216fe03b9ad234efb0b7a2fc887179767e6a1890672791590
-size 5213
+oid sha256:1e43ce2f640f5e1538cd9f339b927b5c0063248d44186360cc35d0157b88b6e0
+size 19143

docs/datascience/images/jupyter/native-code-delete.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5d11e812a4f73876f2411d6a6c62560a8abe06d8d8d7deb53bd01bee853d5020
-size 9223
+oid sha256:c0a87d393f178df0d24017f4a8f3c4590bfda464fbfbf849e7496ca1e0b99db4
+size 19183

docs/datascience/images/jupyter/native-code-runs.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c9bffbc1868ff970ac0cb1692aaf24960aa963d27dde557afe02c91f23977000
-size 44277
+oid sha256:2fa1f579b90801269d4e9e2df2c1cacb50bb564f464896e0164d42558808855f
+size 70971

docs/datascience/images/jupyter/native-kernel-picker.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:26fd943423820d200d172ca7c57892e854426126a832ea57d8f24f5224afa60c
-size 16082
+oid sha256:05568924dcc5caef6f7c2841959256c02e6386b7229fda1dcbf0836057afb453
+size 39471

docs/datascience/images/jupyter/native-language-picker-01.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5d18eee4597d74c9ad9cb6337409bf415f679bbb29d11b087e460e1c4cb1949e
-size 17813
+oid sha256:0492e9e35b9766275d84045778958fca90d0b866099a126a5d946ef8d7a312f3
+size 43924

docs/datascience/images/jupyter/native-markdown-htr.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ba4d800b49553a2998105b06806b05a1c4aabae3e95a5631063236f0ddca407e
-size 7994
+oid sha256:919226aa1b0e26f5738a1b4ea243721db6aee7640a670b46a95d5c6dd9d6b070
+size 56939

docs/datascience/images/jupyter/native-markdown-not-rendered.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7452d862dbb5d048e0db8cda031b9ae77ccdb555e9de03bc0fd17627e70d2ff2
-size 19230
+oid sha256:eaa4cee7c9df18c0050a869c5698f159035d50b74e0c641ea51ebc2278427d0c
+size 56902

docs/datascience/images/jupyter/native-markdown-rendered.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ce6fd16ffe924cc50b93305b65eb61273bd2ba46e0aa3e53b10c02710bff72b8
-size 20439
+oid sha256:fa8a9915b92162b23f38529cc62076a4969f6280c3d23fcf6578eeedbc97c3ae
+size 68671

docs/datascience/images/jupyter/native-toolbar-export.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:00a8c7db0a2551ad1a33024e8614f1afd4fdea71009c23a1859fc5decc416045
-size 17882
+oid sha256:dfd00b39b3a26dfbd4d6cc99caab3d09620e5baebcfb486db9e9248a2aca3110
+size 82608

docs/datascience/images/jupyter/notebook-toggle-line-num.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:16f7bf5cd163e2ac54f6285a89ec24683a95cc8dd381dde30d1b010bd9440970
-size 24971
+oid sha256:52d236d760fe7b22ca2e9c6541f17b7175cb912e6c87335b9197796d23da262a
+size 36632

docs/datascience/images/jupyter/notebook-toolbar.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f2cf9abea8be7df9c58aaee6060bd92e0ea432a9142b2e030d010a69822bc99a
-size 4942
+oid sha256:399aa02b6c8995552f2affedbd85ee813c2c2c30885f6716f7bcb6e5465b240d
+size 20297

docs/datascience/images/jupyter/run-by-line.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9c3892123b8e693ee3a865242d42b07883c2ea431ea11c05c2dbab9155331d6a
-size 110673
+oid sha256:323919d2609ab044ae8ae1e6bc0e71647e94bc2b093d34c230b0cb8e5405c9d7
+size 32035

docs/datascience/images/jupyter/save-output.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4324a72048517453b149abff2ef0a237d3ad8b0b18dbb8011831a25ae100fb07
-size 25809
+oid sha256:d2c47cfa892389bef99d7a3f8d199b8a4765b26d439a8580ef67abacc9815850
+size 29921

docs/datascience/images/jupyter/table-of-contents.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4e92299c2c665374350e17c8c0d76a7b888e7c6c0b24d22b67bb67e6aec952a7
-size 60034
+oid sha256:c643715c8732158718bb0580d05cd3a913fdd9bef5733f8c54fe640ce73af8fd
+size 59437

docs/datascience/images/jupyter/variable-explorer-01.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c9e6358bc4ec181ac8900cf0745d4a3925e9e6a72e2f74547fe1d5c9d4ab20f8
-size 43659
+oid sha256:68400e3d31c68922f47e03c1855e2a96dc02536ba1e3d80a7603b93cc1d96475
+size 49467

docs/datascience/images/jupyter/variable-explorer-02.png

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d59467800cba304dc79f67ee59fe0dff076706ab51e2c09a7d76bed2f5f33700
-size 42679
+oid sha256:6d3f9520261a0828fa8853dc2b83982c34b66de28f5eeed0fdbb48553b8f5523
+size 63723

docs/datascience/jupyter-notebooks.md

@@ -77,7 +77,7 @@ You can save your Jupyter Notebook using the keyboard shortcut `kbstyle(Ctrl+S)`
 
 ## Export your Jupyter Notebook
 
-You can export a Jupyter Notebook as a Python file (`.py`), a PDF, or an HTML file. To export, select the **Export** action on the main toolbar. You'll then be presented with a dropdown of file format options.
+You can export a Jupyter Notebook as a Python file (`.py`), a PDF, or an HTML file. To export, select **...** > **Export** on the main toolbar. You're then presented with a dropdown of file format options.
 
  ![Convert Jupyter Notebook to Python file](images/jupyter/native-toolbar-export.png)
 

docs/editor/codebasics.md

@@ -97,7 +97,7 @@ For more control over `Auto Save`, open User or Workspace [settings](/docs/getst
 
 ## Hot Exit
 
-VS Code will remember unsaved changes to files when you exit by default. Hot exit is triggered when the application is closed via **File** > **Exit** (**Code** > **Quit** on macOS) or when the last window is closed.
+By default, VS Code remembers unsaved changes to files when you exit. Hot exit is triggered when the application is closed via **File** > **Exit** (**Code** > **Quit** on macOS) or when the last window is closed.
 
 You can configure hot exit by setting `files.hotExit` to the following values:
 
@@ -105,7 +105,7 @@ You can configure hot exit by setting `files.hotExit` to the following values:
 * `"onExit"`: Hot exit will be triggered when the application is closed, that is when the last window is closed on Windows/Linux or when the `workbench.action.quit` command is triggered (from the **Command Palette**, keyboard shortcut or menu). All windows without folders opened will be restored upon next launch.
 * `"onExitAndWindowClose"`: Hot exit will be triggered when the application is closed, that is when the last window is closed on Windows/Linux or when the `workbench.action.quit` command is triggered (from the **Command Palette**, keyboard shortcut or menu), and also for any window with a folder opened regardless of whether it is the last window. All windows without folders opened will be restored upon next launch. To restore folder windows as they were before shutdown, set `window.restoreWindows` to `all`.
 
-If something happens to go wrong with hot exit, all backups are stored in the following folders for standard install locations:
+If something goes wrong with hot exit, all backups are stored in the following folders for standard install locations:
 
 * **Windows** `%APPDATA%\Code\Backups`
 * **macOS** `$HOME/Library/Application Support/Code/Backups`
@@ -259,7 +259,7 @@ The `search.searchEditor.reusePriorSearchConfiguration` setting (default is `fal
 
 We'll always offer word completion, but for the rich [languages](/docs/languages/overview.md), such as JavaScript, JSON, HTML, CSS, SCSS, Less, C# and TypeScript, we offer a true IntelliSense experience. If a language service knows possible completions, the IntelliSense suggestions will pop up as you type. You can always manually trigger it with `kb(editor.action.triggerSuggest)`.  By default, `kbstyle(Tab)` or `kbstyle(Enter)` are the accept keyboard triggers but you can also [customize these key bindings](/docs/getstarted/keybindings.md).
 
-> **Tip:** The suggestions filtering supports CamelCase so you can type the letters which are upper cased in a method name to limit the suggestions. For example, "cra" will quickly bring up "createApplication".
+> **Tip:** The suggestions filtering supports CamelCase, so you can type the letters which are upper cased in a method name to limit the suggestions. For example, "cra" will quickly bring up "createApplication".
 
 > **Tip:** IntelliSense suggestions can be configured via the `editor.quickSuggestions` and `editor.suggestOnTriggerCharacters` [settings](/docs/getstarted/settings.md).
 
@@ -398,6 +398,23 @@ Then choose an encoding.
 
 ![Select an encoding](images/codebasics/encodingselection.png)
 
+## Compare files
+
+VS Code supports several ways to compare the content of the current file or of any two files.
+
+When you have an active file open in the editor, you have the following compare options:
+
+* **Compare with a workspace file**: in the Command Palette, select **File: Compare Active File With...**, and then choose another file to compare with.
+* **Compare with clipboard**: in the Command Palette, select **File: Compare Active File with Clipboard** (`kb(workbench.files.action.compareWithClipboard)`) to compare the current file with the clipboard content.
+* **Compare with saved**: in the Command Palette, select **File: Compare Active File with Saved** (`kb(workbench.files.action.compareWithSaved)`) to compare the current file with the last saved version.
+
+To compare any two files:
+
+* Right-click on a file in the Explorer view and select **Select for Compare**. Then, right-click on a second file and select **Compare with Selected**.
+* To start a comparison between two empty editor windows, select **File: Compare New Untitled Text Files** from the Command Palette.
+
+> **Tip:** You can start VS Code from the command line with the `--diff` option to compare two files. Learn more about the [VS Code command line interface](/docs/editor/command-line.md#core-cli-options).
+
 ## Next steps
 
 You've covered the basic user interface - there is a lot more to VS Code.  Read on to find out about:

docs/editor/multi-root-workspaces.md

@@ -138,7 +138,7 @@ VS Code UI such as the **OPEN EDITORS** and **Quick Open** (`kb(workbench.action
 
 ![quick pick has folder name](images/multi-root-workspaces/quick-open-list.png)
 
-If you are using an [File Icon Theme](/docs/getstarted/themes.md#file-icon-themes) and the active theme supports it, you will see a special Workspace icon.
+If you are using a [File Icon Theme](/docs/getstarted/themes.md#file-icon-themes) and the active theme supports it, you will see a special Workspace icon.
 
 Below you can see the Workspace icons from the built-in **Minimal (Visual Studio Code)** file icon theme:
 

docs/getstarted/tips-and-tricks.md

@@ -912,6 +912,12 @@ git config --global diff.tool vscode
 git config --global difftool.vscode.cmd 'code --wait --diff $LOCAL $REMOTE'
 ```
 
+## Compare file with the clipboard
+
+Keyboard Shortcut: `kb(workbench.files.action.compareWithClipboard)`
+
+Quickly compare the active file with the contents of the clipboard with the **File: Compare Active File with Clipboard** command in the Command Palette (`kb(workbench.action.showCommands)`).
+
 ## Debugging
 
 ### Configure debugger

docs/sourcecontrol/overview.md

@@ -171,7 +171,7 @@ The Diff editor has a separate gutter in the middle, which enables you to **Stag
 
 ![Screenshot of the Diff editor, showing the Stage and Revert controls in the gutter](images/overview/diffEditor-stage-revert-demo.gif)
 
->**Tip:** You can diff any two files by first right clicking on a file in the Explorer or **OPEN EDITORS** list and selecting **Select for Compare** and then right-click on the second file to compare with and select **Compare with 'file_name_you_chose'**.   Alternatively from the keyboard hit `kb(workbench.action.showCommands)` and select **File: Compare Active File With** and you will be presented with a list of recent files.
+> **Tip**: You can diff any two files by first right-clicking on a file in the Explorer view and selecting **Select for Compare** and then right-click on the second file to compare with and select **Compare with Selected**. Alternatively, open the Command Palette (`kb(workbench.action.showCommands)`), and select ay of the **File: Compare** commands. Learn more about the different options to [compare files in VS Code](/docs/editor/codebasics.md#compare-files).
 
 ### Accessible Diff Viewer
 

release-notes/v0_7_0.md

@@ -127,7 +127,7 @@ This includes sections on:
 ## PHP
 We added a set of common snippets for PHP.  To access these hit `kb(editor.action.triggerSuggest)` to get a context specific list.
 
-![PHP Snipets](images/0_7_0/PHPSnip.png)
+![PHP Snippets](images/0_7_0/PHPSnip.png)
 
 ## C#
 We have moved to the latest OmniSharp version 1.1.0.

release-notes/v1_13.md

@@ -166,7 +166,7 @@ Set `emmet.useNewEmmet` to `true` to start using this new feature. This feature
 If you have `editor.quickSuggestions` turned off, you can use one of the methods below to get Emmet expansion:
 
 * Manually trigger the suggestion by pressing `kb(editor.action.triggerSuggest)` and then choose the expansion from the suggestion list.
-* Run the command **Emmet: Expand Abbreviation** explicity from the **Command Palette**.
+* Run the command **Emmet: Expand Abbreviation** explicitly from the **Command Palette**.
 * Bind your own keyboard [shortcut](https://code.visualstudio.com/docs/getstarted/keybindings) to **Emmet: Expand Abbreviation** (command id `editor.emmet.action.expandAbbreviation`).
 
 You will see two kinds of suggestions in HTML-like files:

release-notes/v1_22.md

@@ -180,7 +180,7 @@ The boxes for include and exclude patterns in the Search view have been combined
 
 ### Tree: Horizontal scrolling support
 
-There's a new global setting, `workbench.tree.horizontalScrolling`, which enables horizontal scrolling for several tree widgets across the workbench. Use it to provide better readibility for wide tree elements such as deep file system hierarchies in the File Explorer.
+There's a new global setting, `workbench.tree.horizontalScrolling`, which enables horizontal scrolling for several tree widgets across the workbench. Use it to provide better readability for wide tree elements such as deep file system hierarchies in the File Explorer.
 
 ## Integrated Terminal
 

release-notes/v1_23.md

@@ -182,7 +182,7 @@ Use the **Developer: Open Process Explorer** command or **Help** > **Open Proces
 
 ### Multi-root support for terminal splitting
 
-You will now be able to select the folder to split the terminal into when inside a multi-root workspace. The old behavior can be reenabled by keybinding the `workbench.action.terminal.splitInActiveWorkspace` command.
+You will now be able to select the folder to split the terminal into when inside a multi-root workspace. The old behavior can be re-enabled by keybinding the `workbench.action.terminal.splitInActiveWorkspace` command.
 
 ## Languages
 

release-notes/v1_44.md

@@ -170,7 +170,7 @@ This change does not affect the font choice in the editor.
 
 VS Code will now keep the **Undo/Redo** stack of a file when the file is closed. When the file is reopened, if its contents hasn't changed since it was closed, the Undo/Redo stack will be restored.
 
-This is very useful if you limit the number of open editors with the `workbench.editor.limit.value` setting or you accidently close a file you are working on.
+This is very useful if you limit the number of open editors with the `workbench.editor.limit.value` setting or you accidentally close a file you are working on.
 
 ### Explicit ordering for Code Actions on save
 

release-notes/v1_65.md

@@ -562,7 +562,7 @@ The following screencast shows that the intermediate object makes it difficult t
 
 In this release, we have improved VS Code to render the intermediate object in a compact form with a **(...)** button for requesting the full value.
 
-![Reviewing property getter values with lazy evaluation triggerd by '(...)' button](images/1_65/lazy-after.gif)
+![Reviewing property getter values with lazy evaluation triggered by '(...)' button](images/1_65/lazy-after.gif)
 
 A debug adapter can request this new presentation style for a variable by adding a `VariablePresentationHint` with a `lazy` property ([see DAP additions](#debug-adapter-protocol)). If the client does not support the `lazy` flag, the variable will be shown as before.
 

release-notes/v1_70.md

@@ -500,7 +500,7 @@ On window reload, watch tasks can be reconnected to by enabling `task.experiment
 
 We have been working to provide a better experience with **Code Actions** in VS Code. [Code Actions](https://code.visualstudio.com/docs/editor/refactoring#_code-actions-quick-fixes-and-refactorings) include [Refactorings](https://code.visualstudio.com/docs/languages/typescript#_refactoring), Source Actions, and Quick Fixes.
 
-The new experimental Code Actions control can be opened from the [context menu](https://code.visualstudio.com/api/ux-guidelines/context-menus) by selecting **Refactor** or **Source Action**, from a lighbulb, or via a Quick Fix. Try it out via the `editor.experimental.useCustomCodeActionMenu` setting. Let us know about any feedback by creating issues in the [VS Code repository](https://github.com/microsoft/vscode/issues) or commenting in [issue #152913](https://github.com/microsoft/vscode/issues/152913).
+The new experimental Code Actions control can be opened from the [context menu](https://code.visualstudio.com/api/ux-guidelines/context-menus) by selecting **Refactor** or **Source Action**, from a lightbulb, or via a Quick Fix. Try it out via the `editor.experimental.useCustomCodeActionMenu` setting. Let us know about any feedback by creating issues in the [VS Code repository](https://github.com/microsoft/vscode/issues) or commenting in [issue #152913](https://github.com/microsoft/vscode/issues/152913).
 
 Refactoring previews for Code Actions are also accessible from the new Code Action control. Hover over enabled items to view how to preview. Custom keybindings are supported for selection of Code Actions, as well as to preview the selection.
 

release-notes/v1_77.md

@@ -174,7 +174,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
 
 ### Extension installation not blocked by signature verification failures
 
-Extension signature verification is incorrectly reporting errors for a small number of valid extensions and preventing them from being installed. These failures are caused by bugs in the VS Marketplace and VS Code and we are actively working on fixes. In order to unblock extension use, VS Code will install extensions even if signing verification fails. We will reenable signature verification checking once [VS Marketplace issue #619](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
+Extension signature verification is incorrectly reporting errors for a small number of valid extensions and preventing them from being installed. These failures are caused by bugs in the VS Marketplace and VS Code and we are actively working on fixes. In order to unblock extension use, VS Code will install extensions even if signing verification fails. We will re-enable signature verification checking once [VS Marketplace issue #619](https://github.com/microsoft/vsmarketplace/issues/619) is fixed, most likely in our next Stable release.
 
 ## Contributions to extensions
 

release-notes/v1_89.md

@@ -453,7 +453,7 @@ This API is used by the GitHub Pull Request extension's Issues and PR views.
 
 The language model namespace (`vscode.lm`) exports new functions to retrieve language model information and to count tokens for a given string. Those are `getLanguageModelInformation` and `computeTokenLength` respectively. You should use these functions to build prompts that are within the limits of a language model.
 
-> **Note**: inline chat is now powered by the upcoming chat particpants API. This also means `registerInteractiveEditorSessionProvider` is deprecated and will be removed very soon.
+> **Note**: inline chat is now powered by the upcoming chat participants API. This also means `registerInteractiveEditorSessionProvider` is deprecated and will be removed very soon.
 
 ### Updated document paste proposal
 

release-notes/v1_91.md

@@ -5,10 +5,12 @@ PageTitle: Visual Studio Code June 2024
 MetaDescription: Learn what is new in the Visual Studio Code June 2024 Release (1.91)
 MetaSocialImage: 1_91/release-highlights.png
 Date: 2024-7-3
-DownloadVersion: 1.91.0
+DownloadVersion: 1.91.1
 ---
 # June 2024 (version 1.91)
 
+**Update 1.91.1**: The update addresses these [issues](https://github.com/microsoft/vscode/issues?q=is%3Aissue%20milestone%3A%22June%202024%20Recovery%201%22%20is%3Aclosed%20).
+
 <!-- DOWNLOAD_LINKS_PLACEHOLDER -->
 
 ---
@@ -246,7 +248,7 @@ A new hint is displayed in the terminal to help discover the inline chat.
 
 This hint only shows when the Copilot extension is installed and there is a single terminal that has not had any interaction. It's easy to dismiss the message permanently by right-clicking it. The message also dismisses after you use terminal inline chat for the first time.
 
-#### Appy Code Block
+#### Apply Code Block
 
 The **Apply In Editor** command on a code block in the Chat view uses the language model to determine the best approach for applying the changes to the current editor.
 

release-notes/vJanuary.md

@@ -229,7 +229,7 @@ Whenever the editor contents is not loaded from the file system but comes from t
 
 ### Remote Debugging
 
-The followings improvements enable VS Code to support remote debugging, includes debugging into a Docker container:
+The following improvements enable VS Code to support remote debugging, includes debugging into a Docker container:
 
 * The `attach` launch configuration now supports an `address` attribute where a remote host can be specified. Please note that remote debugging is only supported on recent versions of Node.js (>= 4.x).
 * The `attach` launch configuration now supports a `localRoot` and a `remoteRoot` attribute that can be used to map paths between a local VS Code project and a (remote) Node.js folder. This works even locally on the same system or across different operating systems. Whenever a code path needs to be converted from the remote Node.js to a local VS Code path, the `remoteRoot` path is stripped off the path and replaced by `localRoot`. For the reverse conversion, the `localRoot` path is replaced by the `remoteRoot`.

release-notes/vMarch.md

@@ -8,7 +8,7 @@ MetaDescription: See what is new in the Visual Studio Code March 2016 Release (1
 
 ## March 2016 (1.0)
 
-March was the end game milestone leading up to our [1.0 release](/blogs/2016/04/14/vscode-1.0.md).  We wanted the product to meet the high expections of a 1.0 release and we focused on fundamentals like quality, accessibility, global reach and performance. We also added features you care about and streamlined some common tasks.
+March was the end game milestone leading up to our [1.0 release](/blogs/2016/04/14/vscode-1.0.md).  We wanted the product to meet the high expectations of a 1.0 release and we focused on fundamentals like quality, accessibility, global reach and performance. We also added features you care about and streamlined some common tasks.
 
 Here are a few highlights in this release: