Skip to content

Commit 189b398

Browse files
fix: typos in choosing-an-editor.md (#173)
1 parent 5aec2e6 commit 189b398

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/guide/choosing-an-editor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ If you do choose to [try Visual Studio Code](https://code.visualstudio.com/), le
1616

1717
After you install Visual Studio Code, you can open projects using the editor's `File``Open` menu option, but there's an alternative option that works far better for command-line-based projects like NativeScript: the `code` command.
1818

19-
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows on Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
19+
The `code` command runs in your command-line or terminal, and it works just like the `ns` command does for NativeScript apps. Visual Studio Code installs the `code` command by default on Windows and Linux, but on macOS, there's [one manual step](https://code.visualstudio.com/docs/setup/mac) you must perform.
2020

21-
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of command to create a new NativeScript app and open it for editing.
21+
Once set up, you can type `code .` in your terminal to open the files in your current folder for editing. For example, you could use the following sequence of commands to create a new NativeScript app and open it for editing.
2222

2323
```bash
2424
ns create MyNewApp

0 commit comments

Comments
 (0)