From 91a1b1b6647703353ae1420f9b14c6b51fa93be5 Mon Sep 17 00:00:00 2001 From: Anna Bulenkova Date: Tue, 24 Mar 2015 13:51:47 +0100 Subject: [PATCH] [site] cosmetics --- tool_windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tool_windows.md b/tool_windows.md index 804f3d167..e90da54f7 100644 --- a/tool_windows.md +++ b/tool_windows.md @@ -18,7 +18,7 @@ For example, the Run toolwindow displays a tab for each active run configuration There are two main scenarios for the use of tool windows in a plugin. In the first scenario (used by the Ant and Commander plugins, for example), a toolwindow button is always visible, and the user can activate it and interact with the plugin functionality at any time. -In the second scenario (used by the Analyze Dependencies action, for example), the toolwindow is created to show the results of a specific operation, and can be closed by the user after the operation is completed. +In the second scenario (used by the ```Analyze Dependencies``` action, for example), the toolwindow is created to show the results of a specific operation, and can be closed by the user after the operation is completed. In the first scenario, the toolwindow is registered in *plugin.xml* using the `````` extension point. The extension point attributes specify all the data which is necessary to display the toolwindow button: