Spec pdf: incorrect link.

[janis-bhm]

I've noticed that the pdf specs has a broken link at VkImageMemoryBarrier2::subresourceRange, which links to #resource-image-views and not #VkImageSubresourceRange. The same is true for VkImageMemoryBarrier::subresourceRange

[oddhack]

I don't think the link is actually broken, is it - just links to something you were not expecting (the top-level subsection describing image views rather than the section describing the structure type)?

We could say something like 'subresourceRange is a VkImageSubresourceRange[link] structure describing an image subresource range[link] if that would help.

Really it would be nice if the structure definitions automatically linked to the data types of their members, but getting that factored through the various code formatters we use in the toolchain is surprisingly difficult.