diff --git a/getting_started/step_by_step/img/signals_17_custom_signal.png b/getting_started/step_by_step/img/signals_17_custom_signal.png
deleted file mode 100644
index 5f34904a8..000000000
Binary files a/getting_started/step_by_step/img/signals_17_custom_signal.png and /dev/null differ
diff --git a/getting_started/step_by_step/img/signals_17_custom_signal.webp b/getting_started/step_by_step/img/signals_17_custom_signal.webp
new file mode 100644
index 000000000..e5d5c18e9
Binary files /dev/null and b/getting_started/step_by_step/img/signals_17_custom_signal.webp differ
diff --git a/getting_started/step_by_step/signals.rst b/getting_started/step_by_step/signals.rst
index f8b46a524..f5a0ff7c1 100644
--- a/getting_started/step_by_step/signals.rst
+++ b/getting_started/step_by_step/signals.rst
@@ -442,7 +442,7 @@ reaches 0.
 Your signals work the same way as built-in ones: they appear in the Node tab and
 you can connect to them like any other.
 
-.. image:: img/signals_17_custom_signal.png
+.. image:: img/signals_17_custom_signal.webp
 
 To emit a signal in your scripts, call ``emit()`` on the signal.
 
@@ -472,7 +472,7 @@ names between parentheses:
 .. tabs::
  .. code-tab:: gdscript GDScript
 
-    extends Node
+    extends Node2D
 
     signal health_changed(old_value, new_value)