diff --git a/bin/auto-sync.txt b/bin/auto-sync.txt
index 16e028417..9b30c60e0 100644
--- a/bin/auto-sync.txt
+++ b/bin/auto-sync.txt
@@ -68,6 +68,7 @@ resistor-color
 resistor-color-duo
 reverse-string
 rna-transcription
+robot-name
 robot-simulator
 roman-numerals
 rotational-cipher
diff --git a/exercises/practice/robot-name/.docs/instructions.md b/exercises/practice/robot-name/.docs/instructions.md
index a0079a341..fca3a41ae 100644
--- a/exercises/practice/robot-name/.docs/instructions.md
+++ b/exercises/practice/robot-name/.docs/instructions.md
@@ -4,13 +4,11 @@ Manage robot factory settings.
 
 When a robot comes off the factory floor, it has no name.
 
-The first time you turn on a robot, a random name is generated in the format
-of two uppercase letters followed by three digits, such as RX837 or BC811.
+The first time you turn on a robot, a random name is generated in the format of two uppercase letters followed by three digits, such as RX837 or BC811.
 
-Every once in a while we need to reset a robot to its factory settings,
-which means that its name gets wiped. The next time you ask, that robot will
-respond with a new random name.
+Every once in a while we need to reset a robot to its factory settings, which means that its name gets wiped.
+The next time you ask, that robot will respond with a new random name.
 
 The names must be random: they should not follow a predictable sequence.
-Using random names means a risk of collisions. Your solution must ensure that
-every existing robot has a unique name.
+Using random names means a risk of collisions.
+Your solution must ensure that every existing robot has a unique name.
diff --git a/exercises/practice/robot-name/.meta/config.json b/exercises/practice/robot-name/.meta/config.json
index 76419de06..2d550eb0b 100644
--- a/exercises/practice/robot-name/.meta/config.json
+++ b/exercises/practice/robot-name/.meta/config.json
@@ -11,7 +11,8 @@
     "lafent",
     "masters3d",
     "petemcfarlane",
-    "schorsch3000"
+    "schorsch3000",
+    "hazeolation"
   ],
   "files": {
     "solution": [
diff --git a/exercises/practice/robot-name/.meta/example.php b/exercises/practice/robot-name/.meta/example.php
index d9edb40b9..1839f1329 100644
--- a/exercises/practice/robot-name/.meta/example.php
+++ b/exercises/practice/robot-name/.meta/example.php
@@ -1,27 +1,5 @@
 <?php
 
-/*
- * By adding type hints and enabling strict type checking, code can become
- * easier to read, self-documenting and reduce the number of potential bugs.
- * By default, type declarations are non-strict, which means they will attempt
- * to change the original type to match the type specified by the
- * type-declaration.
- *
- * In other words, if you pass a string to a function requiring a float,
- * it will attempt to convert the string value to a float.
- *
- * To enable strict mode, a single declare directive must be placed at the top
- * of the file.
- * This means that the strictness of typing is configured on a per-file basis.
- * This directive not only affects the type declarations of parameters, but also
- * a function's return type.
- *
- * For more info review the Concept on strict type checking in the PHP track
- * <link>.
- *
- * To disable strict typing, comment out the directive below.
- */
-
 declare(strict_types=1);
 
 class Robot
diff --git a/exercises/practice/robot-name/RobotNameTest.php b/exercises/practice/robot-name/RobotNameTest.php
index 0ae7e516c..ea17d738e 100644
--- a/exercises/practice/robot-name/RobotNameTest.php
+++ b/exercises/practice/robot-name/RobotNameTest.php
@@ -1,27 +1,5 @@
 <?php
 
-/*
- * By adding type hints and enabling strict type checking, code can become
- * easier to read, self-documenting and reduce the number of potential bugs.
- * By default, type declarations are non-strict, which means they will attempt
- * to change the original type to match the type specified by the
- * type-declaration.
- *
- * In other words, if you pass a string to a function requiring a float,
- * it will attempt to convert the string value to a float.
- *
- * To enable strict mode, a single declare directive must be placed at the top
- * of the file.
- * This means that the strictness of typing is configured on a per-file basis.
- * This directive not only affects the type declarations of parameters, but also
- * a function's return type.
- *
- * For more info review the Concept on strict type checking in the PHP track
- * <link>.
- *
- * To disable strict typing, comment out the directive below.
- */
-
 declare(strict_types=1);
 
 use PHPUnit\Framework\TestCase;