Why does adding two .OrderBy (or .OrderByDescending) statements apply the sorts in reverse order?

Question

I came across the following in some code that I was refactoring today.

context.Entities.Where(x => x.ForeignKeyId == id)
    .OrderBy(x => x.FirstSortField)