Update best practices SDK link to always point at latest

Author: SaschaWillems

en/06_Texture_mapping/02_Combined_image_sampler.adoc

@@ -60,7 +60,7 @@ Other times, `vkAllocateDescriptorSets` will fail and return `VK_ERROR_POOL_OUT_
 This can be particularly frustrating if the allocation succeeds on some machines, but fails on others.
 
 Since Vulkan shifts the responsibility for the allocation to the driver, it is no longer a strict requirement to only allocate as many descriptors of a certain type (`VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER`, etc.) as specified by the corresponding `descriptorCount` members for the creation of the descriptor pool.
-However, it remains best practice to do so, and in the future, `VK_LAYER_KHRONOS_validation` will warn about this type of problem if you enable https://vulkan.lunarg.com/doc/view/1.3.280.0/linux/best_practices.html[Best Practice Validation].
+However, it remains best practice to do so, and in the future, `VK_LAYER_KHRONOS_validation` will warn about this type of problem if you enable https://vulkan.lunarg.com/doc/view/latest/windows/best_practices.html[Best Practice Validation].
 
 The final step is to bind the actual image and sampler resources to the descriptors in the descriptor set.
 Go to the `createDescriptorSets` function.