A worked example of how a five-person development team plans a two-week sprint using capacity and the average of its recent velocity.
The setup: five developers, a two-week sprint of 10 weekdays, two public holidays and one approved day of leave. The team plans the sprint from its capacity and its recent velocity, not from a guess.

Worked example, not a customer result. All numbers below are made up to show the arithmetic. Replace them with your own rates, hours and fees.
The Resource Planner in Autovella uses 8 hours per weekday and reduces it for holidays and approved time off. Use its figures as a guide, because it does not read individual working-hour patterns. See Resource planner and workload.
Velocity is the story points completed in a sprint. Suppose the last four sprints completed 38, 35, 41 and 35 points.
A commitment of about 36 points is a reasonable plan, because the average already reflects normal interruptions. Sprint velocity is shown in the sprint reports. See Sprints and agile planning.
No. Capacity in the Resource Planner is in hours, based on working days, holidays and approved time off. Story points are tracked as velocity on sprints.
It is the story points completed in each sprint. Average several recent sprints rather than using one, to smooth out unusual weeks.
When you complete a sprint, Autovella asks you to move unfinished tasks to the backlog or another sprint, so you choose where they go.