Cross-functional teams have all the skills and competencies needed to deliver end-to-end work.

The Development Team may need to order the Product Backlog as they would know the most about technical limitations, risks, or dependencies between Product Backlog Items. As User Stories is a localized practice, Scrum does not govern it or dictate the practice. How the team describes the items is up to them as long as it has enough information to be transparent and understood.

The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team.
Only the Development Team can assess what it can accomplish over the upcoming Sprint.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.