Skip to content

Commit 7fc394c

Browse files
committed
Fix typos
1 parent dbd29d8 commit 7fc394c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/usage/vscode.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Visual Studio Code
33
description: See how Visual Studio Code and its extensions helps you run and debug your Pester tests directly inside the editor
44
---
55

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.
77

88
### Code lens
99

@@ -26,7 +26,7 @@ You can control the output verbosity level in VSCode output, or let it inherit f
2626

2727
### Navigation
2828

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.
3030

3131
![Shows a outline of Pester block structure in the sidepanel](images/vscode-outline.png)
3232

0 commit comments

Comments
 (0)