Off by one error in toString, the last node is at index maxNumber-1.

Since `maxNumber` is initially set to `-1` and it is incremented with each added node, the first node will be at index `0` and the last node will be at `maxNumber-1`. This commit fixes a bug that would result in an index out of bounds exception by attempting to access `nodes[maxNumber]` when printing the nodes.