Update Instances of drop-down

blogs/2019/10/31/inspecting-containers.md

@@ -72,7 +72,7 @@ During this time, VS Code is installing an instance of the VS Code **Server** in
 
 ![Remote Container architecture diagram](remote-container-architecture.png)
 
-Once the connection is complete, you should have a new VS Code window with a green indicator in the bottom left that shows this instance of VS Code is running in a remote context. If you click on the indicator, you see will see a drop-down of commands relevant to the current remote context.
+Once the connection is complete, you should have a new VS Code window with a green indicator in the bottom left that shows this instance of VS Code is running in a remote context. If you click on the indicator, you see will see a dropdown of commands relevant to the current remote context.
 
 ![Remote context shown in the Status bar](remote-context-status-bar.png)
 

docs/cpp/pipe-transport.md

@@ -41,7 +41,7 @@ You may also need to add a `sourceFileMap` to map the path of where the code exi
 
 ## Attach
 
-You can also use the above `pipeTransport` block to attach to a remote process. In the attach case, you need to specify a `processId`. The extension can query processes from the remote machine. To do this, change `processId": "${command:pickProcess}` to `processId": "${command:pickRemoteProcess}`. The `pipeTransport` settings will be used to query the processes on the remote machine. Then select the process from the drop-down list. As with `launch`, you may need to configure `sourceFileMap`.
+You can also use the above `pipeTransport` block to attach to a remote process. In the attach case, you need to specify a `processId`. The extension can query processes from the remote machine. To do this, change `processId": "${command:pickProcess}` to `processId": "${command:pickRemoteProcess}`. The `pipeTransport` settings will be used to query the processes on the remote machine. Then select the process from the dropdown list. As with `launch`, you may need to configure `sourceFileMap`.
 
 ## Docker example
 

docs/editor/accessibility.md

@@ -27,7 +27,7 @@ When you adjust the zoom level with the **View** > **Zoom In / Out** commands, t
 
 ## High Contrast theme
 
-We support a High Contrast color theme on all platforms.  Use **File** > **Preferences** > **Color Theme** (`kb(workbench.action.selectTheme)`) to display the **Select Color Theme** drop-down and select the **High Contrast** theme.
+We support a High Contrast color theme on all platforms.  Use **File** > **Preferences** > **Color Theme** (`kb(workbench.action.selectTheme)`) to display the **Select Color Theme** dropdown and select the **High Contrast** theme.
 
 ![High Contrast Theme](images/accessibility/high-contrast.png)
 

docs/editor/codebasics.md

@@ -301,7 +301,7 @@ VS Code analyzes your open file and determines the indentation used in the docum
 
 ![auto detect indentation](images/codebasics/indentation-detection.png)
 
-You can click on the Status Bar indentation display to bring up a drop-down with indentation commands allowing you to change the default settings for the open file or convert between tab stops and spaces.
+You can click on the Status Bar indentation display to bring up a dropdown with indentation commands allowing you to change the default settings for the open file or convert between tab stops and spaces.
 
 ![indentation commands](images/codebasics/indentation-commands.png)
 

docs/editor/debugging.md

@@ -119,7 +119,7 @@ To add a new configuration to an existing `launch.json`, use one of the followin
 
 VS Code also supports compound launch configurations for starting multiple configurations at the same time; for more details, please read this [section](#compound-launch-configurations).
 
-In order to start a debug session, first select the configuration named **Launch Program** using the **Configuration drop-down** in the Run view. Once you have your launch configuration set, start your debug session with `kb(workbench.action.debug.start)`.
+In order to start a debug session, first select the configuration named **Launch Program** using the **Configuration dropdown** in the Run view. Once you have your launch configuration set, start your debug session with `kb(workbench.action.debug.start)`.
 
 Alternatively you can run your configuration through the **Command Palette** (`kb(workbench.action.showCommands)`), by filtering on **Debug: Select and Start Debugging** or typing `'debug '`, and selecting the configuration you want to debug.
 
@@ -206,7 +206,7 @@ The following attributes are mandatory for every launch configuration:
 
 * `type` - the type of debugger to use for this launch configuration. Every installed debug extension introduces a type: `node` for the built-in Node debugger, for example, or `php` and `go` for the PHP and Go extensions.
 * `request` - the request type of this launch configuration. Currently, `launch` and `attach` are supported.
-* `name` - the reader-friendly name to appear in the Debug launch configuration drop-down.
+* `name` - the reader-friendly name to appear in the Debug launch configuration dropdown.
 
 Here are some optional attributes available to all launch configurations:
 
@@ -316,7 +316,7 @@ A powerful VS Code debugging feature is the ability to set conditions based on e
 - **Expression condition**: The breakpoint will be hit whenever the expression evaluates to `true`.
 - **Hit count**: The 'hit count' controls how many times a breakpoint needs to be hit before it will 'break' execution. Whether a 'hit count' is respected and the exact syntax of the expression vary among debugger extensions.
 
-You can add a condition and/or hit count when creating a source breakpoint (with the **Add Conditional Breakpoint** action) or when modifying an existing one (with the **Edit Condition** action). In both cases, an inline text box with a drop-down menu opens where you can enter expressions:
+You can add a condition and/or hit count when creating a source breakpoint (with the **Add Conditional Breakpoint** action) or when modifying an existing one (with the **Edit Condition** action). In both cases, an inline text box with a dropdown menu opens where you can enter expressions:
 
 ![HitCount](images/debugging/hitCount.gif)
 
@@ -391,8 +391,8 @@ For complex scenarios involving more than one process (for example, a client and
 Using multi-target debugging is simple: after you've started a first debug session, you can just launch another session. As soon as a second session is up and running, the VS Code UI switches to _multi-target mode_:
 
 - The individual sessions now show up as top-level elements in the **CALL STACK** view.<BR>![Callstack View](images/debugging/debug-callstack.png)
-- The debug toolbar shows the currently **active session** (and all other sessions are available in a drop-down menu).<BR>![Debug Actions Widget](images/debugging/debug-actions-widget.png)
+- The debug toolbar shows the currently **active session** (and all other sessions are available in a dropdown menu).<BR>![Debug Actions Widget](images/debugging/debug-actions-widget.png)
-- Debug actions (for example, all actions in the debug toolbar) are performed on the active session. The active session can be changed either by using the drop-down menu in the debug toolbar or by selecting a different element in the **CALL STACK** view.
+- Debug actions (for example, all actions in the debug toolbar) are performed on the active session. The active session can be changed either by using the dropdown menu in the debug toolbar or by selecting a different element in the **CALL STACK** view.
 
 ### Compound launch configurations
 
@@ -425,7 +425,7 @@ An alternative way to start multiple debug sessions is by using a **compound** l
 }
 ```
 
-Compound launch configurations are displayed in the launch configuration drop-down menu.
+Compound launch configurations are displayed in the launch configuration dropdown menu.
 
 ## Remote debugging
 
@@ -529,6 +529,6 @@ To write your own debugger extension, visit:
 
 Debugging of Node.js-based applications is supported on Linux, macOS, and Windows out of the box with VS Code. Many other scenarios are supported by [VS Code extensions](https://marketplace.visualstudio.com/vscode/Debuggers?sortBy=Downloads) available in the Marketplace.
 
-### I do not see any launch configurations in the Run view drop-down. What is wrong?
+### I do not see any launch configurations in the Run view dropdown. What is wrong?
 
 The most common problem is that you did not set up `launch.json` or there is a syntax error in that file. Alternatively, you might need to open a folder, since no-folder debugging does not support launch configurations.

docs/editor/editingevolved.md

@@ -149,7 +149,7 @@ For your protection, VS Code displays a prompt before opening an outgoing websit
 
 ![Outgoing link prompt](images/editingevolved/outgoing-link-prompt.png)
 
-You can proceed to the external website in your browser or have the options to copy the link or cancel the request. If you choose **Configure Trusted Domains**, a drop-down lets you trust the exact URL, trust the URL domain and subdomains, or trust all domains to disable outgoing link protection.
+You can proceed to the external website in your browser or have the options to copy the link or cancel the request. If you choose **Configure Trusted Domains**, a dropdown lets you trust the exact URL, trust the URL domain and subdomains, or trust all domains to disable outgoing link protection.
 
 ![Configure Trusted Domains dropdown](images/editingevolved/trusted-domain-dropdown.png)
 

docs/editor/extension-gallery.md

@@ -79,11 +79,11 @@ VS Code makes it easy to manage your extensions. You can install, disable, updat
 
 ### List installed extensions
 
-By default, the Extensions view will show the extensions you currently have enabled, all extensions that are recommended for you, and a collapsed view of all extensions you have disabled. You can use the **Show Installed Extensions** command, available in the **Command Palette** (`kb(workbench.action.showCommands)`) or the **More Actions** (`...`) drop-down menu, to clear any text in the search box and show the list of all installed extensions, which includes those that have been disabled.
+By default, the Extensions view will show the extensions you currently have enabled, all extensions that are recommended for you, and a collapsed view of all extensions you have disabled. You can use the **Show Installed Extensions** command, available in the **Command Palette** (`kb(workbench.action.showCommands)`) or the **More Actions** (`...`) dropdown menu, to clear any text in the search box and show the list of all installed extensions, which includes those that have been disabled.
 
 ### Uninstall an extension
 
-To uninstall an extension, click the gear button at the right of an extension entry and then choose **Uninstall** from the drop-down menu. This will uninstall the extension and prompt you to reload VS Code.
+To uninstall an extension, click the gear button at the right of an extension entry and then choose **Uninstall** from the dropdown menu. This will uninstall the extension and prompt you to reload VS Code.
 
 ![uninstall an extension](images/extension-gallery/uninstall-extension.png)
 
@@ -91,17 +91,17 @@ To uninstall an extension, click the gear button at the right of an extension en
 
 If you don't want to permanently remove an extension, you can instead temporarily disable the extension by clicking the gear button at the right of an extension entry. You can disable an extension globally or just for your current Workspace. You will be prompted to reload VS Code after you disable an extension.
 
-If you want to quickly disable all installed extensions, there is a **Disable All Installed Extensions** command in the **Command Palette** and **More Actions** (`...`) drop-down menu.
+If you want to quickly disable all installed extensions, there is a **Disable All Installed Extensions** command in the **Command Palette** and **More Actions** (`...`) dropdown menu.
 
 Extensions remain disabled for all VS Code sessions until you re-enable them.
 
 ### Enable an extension
 
-Similarly if you have disabled an extension (it will be in the **Disabled** section of the list and marked ***Disabled***), you can re-enable it with the **Enable** or **Enable (Workspace)** commands in the drop-down menu.
+Similarly if you have disabled an extension (it will be in the **Disabled** section of the list and marked ***Disabled***), you can re-enable it with the **Enable** or **Enable (Workspace)** commands in the dropdown menu.
 
 ![enable extension](images/extension-gallery/enable-extension.png)
 
-There is also an **Enable All Extensions** command in the **More Actions** (`...`) drop-down menu.
+There is also an **Enable All Extensions** command in the **More Actions** (`...`) dropdown menu.
 
 ### Extension auto-update
 
@@ -207,7 +207,7 @@ Tags may contain any string and are not provided by IntelliSense, so review the
 
 ## Install from a VSIX
 
-You can manually install a VS Code extension packaged in a `.vsix` file. Using the **Install from VSIX** command in the Extensions view command drop-down, or the **Extensions: Install from VSIX** command in the **Command Palette**, point to the `.vsix` file.
+You can manually install a VS Code extension packaged in a `.vsix` file. Using the **Install from VSIX** command in the Extensions view command dropdown, or the **Extensions: Install from VSIX** command in the **Command Palette**, point to the `.vsix` file.
 
 You can also install using the VS Code `--install-extension` command-line switch providing the path to the `.vsix` file.
 
@@ -278,7 +278,7 @@ Some users prefer to download an extension once from the Marketplace and then in
 
 To download an extension, navigate to the details page for the specific extension within the [Marketplace](https://marketplace.visualstudio.com/vscode). On that page, there is a **Download Extension** link in the **Resources** section, which is located on the right-hand side of the page.
 
-Once downloaded, you can then install the extension via the **Install from VSIX** command in the Extensions view command drop-down.
+Once downloaded, you can then install the extension via the **Install from VSIX** command in the Extensions view command dropdown.
 
 ### Can I stop VS Code from providing extension recommendations?
 

docs/editor/integrated-terminal.md

@@ -23,7 +23,7 @@ To open the terminal:
 
 ## Managing multiple terminals
 
-You can create multiple terminals open to different locations and easily navigate between them. Terminal instances can be added by clicking the plus icon on the top-right of the **TERMINAL** panel or by triggering the `kb(workbench.action.terminal.new)` command. This action creates another entry in the drop-down list that can be used to switch between them.
+You can create multiple terminals open to different locations and easily navigate between them. Terminal instances can be added by clicking the plus icon on the top-right of the **TERMINAL** panel or by triggering the `kb(workbench.action.terminal.new)` command. This action creates another entry in the dropdown list that can be used to switch between them.
 
 ![Multiple Terminals](images/integrated-terminal/terminal-multiple-instances.png)
 
@@ -242,7 +242,7 @@ Note that the command only works with the `\u0000` format for using characters v
 
 ## Rename terminal sessions
 
-Integrated Terminal sessions can now be renamed using the **Terminal: Rename** (`workbench.action.terminal.rename`) command. The new name will be displayed in the terminal selection drop-down.
+Integrated Terminal sessions can now be renamed using the **Terminal: Rename** (`workbench.action.terminal.rename`) command. The new name will be displayed in the terminal selection dropdown.
 
 ## Open at a specific folder
 

docs/editor/multi-root-workspaces.md

@@ -182,7 +182,7 @@ When you go from a single folder instance to multiple folders, VS Code will add
 
 You can easily review and modify the different settings files through the Settings editor. The Settings editor tabs let you select your User settings, global Workspace settings, and individual folder settings.
 
-![settings drop-down](images/multi-root-workspaces/settings-dropdown.png)
+![settings dropdown](images/multi-root-workspaces/settings-dropdown.png)
 
 You can also open specific settings files with the commands:
 
@@ -202,13 +202,13 @@ Unsupported editor-wide folder settings will be shown as grayed out in your fold
 
 With multi-root workspaces, VS Code searches across all folders for `launch.json` debug configuration files and displays them with the folder name as a suffix. Additionally VS Code will also display launch configurations defined in the workspace configuration file.
 
-![debugging drop-down](images/multi-root-workspaces/debugging-dropdown.png)
+![debugging dropdown](images/multi-root-workspaces/debugging-dropdown.png)
 
 The example above shows the debugging configurations for the [TSLint extension](https://marketplace.visualstudio.com/items?itemName=eg2.tslint). There is a `launch` configuration from the `tslint` extension folder to start the extension running in the VS Code Extension Host and also an `attach` configuration from the `tslint-server` folder to attach the debugger to a running TSLint server.
 
-You can also see the three **Add Config** commands for the folders, `tslint`, `tslint-server`, and `tslint-tests`, in the vscode-tslint [Workspace](https://github.com/microsoft/vscode-tslint/blob/main/vscode-tslint.code-workspace). The **Add Config** command will either open an existing `launch.json` file in the folder's `.vscode` subfolder or create a new one and display the debugging configuration template drop-down.
+You can also see the three **Add Config** commands for the folders, `tslint`, `tslint-server`, and `tslint-tests`, in the vscode-tslint [Workspace](https://github.com/microsoft/vscode-tslint/blob/main/vscode-tslint.code-workspace). The **Add Config** command will either open an existing `launch.json` file in the folder's `.vscode` subfolder or create a new one and display the debugging configuration template dropdown.
 
-![debugging template drop-down](images/multi-root-workspaces/add-launch-config.png)
+![debugging template dropdown](images/multi-root-workspaces/add-launch-config.png)
 
 [Variables](/docs/editor/variables-reference.md) used in a configuration (for example `${workspaceFolder}` or the now deprecated `${workspaceRoot}`) are resolved relative to the folder they belong to. It is possible to scope a variable per workspace folder by appending the root folder's name to a variable (separated by a colon).
 
@@ -218,7 +218,7 @@ Workspace scoped launch configurations live in the `"launch"` section of the wor
 
 ![Workspace Settings](images/multi-root-workspaces/workspace-settings.png)
 
-Alternatively, new launch configurations can be added via the "Add Config (workspace)" entry of the Launch Configuration drop-down menu:
+Alternatively, new launch configurations can be added via the "Add Config (workspace)" entry of the Launch Configuration dropdown menu:
 
 ![Add Config](images/multi-root-workspaces/add-config.png)
 
@@ -275,7 +275,7 @@ Here is an example for a launch configuration where the program lives in a folde
 
 Similar to how VS Code searches for debugging configurations, VS Code will also try to autodetect tasks from gulp, grunt, npm, and TypeScript project files across all folders in a workspace as well as search for tasks defined in `tasks.json` files. The location of tasks is indicated by a folder name suffix. Note that tasks defined in `tasks.json` must be version 2.0.0.
 
-![tasks drop-down](images/multi-root-workspaces/tasks-dropdown.png)
+![tasks dropdown](images/multi-root-workspaces/tasks-dropdown.png)
 
 From the TSLint extension [Workspace](https://github.com/microsoft/vscode-tslint/blob/main/vscode-tslint.code-workspace) example above, you can see that there are two **configured tasks** from `tasks.json` files in the `tslint` and `tslint-tests` folders and numerous autodetected npm and TypeScript compiler **detected tasks**.
 

docs/editor/tasks-v1.md

@@ -53,7 +53,7 @@ You should now see a `tasks.json` file in your workspace `.vscode` folder with t
 
 In this example, we are just running the `echo` shell command with "Hello World" as an argument.
 
-Test the `echo` task by running **Tasks: Run Task** and selecting `echo` from the drop-down list. The **OUTPUT** panel will open and you'll see the text "Hello World".
+Test the `echo` task by running **Tasks: Run Task** and selecting `echo` from the dropdown list. The **OUTPUT** panel will open and you'll see the text "Hello World".
 
 You can get IntelliSense on `tasks.json` variables and their values with hover and trigger smart completions with `kb(editor.action.triggerSuggest)`.
 
@@ -79,7 +79,7 @@ To see the exact command VS Code is running, you can enable the `echoCommand` se
 
 ## command and tasks[]
 
-`tasks.json` takes a single `command` value which can be a task runner like gulp or grunt or any command-line tool like a compiler or linter. By default, the `command` will show up in the **Tasks: Run Task** drop-down list.
+`tasks.json` takes a single `command` value which can be a task runner like gulp or grunt or any command-line tool like a compiler or linter. By default, the `command` will show up in the **Tasks: Run Task** dropdown list.
 
 You can also define multiple tasks in a `tasks` array in order to pass different arguments or use different settings when the `command` is run.
 
@@ -107,7 +107,7 @@ Here's a simple example passing different arguments to the `echo` command:
 }
 ```
 
-Now when you run **Tasks: Run Task**, you will now see two tasks in the drop-down list, `hello` and `bye`. We set `suppressTaskName` to true as by default the task name is also passed to the command which would result in "echo hello Hello World".
+Now when you run **Tasks: Run Task**, you will now see two tasks in the dropdown list, `hello` and `bye`. We set `suppressTaskName` to true as by default the task name is also passed to the command which would result in "echo hello Hello World".
 
 ![tasks array](images/tasks/tasks-array.png)
 

docs/editor/userdefinedsnippets.md

@@ -37,7 +37,7 @@ If you find an extension you want to use, install it, then restart VS Code and t
 
 You can easily define your own snippets without any extension. To create or edit your own snippets, select **User Snippets** under **File** > **Preferences** (**Code** > **Preferences** on macOS), and then select the language (by [language identifier](/docs/languages/identifiers.md)) for which the snippets should appear, or the **New Global Snippets file** option if they should appear for all languages. VS Code manages the creation and refreshing of the underlying snippets file(s) for you.
 
-![snippet drop-down](images/userdefinedsnippets/snippet-dropdown.png)
+![snippet dropdown](images/userdefinedsnippets/snippet-dropdown.png)
 
 Snippets files are written in JSON, support C-style comments, and can define an unlimited number of snippets. Snippets support most TextMate syntax for dynamic behavior, intelligently format whitespace based on the insertion context, and allow easy multiline editing.
 

docs/editor/versioncontrol.md

@@ -85,7 +85,7 @@ You'll also see the option to **Clone from GitHub**. Once you authenticate with
 
 You can create and checkout branches directly within VS code through the **Git: Create Branch** and **Git: Checkout to** commands in the **Command Palette** (`kb(workbench.action.showCommands)`).
 
-If you run **Git: Checkout to**, you will see a drop-down list containing all of the branches or tags in the current repository. It will also give you the option to create a new branch if you decide that's a better option, or checkout a branch in detached mode.
+If you run **Git: Checkout to**, you will see a dropdown list containing all of the branches or tags in the current repository. It will also give you the option to create a new branch if you decide that's a better option, or checkout a branch in detached mode.
 
 ![Git checkout](images/versioncontrol/gitbranches.png)
 
@@ -159,7 +159,7 @@ Visual Studio Code supports more Git history workflows through [extensions](/doc
 
 You can always peek under the hood to see the Git commands we are using.  This is helpful if something strange is happening or if you are just curious. :)
 
-To open the Git output window, run **View** > **Output** and select **Git** from the drop-down list.
+To open the Git output window, run **View** > **Output** and select **Git** from the dropdown list.
 
 ## Initialize a repository
 

docs/getstarted/settings.md

@@ -49,7 +49,7 @@ When you open the settings editor, you can search and discover settings you are
 
 ### Edit settings
 
-Each setting can be edited by either a **checkbox**, an **input** or by a **drop-down**. Edit the text or select the option you want to change to the desired settings.
+Each setting can be edited by either a **checkbox**, an **input** or by a **dropdown**. Edit the text or select the option you want to change to the desired settings.
 
 ![Edit a Setting](images/settings/settings-edit.png)
 
@@ -81,7 +81,7 @@ To customize your editor by language, run the global command **Preferences: Conf
 
 ![Configure language-specific settings command](images/settings/pref-config-lang-settings.png)
 
-Select the language via the drop-down:
+Select the language via the dropdown:
 
 ![Select language dropdown](images/settings/lang-selection.png)
 

docs/getstarted/telemetry.md

@@ -47,11 +47,11 @@ For example, the [GitHub Pull Requests extension](https://marketplace.visualstud
 
 ## Output channel for telemetry events
 
-If you'd like to review the telemetry events in VS Code as they are sent, you can enable tracing and it will record telemetry events. Set the log level to **Trace** using the **Developer: Set Log Level...** command and then in the Output panel (`kb(workbench.action.output.toggleOutput)`), pick **Log (Telemetry)** from the drop-down.
+If you'd like to review the telemetry events in VS Code as they are sent, you can enable tracing and it will record telemetry events. Set the log level to **Trace** using the **Developer: Set Log Level...** command and then in the Output panel (`kb(workbench.action.output.toggleOutput)`), pick **Log (Telemetry)** from the dropdown.
 
 ![output panel log telemetry](images/telemetry/output-log-telemetry.png)
 
-When tracing telemetry events, the events are also logged to a local file `telemetry.log` which you can view using the **Developer: Open Log File...** command and choosing **Telemetry** from the drop-down.
+When tracing telemetry events, the events are also logged to a local file `telemetry.log` which you can view using the **Developer: Open Log File...** command and choosing **Telemetry** from the dropdown.
 
 ![open telemetry log file](images/telemetry/open-telemetry-log.png)
 

docs/getstarted/themes.md

@@ -151,7 +151,7 @@ See the [Create a new Color Theme](/api/extension-guides/color-theme.md#create-a
 
 ## Remove default Color Themes
 
-If you'd like to remove some of the default themes shipped with VS Code from the Color Theme picker, you can disable them from the Extensions view (`kb(workbench.view.extensions)`). Open the `...` **More Actions** drop-down menu from the top of the Extensions view, select **Show Built-in Extensions**, and you'll see a **THEMES** section listing the default themes.
+If you'd like to remove some of the default themes shipped with VS Code from the Color Theme picker, you can disable them from the Extensions view (`kb(workbench.view.extensions)`). Open the `...` **More Actions** dropdown menu from the top of the Extensions view, select **Show Built-in Extensions**, and you'll see a **THEMES** section listing the default themes.
 
 ![built-in themes](images/themes/built-in-themes.png)
 
@@ -170,7 +170,7 @@ File icon themes can be contributed by extensions and selected by users as their
 3. Use the cursor keys to preview the icons of the theme.
 4. Select the theme you want and hit `kbstyle(Enter)`.
 
-![file icon theme drop-down](images/themes/file-icon-theme-dropdown.png)
+![file icon theme dropdown](images/themes/file-icon-theme-dropdown.png)
 
 By default, the **Seti** file icon set is used and those are the icons you see in the File Explorer. Once a file icon theme is selected, the selected theme will be remembered and appear again whenever VS Code is restarted. You can disable file icons by selecting **None**.
 

docs/getstarted/tips-and-tricks.md

@@ -834,7 +834,7 @@ Click the (...) button and then select **Undo Last Commit** to undo the previous
 
 VS Code makes it easy to see what Git commands are actually running. This is helpful when learning Git or debugging a difficult source control issue.
 
-Use the **Toggle Output** command (`kb(workbench.action.output.toggleOutput)`) and select **Git** in the drop-down.
+Use the **Toggle Output** command (`kb(workbench.action.output.toggleOutput)`) and select **Git** in the dropdown.
 
 ### Gutter indicators
 

docs/getstarted/userinterface.md

@@ -229,7 +229,7 @@ When you open a file, a new Tab is added for that file.
 
 Tabs let you quickly navigate between items and you can Drag and Drop Tabs to reorder them.
 
-When you have more open items than can fit in the title area, you can use the **Show Opened Editors** command (available through the `...` More button) to display a drop-down list of tabbed items.
+When you have more open items than can fit in the title area, you can use the **Show Opened Editors** command (available through the `...` More button) to display a dropdown list of tabbed items.
 
 If you don't want to use Tabs, you can disable the feature by setting the `workbench.editor.showTabs` [setting](/docs/getstarted/settings.md) to false:
 

docs/languages/cpp.md

@@ -132,7 +132,7 @@ Now that we have a simple C++ program, let's build it. Select the **Terminal** >
 
 ![Run Build Task menu option](images/cpp/run-build-task.png)
 
-This will display a drop-down with various compiler task options. If you are using a GCC toolset like MinGW, you would choose **C/C++: g++.exe build active file**.
+This will display a dropdown with various compiler task options. If you are using a GCC toolset like MinGW, you would choose **C/C++: g++.exe build active file**.
 
 ![Select g++.exe task](images/cpp/select-gpp-task.png)
 

docs/languages/overview.md

@@ -41,11 +41,11 @@ The richness of support varies across the different languages and their extensio
 
 ## Changing the language for the selected file
 
-In VS Code, we default the language support for a file based on its filename extension. However, at times you may wish to change language modes, to do this click on the language indicator - which is located on the right hand of the Status Bar. This will bring up the **Select Language Mode** drop-down where you can select another language for the current file.
+In VS Code, we default the language support for a file based on its filename extension. However, at times you may wish to change language modes, to do this click on the language indicator - which is located on the right hand of the Status Bar. This will bring up the **Select Language Mode** dropdown where you can select another language for the current file.
 
 ![Language Selector](images/overview/languageselect.png)
 
-**Tip**: You can get the same drop-down by running the **Change Language Mode** command (`kb(workbench.action.editor.changeLanguageMode)`).
+**Tip**: You can get the same dropdown by running the **Change Language Mode** command (`kb(workbench.action.editor.changeLanguageMode)`).
 
 ## Language Id
 
@@ -53,7 +53,7 @@ VS Code associates a language mode with a specific language identifier so that v
 
 A language identifier is often (but not always) the lowercased programming language name. Note that casing matters for exact identifier matching ('Markdown' != 'markdown'). Unknown language files have the language identifier `plaintext`.
 
-You can see the list of currently installed languages and their identifiers in the **Change Language Mode** (`kb(workbench.action.editor.changeLanguageMode)`) drop-down.
+You can see the list of currently installed languages and their identifiers in the **Change Language Mode** (`kb(workbench.action.editor.changeLanguageMode)`) dropdown.
 
 ![language identifiers](images/overview/language-identifiers.png)
 

docs/languages/php.md

@@ -53,7 +53,7 @@ Visual Studio Code includes a set of common snippets for PHP. To access these, h
 
 ## PHP extensions
 
-There are many PHP language extensions available on the [VS Code Marketplace](https://marketplace.visualstudio.com/VSCode) and more are being created. You can search for PHP extensions from within VS Code in the **Extensions** view (`kb(workbench.view.extensions)`) then filter the extensions drop-down list by typing 'php'.
+There are many PHP language extensions available on the [VS Code Marketplace](https://marketplace.visualstudio.com/VSCode) and more are being created. You can search for PHP extensions from within VS Code in the **Extensions** view (`kb(workbench.view.extensions)`) then filter the extensions dropdown list by typing 'php'.
 
 ![Searching for PHP in the Extensions view](images/php/category-php.png)
 

docs/nodejs/angular-tutorial.md

@@ -123,7 +123,7 @@ To set a breakpoint in `app.component.ts`, click on the gutter to the left of th
 
 ### Configure the Chrome debugger
 
-We need to initially configure the [debugger](/docs/editor/debugging.md). To do so, go to the Run view (`kb(workbench.view.debug)`) and click on the gear button to create a `launch.json` debugger configuration file. Choose **Chrome** from the **Select Environment** drop-down list. This will create a `launch.json` file in a new `.vscode` folder in your project which includes a configuration to launch the website.
+We need to initially configure the [debugger](/docs/editor/debugging.md). To do so, go to the Run view (`kb(workbench.view.debug)`) and click on the gear button to create a `launch.json` debugger configuration file. Choose **Chrome** from the **Select Environment** dropdown list. This will create a `launch.json` file in a new `.vscode` folder in your project which includes a configuration to launch the website.
 
 We need to make one change for our example: change the port of the `url` from `8080` to `4200`. Your `launch.json` should look like this:
 

docs/nodejs/nodejs-tutorial.md

@@ -184,7 +184,7 @@ You will need to create a debugger configuration file `launch.json` for your Exp
 }
 ```
 
-Save the new file and make sure **Launch Program** is selected in the configuration drop-down at the top of the Run view. Open `app.js` and set a breakpoint near the top of the file where the Express app object is created by clicking in the gutter to the left of the line number. Press `kb(workbench.action.debug.start)` to start debugging the application. VS Code will start the server in a new terminal and hit the breakpoint we set. From there you can inspect variables, create watches, and step through your code.
+Save the new file and make sure **Launch Program** is selected in the configuration dropdown at the top of the Run view. Open `app.js` and set a breakpoint near the top of the file where the Express app object is created by clicking in the gutter to the left of the line number. Press `kb(workbench.action.debug.start)` to start debugging the application. VS Code will start the server in a new terminal and hit the breakpoint we set. From there you can inspect variables, create watches, and step through your code.
 
 ![Debug session](images/nodejs/debugsession.png)
 

docs/nodejs/reactjs-tutorial.md

@@ -127,7 +127,7 @@ To set a breakpoint in `index.js`, click on the gutter to the left of the line n
 
 ### Configure the Chrome debugger
 
-We need to initially configure the [debugger](/docs/editor/debugging.md). To do so, go to the Run view (`kb(workbench.view.debug)`) and click **create a launch.json file** to customize Run and Debug. Choose **Chrome** from the **Select Environment** drop-down list. This will create a `launch.json` file in a new `.vscode` folder in your project which includes a configuration to launch the website.
+We need to initially configure the [debugger](/docs/editor/debugging.md). To do so, go to the Run view (`kb(workbench.view.debug)`) and click **create a launch.json file** to customize Run and Debug. Choose **Chrome** from the **Select Environment** dropdown list. This will create a `launch.json` file in a new `.vscode` folder in your project which includes a configuration to launch the website.
 
 We need to make one change for our example: change the port of the `url` from `8080` to `3000`. Your `launch.json` should look like this:
 

docs/python/debugging.md

@@ -171,7 +171,7 @@ In some scenarios, you need to debug a Python script that's invoked locally by a
 
 1. In the terminal, start Python with the script, for example, `python3 myscript.py`. You should see the "Waiting for debugger attach" message that's included in the code, and the script halts at the `debugpy.wait_for_client()` call.
 
-1. Switch to the Run view, select the appropriate configuration from the debugger drop-down list, and start the debugger.
+1. Switch to the Run view, select the appropriate configuration from the debugger dropdown list, and start the debugger.
 
 1. The debugger should stop on the `debugpy.breakpoint()` call, from which point you can use the debugger normally. You can, of course, set other breakpoints in the script code using the UI instead of using `debugpy.breakpoint()`.
 
@@ -318,7 +318,7 @@ The specific settings are described in the following sections. You can also add
 
 ### `name`
 
-Provides the name for the debug configuration that appears in the VS Code drop-down list.
+Provides the name for the debug configuration that appears in the VS Code dropdown list.
 
 ### `type`
 
@@ -445,7 +445,7 @@ The Python extension automatically detects breakpoints that are set on non-execu
 
 ## Debugging specific app types
 
-The configuration drop-down provides a variety of different options for general app types:
+The configuration dropdown provides a variety of different options for general app types:
 
 | Configuration | Description |
 | --- | --- |

docs/python/editing.md

@@ -95,7 +95,7 @@ The add imports Code Action also recognizes some of the popular abbreviations fo
 
 The import suggestions list is ordered with import statements for packages (or modules) at the top, followed by statements for additional modules and/or members (classes, objects, etc.) from specified packages.
 
-> **Note**: This functionality requires use of the [Microsoft Python Language Server](https://devblogs.microsoft.com/python/introducing-the-python-language-server). To enable the language server,  set `python.jediEnabled` to **false** in your [settings.json file](/docs/python/settings-reference.md). Additionally, you'll need to make sure that linting is enabled by opening the Command Palette (**View > Command Palette...** or `kb(workbench.action.showCommands)`) and running the **Python: Enable Linting** command (Select **On** in the drop-down menu that appears).
+> **Note**: This functionality requires use of the [Microsoft Python Language Server](https://devblogs.microsoft.com/python/introducing-the-python-language-server). To enable the language server,  set `python.jediEnabled` to **false** in your [settings.json file](/docs/python/settings-reference.md). Additionally, you'll need to make sure that linting is enabled by opening the Command Palette (**View > Command Palette...** or `kb(workbench.action.showCommands)`) and running the **Python: Enable Linting** command (Select **On** in the dropdown menu that appears).
 
 ## Run Selection/Line in Terminal (REPL)
 

docs/python/testing.md

@@ -218,7 +218,7 @@ After a test run, VS Code displays results directly with the CodeLens adornments
 
 ![Test results on a unittest class and in Test Explorer](images/testing/test-results.png)
 
-VS Code also shows test results in the **Python Test Log** output panel (use the **View** > **Output** menu command to show the **Output** panel, then select **Python Test Log** from the drop-down on the right side):
+VS Code also shows test results in the **Python Test Log** output panel (use the **View** > **Output** menu command to show the **Output** panel, then select **Python Test Log** from the dropdown on the right side):
 
 ![Test results in the Python Test Log output panel](images/testing/python-test-log-output.png)
 

docs/python/tutorial-django.md

@@ -197,7 +197,7 @@ You're probably already wondering if there's an easier way to run the server and
 
     ![Django tutorial: initial view of the debug panel](images/shared/debug-panel-initial-view.png)
 
-1. Select the link and VS Code will prompt for a debug configuration. Select **Django** from the drop-down and VS Code will populate a new `launch.json` file with a Django run configuration. The `launch.json` file contains a number of debugging configurations, each of which is a separate JSON object within the `configuration` array.
+1. Select the link and VS Code will prompt for a debug configuration. Select **Django** from the dropdown and VS Code will populate a new `launch.json` file with a Django run configuration. The `launch.json` file contains a number of debugging configurations, each of which is a separate JSON object within the `configuration` array.
 
 1. Scroll down to and examine the configuration with the name "Python: Django":
 

docs/python/tutorial-flask.md

@@ -198,7 +198,7 @@ Debugging gives you the opportunity to pause a running program on a particular l
 
     ![Flask tutorial: initial view of the debug panel](images/shared/debug-panel-initial-view.png)
 
-1. 1. Select the link and VS Code will prompt for a debug configuration. Select **Flask** from the drop-down and VS Code will populate a new `launch.json` file with a Flask run configuration. The `launch.json` file contains a number of debugging configurations, each of which is a separate JSON object within the `configuration` array.
+1. 1. Select the link and VS Code will prompt for a debug configuration. Select **Flask** from the dropdown and VS Code will populate a new `launch.json` file with a Flask run configuration. The `launch.json` file contains a number of debugging configurations, each of which is a separate JSON object within the `configuration` array.
 
 1. Scroll down to and examine the configuration, which is named "Python: Flask". This configuration contains `"module": "flask",`, which tells VS Code to run Python with `-m flask` when it starts the debugger. It also defines the FLASK_APP environment variable in the `env` property to identify the startup file, which is `app.py` by default, but allows you to easily specify a different file. If you want to change the host and/or port, you can use the `args` array.
 
@@ -226,7 +226,7 @@ Debugging gives you the opportunity to pause a running program on a particular l
 
     > **Note**: Once `launch.json` is created, an **Add Configuration** button appears in the editor. That button displays a list of additional configurations to add to the beginning of the configuration list. (The **Run** > **Add Configuration** menu command does the same action.).
 
-1. Save `launch.json` (`kb(workbench.action.files.save)`). In the debug configuration drop-down list select the **Python: Flask** configuration.
+1. Save `launch.json` (`kb(workbench.action.files.save)`). In the debug configuration dropdown list select the **Python: Flask** configuration.
 
     ![Flask tutorial: selecting the Flask debugging configuration](images/flask-tutorial/debug-select-configuration.png)
 

docs/typescript/typescript-compiling.md

@@ -126,7 +126,7 @@ As an example, if there was a simple error (extra 'g' in `console.log`) in our T
 
     HelloWorld.ts(3,17): error TS2339: Property 'logg' does not exist on type 'Console'.
 
-This would show up in the terminal panel (`kb(workbench.action.terminal.toggleTerminal)`) and selecting the **Tasks - build tsconfig.json** in the terminal view drop-down.
+This would show up in the terminal panel (`kb(workbench.action.terminal.toggleTerminal)`) and selecting the **Tasks - build tsconfig.json** in the terminal view dropdown.
 
 You can see the error and warning counts in the Status Bar. Click on the error and warnings icon to get a list of the problems and navigate to them.
 

release-notes/v1_14.md

@@ -26,7 +26,7 @@ Welcome to the June 2017 release of Visual Studio Code. There are a number of si
 * **[Emmet abbreviation enhancements](#emmet-abbreviation-improvements)** - Add Emmet to any language. Multi-cursor support.
 * **[New Diff review pane](#diff-editor-review-pane)** - Navigate Diff editor changes quickly with `F7`, displayed in patch format.
 * **[Angular debugging recipe](#recipe-for-angular-debugging)** - Debug your Angular client in VS Code.
-* **[Better screen reader support](#lists-and-quick-pick-leverage-aria-properties)** - Aria properties to better present list and drop-down items.
+* **[Better screen reader support](#lists-and-quick-pick-leverage-aria-properties)** - Aria properties to better present list and dropdown items.
 * **[Preview: 64-bit Windows build](#windows-64-bit-insiders)** - Try out the Windows 64-bit version (Insiders build).
 * **[Preview: Multi-root workspaces](#preview-multi-root-workspaces)** - Open multiple projects in the same editor (Insiders build).
 
@@ -56,7 +56,7 @@ Don't worry about losing sight of this notification. macOS users will have the u
 
 ### Command Palette improvements
 
-We improved the **Command Palette** drop-down (`kb(workbench.action.showCommands)`) to make it more useful.
+We improved the **Command Palette** dropdown (`kb(workbench.action.showCommands)`) to make it more useful.
 
 One popular request was to always restore the last typed input when reopening the **Command Palette**. Enable this behavior with the new setting `workbench.commandPalette.preserveInput`.
 
@@ -66,7 +66,7 @@ We also added a most recently used (MRU) list of commands that is persisted betw
 
 A new command **Clear Commands History** was added to quickly dismiss all the entries from the commands history.
 
-Finally, keyboard shortcuts in the drop-down are presented in the same visual form as in the **Keyboard Shortcuts** editor.
+Finally, keyboard shortcuts in the dropdown are presented in the same visual form as in the **Keyboard Shortcuts** editor.
 
 ### Restore empty workspaces
 
@@ -155,7 +155,7 @@ To make recommended extensions more visible, **Extensions** view now shows **INS
 
 ### Lists and quick pick leverage aria properties
 
-Lists such as the suggestion widget, exception list and the **Quick Open** drop-down now set `aria-setsize` and `aria-posinset`. These lists are virtualized and so without these [aria](http://www.w3.org/TR/wai-aria/) properties, screen readers could not correctly determine the number of entries.
+Lists such as the suggestion widget, exception list and the **Quick Open** dropdown now set `aria-setsize` and `aria-posinset`. These lists are virtualized and so without these [aria](http://www.w3.org/TR/wai-aria/) properties, screen readers could not correctly determine the number of entries.
 
 ## Integrated Terminal
 
@@ -192,7 +192,7 @@ If you want `Ctrl+F` to go to the shell instead of launching the Find widget on
 
 ### Rename terminal sessions
 
-Integrated Terminal sessions can now be renamed using the `workbench.action.terminal.rename` command. The new name will be displayed in the terminal selection drop-down.
+Integrated Terminal sessions can now be renamed using the `workbench.action.terminal.rename` command. The new name will be displayed in the terminal selection dropdown.
 
 ## Git
 
@@ -828,7 +828,7 @@ Contributions to `vscode`:
 * [@campersau](https://github.com/campersau):  cleanup duplicate semicolons in minimapCharRenderer [PR #28106](https://github.com/microsoft/vscode/pull/28106)
 * [Ernest Wong (@chewong)](https://github.com/chewong):  Added setting to enable/disable clickable URL [PR #28160](https://github.com/microsoft/vscode/pull/28160)
 * [Christopher Leidigh (@cleidigh)](https://github.com/cleidigh)
-  *  Fix current output drop-down selected Issue #27643 [PR #27645](https://github.com/microsoft/vscode/pull/27645)
+  *  Fix current output dropdown selected Issue #27643 [PR #27645](https://github.com/microsoft/vscode/pull/27645)
   *  Add Debug Output Copy All command : Fixes #27079 [PR #28197](https://github.com/microsoft/vscode/pull/28197)
 * [@cristianhosu](https://github.com/cristianhosu):  #22622 [PR #23211](https://github.com/microsoft/vscode/pull/23211)
 * [traBpUkciP (@Duroktar)](https://github.com/Duroktar):  Open old version of file in Git side bar. [PR #26629](https://github.com/microsoft/vscode/pull/26629)

release-notes/v1_15.md

@@ -488,7 +488,7 @@ As mentioned above, the new Workspace concept introduces a workspace configurati
 
 ### Folder Settings
 
-With multiple root folders in one workspace, it is possible to have a `.vscode` folder in each root folder defining the settings that should apply for that folder. You can open the folder settings in the Settings editor from the drop-down.
+With multiple root folders in one workspace, it is possible to have a `.vscode` folder in each root folder defining the settings that should apply for that folder. You can open the folder settings in the Settings editor from the dropdown.
 
 ![Settings Dropdown](images/1_15/settings_dropdown.png)
 
@@ -504,7 +504,7 @@ Refer to **[Configuration scopes](#configuration-scopes)** to know about `window
 
 ### Multi-root debugging
 
-When opening a multi-root workspace with multiple `launch.json` files, the Debug drop-down shows all configurations (with the originating folder in parentheses):
+When opening a multi-root workspace with multiple `launch.json` files, the Debug dropdown shows all configurations (with the originating folder in parentheses):
 
 ![multi-root debug](images/1_15/mr_debug.png)
 

release-notes/v1_16.md

@@ -135,7 +135,7 @@ It is now possible to change the cursor position in VS Code using Braille routin
 
 ### Terminal quick open improvements
 
-The Integrated Terminal can now be launched via the **Terminal: Switch Active Terminal** command or by typing "term " (with a trailing space) in **Quick Open**. When using the Integrated Terminal **Quick Open** drop-down, you can also create new terminals or delete existing terminals.
+The Integrated Terminal can now be launched via the **Terminal: Switch Active Terminal** command or by typing "term " (with a trailing space) in **Quick Open**. When using the Integrated Terminal **Quick Open** dropdown, you can also create new terminals or delete existing terminals.
 
 ![Terminal quick open improvements](images/1_16/terminal-quick-pick.png)
 

release-notes/v1_17.md

@@ -130,7 +130,7 @@ Python, Yaml, Pug, Markdown, Clojure, CoffeeScript, FSharp.
 
 ### Snippet selector
 
-The snippet picker drop-down shown by the **Insert Snippet** command now displays snippets in two groups, **User Snippets** and **Extension Snippets**. User-defined snippets are listed on top to give you quick access to your favorite snippets.
+The snippet picker dropdown shown by the **Insert Snippet** command now displays snippets in two groups, **User Snippets** and **Extension Snippets**. User-defined snippets are listed on top to give you quick access to your favorite snippets.
 
 ![Snippet Buckets](images/1_17/snippet_buckets.png)
 

release-notes/v1_20.md

@@ -125,13 +125,13 @@ With this release, new themable colors are added for editor tabs:
 
 You can configure these colors also from the `workbench.colorCustomizations` setting.
 
-### Custom drop-down (Windows, Linux)
+### Custom dropdown (Windows, Linux)
 
-On Windows and Linux, drop-downs now use a custom widget instead of the HTML control. The drop-down leverages the same colors as the tree/list widget in other parts:
+On Windows and Linux, drop-downs now use a custom widget instead of the HTML control. The dropdown leverages the same colors as the tree/list widget in other parts:
 
 ![Custom Drop-down](images/1_20/dropdown.png)
 
-This fixes a couple of issues where the HTML drop-down was not showing up properly in some cases.
+This fixes a couple of issues where the HTML dropdown was not showing up properly in some cases.
 
 ### OPEN EDITORS updates
 
@@ -359,7 +359,7 @@ Workspace scoped launch configurations live in the `"launch"` section of the wor
 
 ![Workspace Settings](images/1_20/workspace-settings.png)
 
-Alternatively new launch configurations can be added via the **Add Config (workspace)** entry of the Launch Configuration drop-down menu:
+Alternatively new launch configurations can be added via the **Add Config (workspace)** entry of the Launch Configuration dropdown menu:
 
 ![Add Config](images/1_20/add-config.png)
 

release-notes/v1_40.md

@@ -256,7 +256,7 @@ If all the tasks you care about are defined in a `tasks.json` file, then you mig
 
 In the past, any task without a problem matcher would need to have an empty problem matcher set in `tasks.json` to skip the problem matcher prompt. Now, you can use `task.problemMatchers.neverPrompt` to disable the problem matcher prompt for all tasks or for specific task types. There's also a new option in the problem matcher prompt to disable the prompt.
 
-![Problem matcher prompt drop-down](images/1_40/task-problemmatcher-prompt.png)
+![Problem matcher prompt dropdown](images/1_40/task-problemmatcher-prompt.png)
 
 ## Source Control
 

release-notes/v1_52.md

@@ -930,7 +930,7 @@ Contributions to `vscode`:
 * [Jiaxun Wei (@LeuisKen)](https://github.com/LeuisKen): cache OpenURLOptions in ExtensionUrlBootstrapHandler [PR #110725](https://github.com/microsoft/vscode/pull/110725)
 * [Jade (@lf-)](https://github.com/lf-): Explicit fontLigatures description [PR #109987](https://github.com/microsoft/vscode/pull/109987)
 * [Logan Rosen (@loganrosen)](https://github.com/loganrosen): Mark .ember-cli as jsonc instead of json [PR #110541](https://github.com/microsoft/vscode/pull/110541)
-* [Mohammed Al-Dahleh (@maldahleh)](https://github.com/maldahleh): #109255 - Add encoding description to settings "File: Encoding" drop-down [PR #109551](https://github.com/microsoft/vscode/pull/109551)
+* [Mohammed Al-Dahleh (@maldahleh)](https://github.com/maldahleh): #109255 - Add encoding description to settings "File: Encoding" dropdown [PR #109551](https://github.com/microsoft/vscode/pull/109551)
 * [Mathias Rasmussen (@mathiasvr)](https://github.com/mathiasvr): Allow git amend message only [PR #91838](https://github.com/microsoft/vscode/pull/91838)
 * [MD Asif Hasan (@mdasifhasan)](https://github.com/mdasifhasan): Fix fetchOnPull behavior for Pull and Sync [PR #99324](https://github.com/microsoft/vscode/pull/99324)
 * [Seth Fitzsimmons (@mojodna)](https://github.com/mojodna): Typo: Uncommited → Uncommitted [PR #109119](https://github.com/microsoft/vscode/pull/109119)

release-notes/v1_53.md

@@ -172,7 +172,7 @@ The breakpoint editor zone widget now supports syntax coloring by respecting the
 
 **Debug console action moved into secondary menu**
 
-In order to make more room for the debug drop-down menu in the debug view, we have moved the **Debug Console** action to the secondary menu (`...`).
+In order to make more room for the debug dropdown menu in the debug view, we have moved the **Debug Console** action to the secondary menu (`...`).
 
 In addition, we believe that the need for the action is small given that the debug console opens automatically when a debug session starts.