jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

FIX: change ; to ,

Browse source
This commit is contained in:
LeviDing 2020-10-15 13:16:32 +08:00 • committed by GitHub
parent 15767fc3cf
commit f0c55baab7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/01-getting-started/4-devtools/article.md
View file

@ -8,7 +8,7 @@ To see errors and get a lot of other useful information about scripts, "develope
Most developers lean towards Chrome or Firefox for development because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catch-up" to Chrome or Firefox. So most developers have a "favorite" browser and switch to others if a problem is browser-specific. Most developers lean towards Chrome or Firefox for development because those browsers have the best developer tools. Other browsers also provide developer tools, sometimes with special features, but are usually playing "catch-up" to Chrome or Firefox. So most developers have a "favorite" browser and switch to others if a problem is browser-specific.
Developer tools are potent; they have many features. To start, we'll learn how to open them, look at errors, and run JavaScript commands. Developer tools are potent, they have many features. To start, we'll learn how to open them, look at errors, and run JavaScript commands.
## Google Chrome ## Google Chrome