More example `same hierarchy` in path templating

We can't describe different templated name with same hierarchy.

Templated paths with the same hierarchy but different templated names MUST NOT exist as they are identical.

But I can't understand what the same hierarchy means.

We can't describe these path templates

  /pets/{petId}
  /pets/{name}

But we can describe these?

  /pets/{petId}
  /pets/{name}/hello

These depth of the hierarchy is different but these is different templated name in same depth of hierarchy.
When we get /pets/1/hello we can match bottom paths and name=1.
These is partially the same, but the whole is different.

So I want to add more example to this section.

Find the specification section containing the quoted “same hierarchy” rule and read the surrounding path-templating guidance. Add an example clarifying why /pets/{petId} and /pets/{name} conflict while the deeper /pets/{name}/hello path differs, then check that the wording matches the rule.