Move dictionaries to i18n

Yes, but that is the point. Those it blocks are "hidden" contexts, to me, and I would rather see everything in the open than have to take a second look and realize that it really is more nested than at first glance.

While I like the second better from a concise standpoint, I think the specs serve a better purpose than simply ensuring your code does what you think it does. In this case, if we had a bunch of nested contexts and a simple assertion in each one, it makes me think this could be refactored later to be cleaner and not be doing as much, and then we wouldn't have as many contexts to worry about. So, the next person to go in might see "wow there are a lot of contexts here let me make a new class for this functionality I want to add" instead of just adding a single line with another "hidden" context and eventually this becomes difficult to unravel.

This is all my opinion, so if we don't want to change right now, we don't have to. I just saw this and it's relatively small so I wanted to weigh in.