images

Author: iliakan

1-js/02-first-steps/01-hello-world/hello-world-render.svg

@@ -50,7 +50,7 @@ Congratulations! You've set a breakpoint. Please also click on the number for li
 
 It should look like this (blue is where you should click):
 
-![](chrome-sources-breakpoint.png)
+![](chrome-sources-breakpoint.svg)
 
 A *breakpoint* is a point of code where the debugger will automatically pause the JavaScript execution.
 
@@ -93,7 +93,7 @@ In our example, `hello()` is called during the page load, so the easiest way to
 
 As the breakpoint is set, the execution pauses at the 4th line:
 
-![](chrome-sources-debugger-pause.png)
+![](chrome-sources-debugger-pause.svg)
 
 Please open the informational dropdowns to the right (labeled with arrows). They allow you to examine the current code state:
 
@@ -125,7 +125,7 @@ There are buttons for it at the top of the right pane. Let's engage them.
 
     Here's what we can see after a click on it:
 
-    ![](chrome-sources-debugger-trace-1.png)
+    ![](chrome-sources-debugger-trace-1.svg)
 
     The execution has resumed, reached another breakpoint inside `say()` and paused there. Take a look at the "Call stack" at the right. It has increased by one more call. We're inside `say()` now.
 

1-js/02-first-steps/10-ifelse/2-check-standard/ifelse_task2.svg

@@ -28,7 +28,7 @@ It works like this:
 2. If there were no errors, then `catch(err)` is ignored: the execution reaches the end of `try` and then jumps over `catch`.
 3. If an error occurs, then `try` execution is stopped, and the control flows to the beginning of `catch(err)`. The `err` variable (can use any name for it) contains an error object with details about what's happened.
 
-![](try-catch-flow.png)
+![](try-catch-flow.svg)
 
 So, an error inside the `try {…}` block does not kill the script: we have a chance to handle it in `catch`.