Problem/Motivation
The form for editing a single corresponding entity reference (form#corresponding-reference-edit-form) would be way more user-friendly if the "first field" / "second field" select lists included the label/human-readable name as a prefix, like how the bundles list has the entity type as a prefix.
I know human-readable names are per field instance, but the Views admin interface handles it somehow (they seem to use the "default" field label, which I imagine is the first one that existed? and then "also known as" -- which doesn't seem important here, I'm just explaining), so maybe we can use that as a model?
Alternatively, maybe just changing the option-list sort to be alphabetical by machine name, since that's what's shown as the choices.
Proposed resolution
Add human-labels to "first/second fields"
OR
Order the "first/second field" options alphabetically by machine name.
Remaining tasks
decide... do...
User interface changes
Depends on decision, but: changes to user interface text would be included.
Release notes snippet
(Major and critical issues should have a snippet that can be pulled into the release notes when a release is created that includes the fix)
Original report by [username]
(Text of the original report, for legacy issues whose initial post was not the issue summary. Use rarely.)