Skip to content

Commit e2c276c

Browse files
authored
Merge pull request NativeScript#1923 from dodongphure/fix-cli-basic-docs-links
Fix cli basic docs links
2 parents 85533d9 + 88debd7 commit e2c276c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/start/cli-basics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -258,10 +258,10 @@ You now know how to create and run NativeScript apps. Your next step is learning
258258
There are two main paths you can take when you want to debug a NativeScript application:
259259

260260
- **Chrome**
261-
The default way of debugging a NativeScript application is by using the integration with Chrome. You can find more information on the actual steps [here](http://docs.nativescript.org/tooling/debugging).
261+
The default way of debugging a NativeScript application is by using the integration with Chrome. You can find more information on the actual steps [here](https://docs.nativescript.org/tooling/debugging/chrome-devtools).
262262

263263
- **Visual Studio Code**
264-
One of the preferred ways of debugging a NativeScript application is with the [NativeScript extension for Visual Studio Code](http://docs.nativescript.org/tooling/debugging#debugging-with-visual-studio-code).
264+
One of the preferred ways of debugging a NativeScript application is with the [NativeScript extension for Visual Studio Code](https://docs.nativescript.org/tooling/visual-studio-code-extension).
265265

266266
You’ll want to check out the Chrome Dev Tools and the Visual Studio debugger as you need to step through your JavaScript code or TypeScript code, but for the moment let’s look at how to do some simple logging in your apps.
267267

0 commit comments

Comments
 (0)