Very beatiful and nice kata

Replaced with in initial solution, sample tests, and test cases

In C++:

• #include <iostream> is unnecessary in initial solution and in sample tests
• #include <string> is missing in initial soltuion

First off {1, 3, 2, 2, 2, 5} wouldn't be an issue however, none of the two's would be an error, but for
{1, 3, 2, 2, 2, 5} none of the 2's would be an error thus none of them should be removed. For this in example in particular 5 would be the error.

Trying C++...
Could you precise the "4- If planets in a row are the same size it will not count as an error for ordered nor antiordered"
Doest it mean that you remove ALL the same values in a row (i.e. {1,3,2,2,2,5} becomes {1,3,5} for ordered, having no error), or does it mean that you keep only the 1rst anomaly meaning 1,3,2,2,2,5 yields to {1,3,2,5} and thus leaves with 1 error ?
Should it be "4- If planets in a row are the same size it will not count as multiple errors for ordered nor antiordered" ?

Included image of periodic table

Approved by author

PHP translation

People need to lookup the periodic table to know what to expect in a solar system. You should specify elements are titlecased. This way, the kata can be solved without having to click an external link.

That one can only be applied by usage of language code-blocks, but should not be encouraged except for tutorial-based katas that require emphasizing syntax-wise differences among languages during implementation.

Updated, is there away that you could have a different description for each language?

Since python's function name (and other languages that uses snake_case) will be incompatible with the current description despite update below, a more generalized form is suggested like

**Input 1, Input2 --> Output**
["OHNCCaP_100", "OHC_200", "OCa_50", "OHCCaP_400", "OHNCCaP_225", "OHCa_250"], 250 --> "OHNCCaP_225"

Above is just an example, as long as you remove the function name across all sections of your description, it should be fine.

Approved

[updated above]

Removed cpp from all of them, now they should be language agnostic :)