How does the representing flow of a extending use case include another use case in the specification document?

Question

My use case:

Example of how I’m doing the flow specification:

[...]

1. X-flow.
2. Flux y.
3. Z-stream.
4. Here would need to enter the use case part "Provide Identification" \ "Cadastrar Times"

My doubt: When specifying the use case flows "Place Bet" \ "Administrate Times" what would be the most recommended way to describe that this use case has a <<extends>> ? And in case you’re a <<include>> ?