You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/usage/vscode.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Visual Studio Code
3
3
description: See how Visual Studio Code and its extensions helps you run and debug your Pester tests directly inside the editor
4
4
---
5
5
6
-
Using Visual Studio Code with the latest [PowerShell extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell)is a great combination for writing PowerShell code. The extenstion even includes a few Pester-specific features to improve the way you write, run and debug Pester tests.
6
+
Using Visual Studio Code with the latest [PowerShell extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.PowerShell)provides a great experience for writing PowerShell code. The extension includes Pester-specific features to improve the way you write, run and debug Pester tests.
7
7
8
8
### Code lens
9
9
@@ -26,7 +26,7 @@ You can control the output verbosity level in VSCode output, or let it inherit f
26
26
27
27
### Navigation
28
28
29
-
Pester-blocks are recognized by the PowerShell-extenstion to simplify navigation in your test files. You can see the strcuture of your Pester file using the Outline view.
29
+
Pester-blocks are recognized by the PowerShell-extension to simplify navigation in your test files. You can see the strcuture of your Pester file using the Outline view.
30
30
31
31

0 commit comments