I can understand why it is confusing.

If it helps, Evaluate should almost never be used. So understanding this distinction is not really important for writing good code.

This is also completely correct. the other t's in the list take on the global value of "t". The first one is just the variable for the local iteration.

It is easy to create intentionally confusing code like:

t = 7; Table[t, {t, t, 10}]

Most programmers cannot tell you what this code would do. They just avoid this kind of ambiguity.

Avoiding ambiguity is an important programming skill. More important than a strict understanding of how code evaluates.

I knew a proffesor in college (not Comp Sci.) who loved to create these kinds of puzzles in the C programming language and gave them to his students. He had no real programming experience and got very little taught except making sure his students hated programming as much as he did.

This is how it should work. When you run use "Evaluate", you are asking for that section to evaluate before being given to Table. And in Table, you've asked for "t" to be localized.

That behavior is how this is all supposed to work.

The variable t inside Table is protected from outside assignments. You can force t to get the outside value 7 this way:

t = 7;
Table[Evaluate[t + 1], {t, 1, 10}]