“Product Backlog item selected for the Sprint” is difficult to write and read. And the Product Backlog item selected for the Sprint is no longer in the Product Backlog.
It may be helpful to define the Sprint Backlog Item, which doesn’t include a plan for delivering it (for example tasks).
The only change in the Scrum Guide would be adding something like this:
“The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what; aka Sprint Backlog Items), as well as an actionable plan for delivering the Increment (how).”
Although okay as recommendatin, I feel this is focusing on the mechanical nature of scrum and not really creating the environment and behaviours that people don’t get caught up with wording symantics.
The intention is more to create transparency, who cares what it called.
Sure some wording changes may help people come to the reality of what Scrum is really about, but as I have posted many a time here is the guide generally is badly written.
I for one care what things are called. Word choice is always important and when the intent is to remove confusion I applaud those who question existing terminology.
For this suggestion I can see where this could bring value and simultaneously where it would not. I think it is highly contextual. Personally I have experienced this disctinction in the field many times and would not object to this change. Nor will I cry if it is not made.