I've seen a lot of bug templates all having **Expected Result** before **Actual Result**. To me, this does not make sense because it breaks the flow of reading through the bug/page.

Usually when you read (anything, not just a bug) you'd go:

**top > bottom** 

and not 

**top > middle > bottom > middle again > almost bottom**

I asked several coworkers why they write bugs in that way the general answer I got was that "that's how it was in a bug template" / "that how I was told to write it"

Can someone explain why those are reversed in bug templates and what are the benefits of having the expected before the actual?