So I've started reworking these assertions to

Great initiative.

Should these two commits result into two statements in the changelog?

Don't think so. Also, the 2nd commit seems to contain unrelated changes. In other words, you've changed the expected output in the specs, but there are no other changes that are the cause of this.

The second commit contains change of test and change using expectationIterator instead of subjectIterator.

The second commit contains change of test and change using expectationIterator instead of subjectIterator.

Yes, so it's weird that you had to change a test even though nothing changed in that commit. So I fail to understand why you were asking about the commits.

The commits are doing what their commit message reports:

1. add variable name and some additional information
2. change kind of XML validation to get better message

Regarding changelog this could be two changes or a single one.

We must be on the wrong channel ;-)

The 2nd commit updates XElementAssertionSpecs.cs, but there's nothing in that commit that seems to cause a change in the assertion method. So I don't understand why that change is in the 2nd commit. If it was caused by the 1st commit, that change should belong there. Just a matter of a fixup commit.

Thanks for giving the xml assertions and specs some needed love.

I think the two commits are so closely related, that the single release note covers them both - and that's fine by me.