tracks/java/exercises/hello-world/TUTORIAL.md in trackler-2.0.0.5 vs tracks/java/exercises/hello-world/TUTORIAL.md in trackler-2.0.0.6
- old
+ new
@@ -417,10 +417,10 @@
the code is in the most readable/maintainable/efficient shape. What makes
for "good" design of software is a big topic. The pursuit of it underlies
much of what makes up the more valuable conversations on Exercism.
For now, let's just take a quick review of our solution and see if there's
-any part of it we'd like to refactor. Refactoring is changing the the way
+any part of it we'd like to refactor. Refactoring is changing the way
a bit of code reads without changing what it does.
Right now, the details of detecting whether the caller of `hello()` has
given a name or not (i.e. `name` is either `null` or an empty string) is
sitting right next to the core responsibility of the method: to produce a