In the following section, under the Decomposition heading:
In Ruby, it is possible to decompose the elements of arrays/hashes into distinct variables. Since values appear within arrays in a index order, they are unpacked into variables in the same order:
“…in a index order…” should be “…in an index order…”.
Assuming I’m not overlooking something, let me know when you’re ready for a PR.
Also, I’m looking at Ruby’s locomotive-engineer’s introduction.md for this typo (same for the other two posts I just created). Does the fact that this is a “concept” mean these could be relevant to other tracks?
I am pretty sure I will take all three, but I have to look at the other two more carefully than this one.
For this specific wording we can drop the “an” or “a” and just make it “in index order”.
If you fix this, you might also notice that introduction.md and about.md are almost identical in the first 22 lines.
We might want to make them identical in those first 22 lines. I prefer using full words, rather than abbreviations, even though we often see abbreviations used in the documentation, we can be clearer than that.
One commit for that, one for the “in index order” change.
Practice exercises almost all use the exact .md from the problem specs so they are uniform across tracks and synced from the specs reop.
Concept exercises are not sync across locations (except possibly between the intro and about files). It’s possible that a track copied the exercise from another track, though, and that the same doc is shared across tracks. However, changes to different tracks should be handled as completely separate reports as different tracks have different maintainers and processes.
I haven’t seen this term before so the description was confusing and a Google search brought up unrelated things. Reading between the lines, index order likely means the array values are in the order of their indices. “Values are unpacked into variables in the same order they appear within the arrays” would avoid my confusion without losing clarity.