Are "Plans" definition of the example given in Appendix E consistent with the BPMN SPEC?

In the current version of TOSCA, the Appendix E introduces an example where a Plan (with id="DeployApplication") is described in detail. In this plan, the PlanModel is described by BPMN 2.0. However, I found there is something not consistent with the BPMN2.0. For instance, in the example, the name of a task means the corresponding operation invoked during the runtime. But, the name of a task in BPMN2.0 is just the content read by human beings, rather than representing the task's corresponding operation. So, it is recommended to clarify this in the SPEC.