diff --git a/1-js/02-first-steps/01-hello-world/hello-world-render.svg b/1-js/02-first-steps/01-hello-world/hello-world-render.svg
deleted file mode 100644
index 215df79e..00000000
Binary files a/1-js/02-first-steps/01-hello-world/hello-world-render.svg and /dev/null differ
diff --git a/1-js/02-first-steps/10-ifelse/2-check-standard/ifelse_task2.svg b/1-js/02-first-steps/10-ifelse/2-check-standard/ifelse_task2.svg
index e69de29b..d2ac8d76 100644
--- a/1-js/02-first-steps/10-ifelse/2-check-standard/ifelse_task2.svg
+++ b/1-js/02-first-steps/10-ifelse/2-check-standard/ifelse_task2.svg
@@ -0,0 +1,48 @@
+
+
\ No newline at end of file
diff --git a/1-js/02-first-steps/11-logical-operators/9-check-login/ifelse_task.svg b/1-js/02-first-steps/11-logical-operators/9-check-login/ifelse_task.svg
index e69de29b..c391a680 100644
--- a/1-js/02-first-steps/11-logical-operators/9-check-login/ifelse_task.svg
+++ b/1-js/02-first-steps/11-logical-operators/9-check-login/ifelse_task.svg
@@ -0,0 +1,101 @@
+
+
\ No newline at end of file
diff --git a/1-js/03-code-quality/01-debugging-chrome/article.md b/1-js/03-code-quality/01-debugging-chrome/article.md
index 1ca3c28c..70c52efc 100644
--- a/1-js/03-code-quality/01-debugging-chrome/article.md
+++ b/1-js/03-code-quality/01-debugging-chrome/article.md
@@ -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):
-
+
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:
-
+
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:
- 
+ 
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.
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.png
deleted file mode 100644
index 822daba8..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.png and /dev/null differ
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.svg b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.svg
new file mode 100644
index 00000000..f83e0268
--- /dev/null
+++ b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint.svg
@@ -0,0 +1,25 @@
+
+
\ No newline at end of file
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint@2x.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint@2x.png
deleted file mode 100644
index cc278f13..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-breakpoint@2x.png and /dev/null differ
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.png
deleted file mode 100644
index 2d86f5d7..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.png and /dev/null differ
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.svg b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.svg
new file mode 100644
index 00000000..62de7351
--- /dev/null
+++ b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause.svg
@@ -0,0 +1,70 @@
+
+
\ No newline at end of file
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause@2x.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause@2x.png
deleted file mode 100644
index 5899b652..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-pause@2x.png and /dev/null differ
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.png
deleted file mode 100644
index d15e36c4..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.png and /dev/null differ
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.svg b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.svg
new file mode 100644
index 00000000..b9d05f4e
--- /dev/null
+++ b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1.svg
@@ -0,0 +1,18 @@
+
+
\ No newline at end of file
diff --git a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1@2x.png b/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1@2x.png
deleted file mode 100644
index e1aa1e8c..00000000
Binary files a/1-js/03-code-quality/01-debugging-chrome/chrome-sources-debugger-trace-1@2x.png and /dev/null differ
diff --git a/1-js/03-code-quality/02-coding-style/code-style.svg b/1-js/03-code-quality/02-coding-style/code-style.svg
index 8a9f24b6..d25454fb 100644
--- a/1-js/03-code-quality/02-coding-style/code-style.svg
+++ b/1-js/03-code-quality/02-coding-style/code-style.svg
@@ -6,77 +6,77 @@
-
-
-
-
-
-
+
+
+
+
+
+
- 2
+ 2
-
-
-
+
+
+
- No space
- between the function name and parentheses
- between the parentheses and the parameter
+ No space
+ between the function name and parentheses
+ between the parentheses and the parameter
-
+
- Indentation
- 2 spaces
+ Indentation
+ 2 spaces
-
+
- A space
- after for/if/while…
+ A space
+ after for/if/while…
-
+
- } else { without a line break
+ } else { without a line break
-
+
- Spaces around a nested call
+ Spaces around a nested call
-
+
- An empty line
- between logical blocks
+ An empty line
+ between logical blocks
-
+
- Lines are not very long
+ Lines are not very long
-
+
- A semicolon ;
- is mandatory
+ A semicolon ;
+ is mandatory
-
+
- Spaces
- around operators
+ Spaces
+ around operators
-
+
- Curly brace {
- on the same line, after a space
+ Curly brace {
+ on the same line, after a space
-
-
+
+
- A space
- between
- parameters
+ A space
+ between
+ parameters
-
+
- A space between parameters
+ A space between parameters
-
+
\ No newline at end of file
diff --git a/1-js/06-advanced-functions/01-recursion/recursion-pow.svg b/1-js/06-advanced-functions/01-recursion/recursion-pow.svg
index 156ccb4f..cb81b12a 100644
Binary files a/1-js/06-advanced-functions/01-recursion/recursion-pow.svg and b/1-js/06-advanced-functions/01-recursion/recursion-pow.svg differ
diff --git a/1-js/10-error-handling/1-try-catch/article.md b/1-js/10-error-handling/1-try-catch/article.md
index 4a1adba0..8b265e22 100644
--- a/1-js/10-error-handling/1-try-catch/article.md
+++ b/1-js/10-error-handling/1-try-catch/article.md
@@ -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.
-
+
So, an error inside the `try {…}` block does not kill the script: we have a chance to handle it in `catch`.
diff --git a/1-js/10-error-handling/1-try-catch/try-catch-flow.png b/1-js/10-error-handling/1-try-catch/try-catch-flow.png
deleted file mode 100644
index 8b377538..00000000
Binary files a/1-js/10-error-handling/1-try-catch/try-catch-flow.png and /dev/null differ
diff --git a/1-js/10-error-handling/1-try-catch/try-catch-flow.svg b/1-js/10-error-handling/1-try-catch/try-catch-flow.svg
index 7b1005c8..1db85eec 100644
--- a/1-js/10-error-handling/1-try-catch/try-catch-flow.svg
+++ b/1-js/10-error-handling/1-try-catch/try-catch-flow.svg
@@ -1,54 +1,57 @@
-