Skip to content

Commit 9381f3d

Browse files
authored
Update how-to-diagnose-ui-delays-caused-by-extensions.md
Fixing a typo.
1 parent 85253b0 commit 9381f3d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/extensibility/how-to-diagnose-ui-delays-caused-by-extensions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ In the following sections, we will go through these steps in more detail.
3939

4040
## Identifying the trigger scenario
4141

42-
To do diagnose a UI delay, you first need to idetify what (sequence of actions) causes Visual Studio to show the notification. This is in order for you to able to trigger the notification later with logging turned on.
42+
To do diagnose a UI delay, you first need to identify what (sequence of actions) causes Visual Studio to show the notification. This is in order for you to able to trigger the notification later with logging turned on.
4343

4444
## Restarting VS with activity logging on
4545

0 commit comments

Comments
 (0)